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

• When changing to Rates or Addresses while editing a Recurrence and clicking on Discard, the Recurrence and Default Driver and exclusion calendar on the template were blanked even if they had not been modified.
• On small windows, the Driver Deduction/Additions did not show properly.
• A delay was added before printing the invoice when invoices are generated to prevent getting blank invoice reports.
• When creating or editing Accounts through the API, the BillingMethodOption was not validated.
• On Recurrences and Recurring Orders, checking the Override on a template showed with filled in default values but the values were not there. This prevented the save button to be enabled.
• When editing an order template, if the price became invalid, it would show as invalid but would still display a message that the other price was kept even if this was incorrect. The message has been removed.
• When the add charge or the override delivery charge or the update order charges was used on the Integration-Tenant API, multiple delivery charges could be added if the calls were done at the same time. A validation will now prevent the addition of multiple delivery charges.
• The Delete button on Order Template segment was removed since only the Multi-segment Order template can be deleted along with all the segments.
• Internal users do not need to have edit access to the Order to update Exception codes as well as internal note on the Order as long as they have edit access to those permissions as part of their roles.
• When a Account admin with view to the pricing duplicated an order that had overriden extra fee prices, the prices would show as they were in the original order but were then changed once the order was created. When duplicating Orders now, all extra fees will be recalculated so the Account admin can see the correct price on duplicate.
• It is no longer needed to add the Address section when creating Drivers through the Integration-Tenants API.
• Time differential property was causing an error when validating and saving a Content Template.
• Error displayed when accessing Addresses when user only has the Addresses right under Settings.
• In some cases, the POD report would not show with the signature because the report was generated before the signature became available. A 1 minute delay was added before POD report generation to ensure the signature is available.
• With Suggested Auto-Dispatch, the dispatcher did not get a warning if another dispatcher had already dispatched an suggested Order to another Driver. 

Driver App Bug Fixes included in this release

• When Driver created new Orders and selected a contact linked to a geofence, the geofence was not included.
• When editing a license plate that already exist and scanning the Yes instead of selecting, an error was displayed.
• In Dark Mode, the widget did not show all information. Some of the writing was invisible.
• If Login request timed out while logging in, the Driver App was set as offline which caused problems on the next login. The Driver App will not go to offline mode unless the Driver is logged in and in the App.