Bug Fixes for Version 1.70

Modified on Thu, 6 Feb at 6:19 PM

Definition

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:https://api.dispatchscience.com/
Tenant API: API provided to you to create orders for your accounts, retrieve invoices and change invoice status. For documentation, please follow this link: https://api.dispatchscience.com/  


 

Bug Fixes included in this release

  • Opening the Driver workload from the Dispatch Board Map did not show the workload line, user had to move the slider to update the view.
  • Number localisation was missing on the Transactions batches when working in French, numbers showed with a period as the decimal rather than the comma.
  • Orders created through Import were able to use a reattempt service levels. This will not be allowed, the Order will not be created and an error message will be added to the log.
  • On the Dispatch Map Board in the Order list and the Order details, clicking on  did not open a new tab with the Back Office Order details.
  • Transactions status sort was not in alphabetical order
  • Transactions status filter list was only alphabetical when it needed to be by the greater number of entries in each status then by status.
  • When changing the mileage on an Order through script, the Fuel surcharge commission on the Driver was not recalculated automatically when, in the script, the recalculate order was performed.

Was this article helpful?

That’s Great!

Thank you for your feedback

Sorry! We couldn't be helpful

Thank you for your feedback

Let us know how can we improve this article!

Select at least one of the reasons
CAPTCHA verification is required.

Feedback sent

We appreciate your effort and will try to fix the article