Bug Fixes for Version 1.76

Modified on Tue, 14 Apr at 4:20 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

BackOffice — Orders

  • Language not validated when importing addresses
    When an internal user imported hub addresses, the language field was not validated against the tenant's configured languages. Addresses with unsupported languages were imported without error.

BackOffice — Drivers

  • Error when deleting a driver document type
    An error was thrown when attempting to delete a driver document type from the configuration screen.

Dispatch Board — Map Board

  • Rainbow and Home icons disappeared after board refresh
    The Rainbow and Home icons on the Dispatch Board vanished after a browser page refresh.
  • The grid board did not allow selection of the last row with SHIFT only

Orders — Recurrences

  • After-Hours and Holiday extra fees not applied on orders created via recurrences
    When orders were created using recurrences, after-hours and holiday extra fees were not automatically added even when the service level was configured to allow them for the full off-hours window.

Bug Fixes Included in Version 1.75 After Release

BackOffice — Orders

  • Transactions page displayed incorrect amount
    The transactions page was not displaying the correct monetary amount for certain transaction types.
  • Auto Dispatch — suggested orders list cleared after accepting or dismissing one
    When the optimizer suggested multiple orders for a driver, accepting or dismissing a single suggestion caused all other suggestions to disappear until the next optimization cycle.

BackOffice — Drivers

  • Error when trying to add attributes to accounts or drivers with large attribute sets
    Tenants with a very large number of attributes (400+) experienced errors when saving attributes on accounts or driver profiles. The system now supports up to 1,000 attributes.
  • Unable to search by driver number in the dispatch dashboard
    Users could no longer search by driver number on the Dispatch Board or BackOffice Drivers page. The search field UI has been corrected to accurately reflect which fields are searchable, and driver number search is restored.

Dispatch Board — Map Board

  • Entering characters into the board search field caused unexpected behaviour
    Typing in the search field on the Dispatch Board triggered unexpected UI behaviour.
  • Orders would sometimes show At Risk when they were not

Platform & Infrastructure

  • Audit system did not detect certain un-audited POST endpoints
    Two endpoints using the AcceptVerbs attribute were not flagged by the automatic audit detection system, causing them to be missing audit attributes. This has been corrected and the relevant service level configuration endpoint is now audited.

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