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

  • In some cases, the Export button would become visible on the Order List and this prevented the Order List from being loaded correctly.
  • When Driver picture was rectangular instead of square, the aspect ratio was incorrect.
  • If Account name was very long, on a Grid Board, when filtering Accounts, the Account name would overlap and it was not possible to see the Account Name. Long Account names now have an ellipsis and name is shortened.
  • When Account user/admin had Edit access but no Delete permission on the Order Templates, the Delete button was visible in the Order template details page. User would get an error message when clicking and template would not delete. The button is now hidden.
  • When Account user/admin had View Access and Delete permission on the Order Templates, the Delete button was not visible on the Order template details page. The Delete action can now be done from the Order template list through the delete icon and in the Order template details through the Delete button.
  • On Grouped Orders containing Orders with no inner-outer KML files and with inner-outer KML files, the notification for Driver arrived at stop was sent for all Orders as soon as the Driver entered the largest inner KML file.
  • The KML file was not attached to the Order pickup or delivery address when KML file was added during order creation. 
  • When Internal user had view access to Drivers, the New Driver button was visible. User would receive an error message when they clicked on the button so they were not able to create a Driver. This was fixed by removing the New Driver button if internal user only has view access.
  • When Orders were created through the API with an invalid Service Level/Vehicle Type, in Dispatch Science the Order would show without a Service Level/Vehicle Type and with an invalid price however, when getting the Order through the API, the invalid Service Level/Vehicle Type would be returned in the Order.
  • When duplicating Orders whose delivery charges have been overridden, the overridden charge was displayed but when order was created, the charge was recalculated. This was fixed to show the calculated delivery charge when order is duplicated.
  • Segments were not always visible when they were on different dates in the Grid Boards and filter was changed from one day to the next.
  • The pickup signature URL was missing in the proof_of_pickup subscription. 
  • Some of the code in the Notification editor was breaking because the editor was encoding it. This was resolved by preventing the editor from encoding/decoding after saving and re-opening.
  • Driver name was not updated in the Chat once updated in the Driver profile.
  • When Driver was edited, if the address associated with the Driver did not have a geolocation, the Driver information would not be saved and no error messages was displayed.
  • When Orders were moved to Routes from the Dispatch Board or Board Grid, an error was returned if the route container selected was empty.
  • Pill in Driver Stop List on Dispatch Board did not take into account time zones.
  • On the invoice, the secondary language tax name was used instead of the primary.

Driver App Bug Fixes included in this release

  • When the first stop on the Driver App was a grouped Order, if another Order that would fall in that same group was dispatched, the Next Stop on the Home screen would not reflect the new number of Orders in the group. 
  • When dispatching Orders in the Driver App, in the search for Drivers, when Driver App falls offline, the message was Something went wrong when it should have been Action is not available when working offline.
  • When viewing documents or certificates while offline, the message was Something went wrong when it should have been Action is not available when working offline.
  • The Pass/Fail on visible Certification would show as if they were updatable when they were only visible. 
  • Logged in as an internal user with access to Warehouse, an error would be displayed when moving to the Settings tab.
  • When scanning items in the Warehouse module, the barcode would scan but the order panel would not display.
  • In older version on iOS, when Driver App was deemed too old and needed to be updated, the Driver was not sent to the correct link in the App Store. This has been fixed in version 1.63.
  • When adding an item during pickup/delivery with a workflow without Barcode Scanning step, the App would crash.
  • The App would crash when resuming pickup/delivery scan while the What's new was displayed on Home.
  • The Camera permission was not asked at the right time.