The release notes refer to different sections of the application:

Back Office: Where Customer Service Representatives (CSR) create and edit orders, create accounts, review drivers, etc.

Dispatch Board: Where Dispatchers assign orders to drivers, get notifications for invalid orders, etc.

Auto-Dispatch: This section refers to the automated order assignment setup and its process.

Administration: This section is in the Back Office but refers to sections only an administrator will use like Settings and Pricing.

Customer Portal: Where account users log in to create orders, view their order history, enter a credit card, etc.

Tracking site: Where customers enter a tracking number like the order ID or a reference number to view the status of their order.

OData: Data fields and variables saved in OData.

Account API: API provided to your accounts to create, update and get orders. For documentation, please follow this link:
Tenant API: API provided to you to create orders for your accounts, retrieve invoices and change invoice status. For documentation, please follow this link:  


Bug Fixes included in this release

  • A price list could not be saved without a file imported however, price list needed to be saved when using separate price sheet per vehicle type. You can now save the price list without a file. 
  • Optimizer failed to Optimize a Route in Mode Fixed Stops Allow Insertions when Order were late and using the On Demand Optimization option. 
  •  During the time change (going from standard to daylight saving time) Recurring Orders/Routes where an Order Template would go across 2 time zones as they are happening around the 2AM time change, Orders could have a To Time that would be set earlier than the From time. Since this is not admissible, the Recurrence or Recurring Route would not fire. To fix this, any orders where the To Time would be before the From time when going to Daylight Saving, the To Time on the Orders will be made the same as the From time.
  • When Order Profile contained more than 236 characters, an error 500 was displayed during the saving process. The name will now be shortened to 256 characters, allowing the save process to be completed.
  • Recurrences with invalid Route names were able to be saved which was creating a problem once the Route was used. If a Recurrence is saved with an invalid Route Name, an error message will be displayed and the Recurrence will not be saved:
  • When sorting Next Stop Eta on the Dispatch Grid Board, it was sorting alphabetically rather than by time.
  • If the avoid Toll Road was selected in the Tenant settings, the mileage indicated in the Order was using toll road. 
  • The Driver Audit did not always show when a Driver was unarchived.
  • Could not create a Driver with a null Reports To even if the field is not required.
  • The following fields were added in the new Order Search in the Back Office:
  • On the new Order Search, the ability to move columns has been added.
  • The popup with the error message does not stay open when an error is found during the address upload.
  • Dates were difficult to enter on the Recurrences because they kept erasing. The only way to add dates was to use the calendar.
  • On the Route Plan, when using the same Zone name or same Recurring Route, the information would appear multiple times when retrieving through the API.
  • Changes to the Driver were not flowing on the Driver Search.
  • When an ETA recalculation is requested but Optimizer sees it has new Orders to process, a full optimization will be done instead.
  • Using the PUT/api/v1/orders/{orderId}/driverpayout endpoint, it was possible to change the Driver Payout on a settled Driver on the Order. This will no longer be available in this version.

Bug Fixes included in this release

  • When a user logs in on the Driver App, only Scanning and Settings tabs are available. User is automatically on the Scanning tab but the Home tab header was displayed. This is now fixed and will show the Scanning header.
  • On IOS, the first stop of My Run was partly cut off by the filter. 
  • On Checkpoint, when using first the damaged icon and scanning items, the damaged would stay turned on without the knowledge of the driver and all items would be set as damaged. This only happened when the first item was set as damaged.