Bug Fixes for Release 1.4

Modified on Fri, 5 Apr, 2019 at 3:45 PM

This release includes several new features and bug fixes.

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.

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/


Back Office

Error when weight is too large

Allow a weight of 0 to 1000000000 when creating an order.



Show error when a fuel surcharge is created without any vehicle

Do not allow to create a fuel surcharge without a vehicle, show an error.


Cannot add an email address for Account user created by CSR

If an account user was created by the CSR on the create order, the email address could not be added to the user profile.


Long email addresses leaked in the Create By column in Order list

When an account user had a long email address, the email address in the Created By column would leak into the Create At column in the Order list.



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