TABLE OF CONTENTS

• Enhancements
  • Manage Accounts in ADP
  • Calculate distances and drive times by road network
  • Search for orders
  • Load Predefined Routes & Apply Fixed Route Sequences
• Issues Resolved

Enhancements

Manage Accounts in ADP

You can now view and manage customer accounts directly in Appian Daily Planner (ADP). You can create a new account, edit existing accounts, geocode accounts, and duplicate accounts. You can also set a primary account (known as Load Default in DRTrack), which allows you to select default account values to automatically populate when creating a new account. Newly created accounts and edits to existing accounts are stored in the corresponding DRTrack account tables. 

Calculate distances and drive times by road network

A new Distances feature allows you to generate commercial-vehicle road distances and drive times between as many as 50,000 locations in a few minutes or less. Located in Preferences > Algorithm > Distances, the feature allows you to select a vehicle profile so distances and drive times are based on the type of vehicle being routed, and the region (North America or Europe). (Please note these distances cannot be edited.)

Search for orders

You can now search orders on a branch with the order search bar next to the date selector in the header. You can search by OrderID, Account ID, Account Name, Address, City. Unloaded orders can be dragged directly from the search results onto a route.

Load Predefined Routes & Apply Fixed Route Sequences

Some fleets operate fixed routes that are stored in their ERP. Daily Planner can build new routes while taking these fixed routes into consideration. At the order level, you can pass a Stop User Field titled FixedRt that contains the route the order should be placed on. If an order’s FixedRt value matches a TruckID, then that order will be placed on the matching truck. This works for previously created routes or new routes built in the Route Building Wizard. 

You can also pass a User Field titled FixedSeq that represents the fixed sequence of that order. The stops in the route are then sequenced according to the FixedSeq values associated with those orders. You can apply sequences to specific routes or batch apply sequences as you see fit using the Apply Fixed Sequences and Optimize button. Orders that do not have Fixed Route values associated with them will be slotted in according to the standard algorithm.

Issues Resolved

• Fixed an issue where the Unloaded Orders Suggest Routes pop-up window might show in the upper left corner of the screen if triggered from grid view. 
• Fixed an issue where the Preassignment dot hover pop-up was showing misaligned. 
• Fixed an issue where users couldn’t search via the branch drop-down.
• Fixed an issue where the switching from grid view to card view and vice versa was dismissing filters for the Unloaded Orders list.
• Fixed an issue where the Optimization > Time Limit algorithm setting displayed a max value of 20 instead of 15.
• Fixed an issue where skipped stops were showing as completed late, even though there were no actuals associated with the stop. 
• Fixed an issue where the Consolidation Settings were referencing DRTrack INI settings instead of ADP settings.
• Fixed an issue where the get stops query was sometimes causing an error if more than 2,000 stops existed on a given branch and date. 
• Fixed an issue where the order card capacity gauge calculation was including backhaul.
• Fixed an issue where cost was showing a single decimal point instead of two in grid view.
• Fixed an issue where fixed routes created in Daily Planner were not downloading to DirectRoute as expected.
• Fixed an issue where Suggest Routes was always suggesting placing a stop at the end of the route rather than where it would be optimal.
• Fixed an issue where dragging and dropping a single fixed route stop was moving multiple stops instead. 
• Fixed an issue where the individual route toggle button did not work in grid view.
• Fixed an issue where the lasso tool would zoom out on the map after creating a selection polygon.
• Fixed an issue where a boundary code error would appear for a user if a fleet solution was built with boundaries and then routes were deleted.
• Fixed an issue where the lasso tool on the Fixed Routes page would create a new route but not load the selected orders.