New features included in this release
Order grouping in Dispatch Board driver stop list and in the Driver App stop list.
Cascading Price Lists.
Changes to ETA report and ability to select all drivers.
Tenant API create drivers, checkpoint.
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.
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/
Driver App version
Version 1.11.446 contains the new features for this release. Please see Release Notes for Driver App Version 1.11.446.
Driver ETA Report
In the Driver ETA report, only the list of drivers who have orders assigned to them now display in the list which will allow you to use the Select all checkbox.
A new column was added to the Driver ETA report to show the name associated to the Delivery under the column Delivery Name.
Setup Order Grouping Option
Grouping options can be setup in the Account Profile.
Upon deployment, to keep the Pickup grouping as is on the Driver App and in the Dispatch Board, the pickup option will be set to Based on Address Line 1 and there will be no delivery grouping.
This can be changed in the Account Profiles as needed.
Order stops can be left ungrouped or grouped for pickup and/or delivery stops. The grouping is done first by Account and secondly by the Address Line 1 or a combination of Address Line 1 and 2.
Orders which are setup with an ID identification and/or COD will not be grouped regardless if they have been setup to be grouped in the Account Profile.
Another option is visible on the Account Profile but will not be used right away: Can change grouping when creating order. This option will be taken into account when the change is made in the New order screen in the next release.
1) Open the Account Profile by selecting Accounts then Profiles and click
2) Open the profile from the Profile list that should be modified:
3) In the Account profile, scroll down to the Grouping Option section and select the pickup and/or delivery options:
No Grouping: All orders will show individually
Based on Address Line 1: Orders are grouped by Account+Address Line 1.
Based on Address Line 1 and 2: Orders are grouped by Account+Address Line 1+Address Line 2. If a different address line 2 is used on 2 orders, these will show ungrouped. This will be used when picking up/delivering to the same building but different offices for instance.
Note: The grouping will be not be done on any order setup with an ID verification and/or a COD.
4) Click on Save when completed.
Note: Only orders created after the modification to the Account Profile will use the new grouping. Existing orders will not be affected.
Delivery contact name added to Driver ETA Report
The delivery contact name was added to the Driver ETA report.
Customer Notes on Order List
The order customer notes have been added in a column between Number of Pieces and COD on the Order List.
The fuel surcharge can now be entered with 2 decimals.
Pricing zones will have the same rules as the auto-dispatch/filtering zones where zones can be named using letters, numbers and an underscore. Using any other characters, including a space, will result in the zone not importing to the zone layout as this was creating issues in the price list.
Fixing zones in a zone layout
1) Download the price list associated with the zone layout.
2)Open Pricing section, open Zones, select a zone layout then click on Download File.
3) The file will be downloaded. You can import this file in Google My Map, rename all zones to remove any special characters including spaces.
You can also open the kml file in a text editor and do a search for <name> and search next until you see the first Placemark zone name. You can then remove any special characters including spaces from the name:
Save the file.
3) Click on Choose File, select the modified kml file then click on Import KML File.
4) Download your price list again, copy the missing information from the price list you downloaded in step 1. Save the file and reupload.
Modification to Extra Fees User Interface
The Extra fees user interface was modified in this release. The extra fee schedule is available from the Extra Fees menu. The Extra Fees management can be access from a link in the Extra Fees.
Extra Fee Schedules are now available under Extra Fees menu.
The Extra fee management can be accessed through the link Manage Extra Fees.
To return to the Extra Fee Schedule list from the Extra Fees Management screen, simply click on the breadcrumbs:
Cascading Price Lists
The failover price list has been modified to allow selection of any price list (zone or distance) from any price list (zone or distance) as long as they use the same Service Schedule and the price list has not been used in the chain.
The price lists can now fail over to a chain of price lists until it either reaches the end of the chain or finds a price.
Set Cascading Price Lists
1) Open a price list and notice the Failover price list field is available.
2) The failover drop down list will contain the price lists that are using the same service levels and that have not been used in the chain containing the current price list.
3) Once the failover price list is selected, click on save.
Using Cascading Price Lists in Orders
When an order is created, the price list associated to the account will be used to find the price of the delivery.
If no price is found in the first price list, it will use the failover price list selected.
If no price is found in the failover price list, the next failover price list will be used. It will go through failover price lists until it finds a price or until there are no other failover price list. In this case, the price will be null and show as an invalid price.
Using Cascading Price Lists on Reattempt
When an order is put on hold and, from the Dispatch Board, the dispatcher selects to release the order using the Reattempt, Dispatch Science will attempt to find a price in the price list associated to the account or along the failover price lists until it finds a price for each reattempt service level or until it reaches the end of the chain.
Delete a Price List Used as a Cascading Price List
If you attempt to delete a price list that was used as a cascading price list, the price list will not be deleted and an error message will be displayed, indicating where it has been used.
Open the price list, remove the failover selection and save. You will then be able to delete the price list.
Drivers can be created from the tenant API.
For documentation, please follow this link: https://api.dispatchscience.com/reference#drivers.
Checkpoint status update
The checkpoint scanning has been added as a status update when using a webhook.
Checkpoint status update
The checkpoint has been added as a status update when using a webhook and subscriptions.