Bug Fixes for Version 1.71

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

• Dispatch Board:
  • Addressed an issue where the driver icon incorrectly displayed at position (0,0) on the vertical board with the map when the driver went off duty or offline.
  • The Created By field on the Grid Board now correctly displays the user's name instead of the login.
  • The Driver status end time was not displayed on the Map Board sliding Driver panel.
  • Resolved an error that occurred when moving an order to a route using a specific route plan and container while selecting the "Use Configuration" option on the route.
  • Resolved an issue where the description entered when setting an order or multiple orders at a checkpoint was not displayed in the order history.
  • Fixed an issue where modifying an order after updating an account's service level schedule did not correctly display the updated vehicle type and service level. Now, the vehicle type and service level reflect the new schedule. Additionally, users will see the full list of service levels from the new schedule, including the previously selected service level, as well as the updated vehicle list, including the previously selected vehicle.
  • Resolved an issue with the filter Contains on the Created By column.
  • Rights to set an order as delivered gave access to to set as picked up as well.
  • In some case, when opening a driver on the Map board, the list of Drivers would resort. 
  • Resolved an issue where horizontal signatures were truncated in the Map Board Order Details.
• Transaction List:
  • Dates in Transaction list showed in the computer time zone instead of the logged in user time zone.
• Orders:
  • Resolved an issue where user fields were not correctly populated when uploading orders via the Dispatch Science import, tenant, or integration API for accounts using Order Profiles with Rules, if the selected profile was not the default.
  • Resolved an issue where the COD amount and partial payment option were not saved when creating an order using an order template with COD.
• Roles:
  • Previously, the Role Driver History required Edit access to the Driver. Now, it only requires View access to Drivers to have access to the Driver History button in the Driver Details.
• API: 
  • Resolved a 500 error that occurred when attempting to delete orders associated with a deleted route.
  • Using the Quote endpoint in the API could block the Account.

Bug Fixes included after version 1.70 was released

• Issues resolved on the DIspatch Board Grid and Map:
  • Drivers were not always visible after coming online and on duty when clicking to open the sliding panel.
  • Unable to enable the lasso tool on the Grid Board map.
  • Refreshing the Map Board in some cases resulted in an empty driver list and driver stop list.
  • Multi-segment orders only appeared when the "Routed Orders" option was enabled on the Grid Board.
  • The Grid Board order list did not clear filters when using "Reset Grid" if the filter included a date field.
  • Order pricing info (i) in the Board Map Order details did not reflect updated information.
  • The Driver Grid in the Dispatch Grid Board failed to load data when "Show Orders Under Drivers" was enabled and no columns were selected.
  • On the Order Details slide panel, the pricing information (i) tooltip was empty after an order status update.
  • The triple-panel Grid Board map could become unsynchronized with the grid when opening and closing Driver Details.
  • The Ready At column displayed an error in the triple-panel Grid Board.
  • Removing a filtered column in the Dispatch Grid Board caused the board to display as empty.
  • Accepting a suggestion from the Dispatch popup did not save the information correctly.
  • The link to Back Office Order details failed to open the order.
• Issue fixed on the API:
  • Orders could be set as "Verify Before Invoicing" through the API, even when the account was configured with an "After Delivery" billing cycle or used pre-authorization.
• Other issues fixed:
  • In the Transaction List, invoices and debit notes were missing menu entries when filtered as Partially Paid.
  • The Transaction List incorrectly displayed unapplied adjustments as Partially Applied Apply or Unapplied Payment.
  • No popup was displayed to indicate a pre-authorization when an order template was created simultaneously with an order.
    

Bug Fixes included for Driver App version 1.70

• In offline mode, drivers were able to place the same order on hold multiple times. This issue has been resolved.
• Drivers were unable to add an item at a checkpoint if the order was not dispatched to them. This has now been fixed.
• In certain scenarios while operating in offline mode, attachments may have synchronized with Dispatch Science before the associated order has been updated with the work completed by the driver.
• Previously, when a driver selected "When in Use" for location permissions and then answered "No" to the prompt asking to allow location access at all times, the Driver App could enter an infinite permission request loop. This issue has been fixed.