Bug Fixes for Version 1.74

Modified on Tue, 2 Dec at 2:08 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

Order List and Order Details

Could not change the driver on an order created from an order template with a default driver. The previous driver was saved with the order.
When the order template contained a service level that did not match the case, the order created with that order template did not have the service level selected.

Self-Serve

Contact was created twice when account was set with a parcel rule that was not met and add contact was checked.

Accounts

Unable to search in Accounts list with a special character.
When copying an order profile with grouped steps, the grouped steps did not show on the Driver App.
When users from an account associated to a Master Account had its account removed, the user would still have access to that account until they disconnected. If an account is removed from a Master Account, all users are disconnected to ensure they no longer get access to the removed account. Furthermore, clicking on the user on an Order from an account other than the user account opens the user information in their own account.
The Account Profile Copy and Delete buttons were too close and a user could easily click on the delete while trying to copy.

Dispatch Grid Board

There was an issue when scrolling with the wrap option setup. This was fixed by setting all rows to a specified height when the option is checked in a grid board.
When clicking on the Driver link on the Order sliding panel, it now brings you to the Driver tab on the order in the Back Office.
When attempting to move cancelled or delivered orders to a route, the error message was not explicit. This was changed to show the reason why the order was not moved.
Phone number with area code in brackets was missing the area code when viewing the driver list on the Map Board.

Settings>System

When validating a disabled script, it shows enabled. This was only a visual glitch.
In the Application log, the date filter did not return the information as specified.
In the Application log, the created at filter did not return the information when using OR

API

When creating an order through API (Tenant or Integration), contrary to the service level, the vehicle type id is case sensitive causing invalid price on an order when the vehicle is not in the same case as in the price list.

Bug Fixes deployed after version 1.73 was released

Order List and Details

In some cases, delivered orders could be moved to a route which caused the order being reactivated.
In cases where a driver extra fee schedule was used with no account driver extra and was added at creation, the commission on the driver extra fee was not taken from the driver extra fee schedule.
Driver payout used the Account price list calculated price if the delivery price was overridden on the order when Account driver and driver were not associated with a price list.
In some cases, duplicate orders were created from Recurrences.
When opening a linked order then opening another linked order, sometimes the linked order would be from the previous order.

Dispatch Board

On the map board, it happened that the driver sliding panel was blank when clicking on a driver.

Self-Serve Portal

The Print label was no longer available from the Order list menu.

OData

The download link provided in Odata under InvoiceDetails was not valid,

Audit Logs (under Settings"System>Application Log)

When more than one application was selected in the column filter, only logs matching the first application would be displayed.
Incorrect coordinates showing in the Audit log for Checkpoint latitude and longitude update.

Integration API

Reference numbers were displayed twice on the returned body of a quote creation.

Tenant API

Error 404 was returned when attempting to get contact information
- GET /api/v1/accounts/{accountId}/contacts
- GET /api/v1/accounts/{accountId}/contacts/{contactId}
- GET /api/v1/accounts/{accountId}/users/{userId}/contacts
- GCET /api/v1/accounts/roles
- GET /api/v1/accounts/{accountId}/contacts/nearby
Closed orders could be moved to routes through the API.

Bug Fixes in Driver App

When uploading attachments using a name with a date and time, the attachment would upload but not link to the order.
When adding exception codes on grouped orders, the codes do not display until a refresh is done.
Adding items in the Driver App for an order on an account with a blank profile would prevent scanning multiple items.
With orders on accounts with a pickup or delivery COD step where no value was entered in the COD at creation but added on edit, the COD step would not display on the Driver App when picking up or delivering the items.
On a grouped step using signature, there was no Report on the signature. If Picture was the first step in the grouped step, could not get out of the workflow.
On iPhones Pro, when scanning a document, document would zoom too much.