This release includes 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:
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/


Dispatch Board

Driver list extended past the edge of the window

When an order was dispatched to a driver, the driver list extended past the window. The driver list now stops at the bottom of the window.


Held order status was displayed briefly and disappeared

When an order was put on hold, its status would briefly be changed to HL and then reverted back to the status before it was put on hold. This is fixed, the HL status will remain until the order is released or cancelled.


Lasso was disappearing on selection tool and orders

The lasso selection tool would not be visible when navigating from a Driver stop list back to the Orders list.

The order stop list would not show the orders when navigating from a Driver Stop List back to Orders and when reopening a Driver Stop List.  


Delivery charge was not always above the extra fees

The delivery charge would sometimes be displayed below the extra fees in the pricing window. The delivery price should always be at the top.


Changing the service level only showed that price is changed in history

When changing the service level in an order, only the price change would be added to the order history. This was changed to show both the service level (before and after) as well as the price change.


Back Office

Order could not be be created when an extra fee was set to Per 0

When an order was created using an extra fee schedule with an extra fee set to 0 in the Per column, the order would not be created and an error message was displayed. To fix this, extra fees will be added as Per 1 and if Per is changed to 0, an error message will be displayed in the extra fee schedule upon saving any changes.


Could not create an account with the same number on different company

When attempting to create an account on different company, could not use the same account number. In this release, you will be able to create accounts with the same account number as long as the accounts are created in different companies.


Could not delete a contact from the Account User

When attempting to delete a contact from the Account User, the confirmation message would display but the contact was not deleted. 


Changing the service level only showed that price is changed in history

When changing the service level in an order, only the price change would be added to the order history. This was changed to show both the service level (before and after) as well as the price change.


On Firefox, icon displayed incorrectly

When using Firefox, the icons were displaying incorrectly. The new icons now show correctly in the Back Office and Dispatch Board.


Account API

Stop Order with Get Order Status

The Get Order Status returned the pickup and delivery stop position from the overall list of orders rather than the order for each driver. 


Creating an order with an invalid service level

When creating an order with an invalid service level, the Ready at would default to January 1 0000. This has been changed. Even if the service level is invalid, the Ready At will be used on the order.