This release includes several new features and bug fixes as well as overall stability improvements. 

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.

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.

Dispatch Board

Cannot see driver order list

The driver order list in the dispatch board could not refresh when an order, created from the API, with a Ready At date-time later than the Delivery window date-time was assigned to a driver. 

The API will no longer be able to create an order with a Ready At later than the delivery window. If an order is created from the API with this error, the Ready At will be changed to match the Drop off window start. If no Ready At is sent when the order is created, the Ready At default to the date-time of the order creation. If this date-time is after the Drop off window end, the Ready at will be changed to the Drop off window start.

Dispatching to another driver from the driver order list does not dispatch

In the driver order view on the Dispatch Board, you were able to use the lasso to select orders and dispatch to another driver. Although the move seemed to be successful, the orders were not transferred to the new driver.

Menu shows 2 lines when order is on hold

When an order is on hold, there were 2 separators showing in the ... menu.

Performance

Performance was improved on the Dispatch Board when hundreds of orders were displayed.

Optimization

The Optimization model was improved.

Driver App

Cannot see My Run

My Run could not refresh when an order, created from the API, with a Ready At date-time later than the Delivery window date-time was assigned to the driver. 

The API will no longer be able to create an order with a Ready At later than the delivery window. If an order is created from the API with this error, the Ready At will be changed to match the Drop off window start. If no Ready At is sent when the order is created, the Ready At default to the date-time of the order creation. If this date-time is after the Drop off window end, the Ready at will be changed to the Drop off window start.