Route Planner On-demand 24.07 is available as of July 29, 2024. This release includes new features, enhancements, and resolved issues. Reference the ticket number in parentheses if you have any questions about the respective items to the support team.

IMPORTANT - PLEASE READ
Be advised of the following important information concerning this release:

• Microsoft® Internet Explorer: As Microsoft has announced the end of support for applications and services on Internet Explorer, the browser is no longer supported for the Descartes® Route Planner On-demand application. The browser can be used, but new functionality may not work. Please use Google™ Chrome or Microsoft Edge as the preferred internet browser to access Route Planner On-demand.

• Supported Versions: Versions one year older than the current version will not be supported (i.e., for 24.07, versions 23.04 and older are not supported). You can continue using versions older than one year from the current version, but critical issues with those versions will not be fixed.

Submit your enhancement idea using our Idea Portal! You can find more information and learn how to request access here.

Highlights

24.07.01

🟩 Resolved Issue: Incorrect time related data format was being generated and presented for the route GPS Start and GPS Stop fields within some of the applications standard reports such as the Route Level report. The issue has been resolved, and now the time format is sourced from configured regional settings. (1100123)

🟩 Resolved Issue: The mobile applications capture of multiple scan field data items was only partially processed and found to be incomplete within the application, as only partial (every other), related data was found shown for a stop. (1099903)

🟩 Resolved Issue: On occasion, the processing of an optimization result set would fail upon generation of an exception. The exception was caused by the result dataset containing a shipment that is no longer present on the respective delivery day within the application. (1098457)

🟩 Resolved Issue: Users could not configure all available vehicles in an Optimization Schedule when the active vehicle count exceeded 64. This issue prevented the selection of all vehicles to be considered as part of a scheduled optimization. (1093846)

🟩 Resolved Issue: Shipment file uploads containing complete route-related data were taking longer than expected to process. This issue was caused by duplicate recalculation calls made during route creation, as it was waiting for the process to compete prior to moving on to the next record. (1090914)

🟩 Resolved Issue: The Regional Settings page incorrectly displayed the incorrect time format value (Long Time format) for the configuration of how time-related information should be shown and utilized by the application. The issue has been resolved by reinstating the Short Time format for configuration. (1089934)

🟩 Resolved Issue: The Scheduling Board page would momentarily freeze and log an error when users changed their location to another they had access to. (1088434)

🟩 Resolved Issue: The map displayed an incorrect view after changing the delivery date. When users enabled and then disabled a view (e.g., Show Traffic), the view behaved correctly. However, after changing the delivery date, the previously disabled view appeared as if it were still enabled. (1085717)

Enhancement: The Scheduling Board module has been optimized to improve data loading performance and reduce processing times. Various adjustments and refinements have been applied to features and functions, addressing inefficiencies in methods that previously caused delays, particularly when loading shipment grids and handling when multiple users access the same dataset. (1084697)

🟩 Resolved Issue: Icon colors were not displayed correctly when configured as part of an Icon/Depot Display definition. This occurred when the 'Try new map' and 'Enable clustering' features were enabled. (1069893)

24.07.00

🟩 Resolved Issue: An incorrect shipment state value of 'OPTIMIZED' was found associated and displayed within its history when shipment was found assigned to a frozen route and optimization action executed against remaining unassigned shipments found present on delivery day. However, the respective data was not sent onto the engine as expected for frozen-route shipments. (1079490)

🟩 Resolved Issue: Stop route positions were not calculated as expected when the Split Stop function was executed for an order found assigned to the Start Depot stop. This incorrectly occurred for all routes, thus causing issues with stop positions and incorrect sequences when assigned shipments happened to be updated. (1075635)

🟩 Resolved Issue: The Selected Summary tooltip failed to generate and display on the map in Map View on shipment selection as expected when the 'Try new map' feature was enabled. Specifically, this occurred when the General Display > Show Selected Summary setting had been configured as Simple Summary. (1075446)

🟩 Resvolved Issue: Customer attribute-related fields were incorrectly missing from the Customer Management> Add Customer page. However, the fields are displayed correctly on the Edit Customer page upon redirection after the save action is performed. (1075015)

🟩 Resolved Issue: Attribute-related data was incorrectly being cleared out when uploading Fixed Routes into the application. This occurred when attributes were not found contained in the upload file nor mapped on the respective parser page, causing them to be considered and updated to an empty (null) value. (1071122)

🟩 Resolved Issue: The "Some existing routes are not selected. Do you want to optimize selected routes only?" message was incorrectly shown to users. This occurred when optimizing a day with prebuilt routes using the 'Keep Existing Routes and Insert Shipments' option and a subset of available, used, vehicles selected. (1071104)

🟩 Resolved Issue: Incorrect time value was supplied in the export for the Route Last Update Time field. This occurred regardless of whether the "Outputtimestamps in UTC" setting was enabled. (1070964)

🟩 Resolved Issue: An error was generated and shown when a user attempted to clone an export definition. This occurred when no changes other than the export name were made, resulting in an incomplete clone with missing column mappings related to the presence of field data and/or attribute items. (1070416)

🟩 Resolved Issue: Icon sizes were not displayed correctly on the map in Map View when the 'Try new map' feature was enabled. The 'General Display > Icon size to set' setting was not applied as configured. (1069844)

🟩 Resolved Issue: Users could not navigate and scroll around the map as expected as a shipment remained selected with the 'Try new map' feature enabled. (1069767)

🟩 Resolved Issue: Attribute-related data was missing from the Choose columns selection list for display configuration on certain pages within the Deliveries section. The following pages have been corrected to include the missing data, similar to the logic found in Map View: (1069647)

• Deliveries > View Routes > Deliveries View Routes Columns

• Deliveries > View Route Detail > Deliveries View Route Detail Summary Columns

• Deliveries > Dispatch > Deliveries Dispatch Route Columns

🟩 Resolved Issue: GPS Service/Departure Time data was incorrectly calculated, showing the driver departing a stop earlier than they actually did. This issue occurs when multiple stops are found close to each other or at the same physical location (latitude, longitude), causing overlapping geofences and incorrect evaluation of GPS points for each stop. (1069520)

🟪 Enhancement: The Deleted Shipment event trigger was updated to exclude the generation and transmission of data onto the host system when shipments are deleted due to the Data Retention Policy and purging of old delivery days. (1067004)

🟩 Resolved Issue: Inconsistent behavior occurred when using the range parameter for the Export Delivery Day URL call. When the range parameter was set to zero, the system behaved differently depending on whether a location was found specified. If a location was specified, data was provided as expected, but if no location was specified, no data was provided, which was incorrect. (1064348)

🟪 Enhancement: Added support of Commodity Code rules for compartment planning, allowing the configured rules to be retrieved and utilized within associated functionality. Previously, this functionality was only available for shipments at the vehicle level. This extension ensures that configured details are generated and included in the optimization and sequencing actions performed on the respective dataset. (1064049)

🟩 Resolved Issue: Users were unable to create new Report Schedules due to an incorrect Location/Region validation error. When selecting a report, the 'Select Location/Region' option was replaced with 'Location Selection,' causing the error. (1063915)

🟩 Resolved Issue: There were some issues with the display of an exception associated with the assignment of helpers: (1062312)

• The Helpers route level column incorrectly showed red, indicating an exception when no helper(s) were assigned and a driver exception existed. The Helpers column exception was tied to the Driver column for violation display.

• Users were unable to assign a resource (helper or driver) to a route after changing the driver, as the Assign Helper window did not correctly display the dropdown selector.

🟩 Resolved Issue: The application did not correctly use configured commodity code rules for transfer orders during shipment planning, optimization, or route sequencing. Routes were planned with commodity code violations, and products were incorrectly mixed when transfer orders were present. (1061553)

🟩 Resolved Issue: Users were able to view shipments not linked to their Delivery Company when transfer orders were initially submitted. This issue has been resolved, and now shipments are correctly removed from view when the Map View page is refreshed as expected. (1061504)

🟩 Resolved Issue: Users were not able to edit and input any value with a zero (e.g., 0, 10, 20) when modifying the Fixed Route group presentation order in the Fixed Routes & Territories module. (1058148)

🟩 Resolved Issue: The 'Compartment Capacity Exceeded' alert was incorrectly shown in Map View when manually assigning shipments to a route. This alert disappeared after running the sequence action for the same route. The issue was due to the incorrect evaluation of capacity-related shipment metrics when not found set and configured for compartment(s). Compartments with a capacity of zero or none are no longer evaluated against the respective metric. (1057412)

🟩 Resolved Issue: Driver user accounts created via file upload did not appear in the Change Driver selection list as expected. This issue occurred when drivers had access to multiple locations and were attempted to be assigned to a route that was not found in their default location. The issue has been resolved, and drivers are now available on the drivers' list in Map View. (1055851)

🟩 Resolved Issue: The 'SELECTED ROUTE' tab in Map View incorrectly showed the 'Vehicle Capacity Exceeded!' exception alert text when the exception was inactive, regardless of whether the associated metrics (e.g., piece count, weight, volume, dimensions) were exceeded. (1054359)

🟩 Resolved Issue: The application incorrectly generated and displayed a notification about dispatching the same customer on another route. This occurred when the 'Enable merge option when shipment's customer is already assigned to another route' setting was enabled, and a shipment was reassigned from one route to another from the All tab on the Deliveries > Dispatch page via click-and-select. (1053480)

🟩 Resolved Issue: The following issues with the 'Change delivery date' feature on the Deliveries > Dispatch page have been fixed: (1053363)

• The window for changing the delivery date did not show options to specify the date.

• The tooltip icon name was changed from 'Move' to 'Change delivery date'.

• The icon to move/change the delivery date was incorrectly active when the control parameter to change delivery dates was disabled.

• The Unroute icon was incorrectly enabled for unrouted shipments, prompting a useless verification.

• Selecting multiple shipments using the Ctrl key and right-clicking to generate a context menu produced a system error.

🟪 Enhancement: The following changes were made to the Display configuration parameters: (1050272)

• Moved the 'Include DC Stops' setting to the Configuration > Parameters > Route page and renamed it to 'Include DC Stops in stop count'.

• Moved the 'Highlight reload depot stops' setting to the Configuration > Parameters > Route page and renamed it to 'Highlight Depot stops in route detail'.

🟩 Resolved Issue: Exception alert text was missing for some options when enabled to show violations encountered during route planning based on configured settings. This occurred for the following: (1047398)

• Violation if the total distance exceeds the specified amount.

• Violation if the total duration exceeds the specified amount.

🟩 Resolved Issue: Customer record time windows were incorrectly updated on orders manually created via Order Management. Customer time windows can now only be updated via the Customer Management module or through integration (i.e., upload, API). (1046810)

🟩 Resolved Issue: An error occurred when attempting to access the View Vehicles page (Configuration > Vehicles) in certain scenarios. The error was related to the sorting of the vehicle list. (1046792)

🟩 Resolved Issue: The application did not retain the view map settings like Show Traffic and Show Vehicle Restrictions when changing the delivery day in Map View. (1046746)

🟩 Resolved Issue: Geocode data (latitude and longitude) was not correctly set for new customer records created when changing a shipment's origin to another location using the 'Change Depot Association' functionality with the 'Allow multi-location depots in change depot association' feature enabled as well. (1043297)

🟪 Enhancement: Added the ability to restrict multi-location depots in the Change Depot Association options list to only show options based on the user's configured location access. A new setting, 'Restrict multi-location depots to user location access', allows users to move unrouted shipments only to locations they can access. The default setting is disabled (off). (1042135)

🟪 Enhancement: Added support to include Stop Customer attributes for Depot Transfer Order types sent in the route XML to Descartes wGLN. When Stop Customer attribute data is set for depot-to-depot transfer orders, it is displayed in the application user interface and now correctly included in the route XML generated and sent to wGLN. (1042124)

🟩 Resolved Issue: Optimization incorrectly inserted 0-minute wait stops into routes. This occurred when the Sequencer/Optimizer profile was set to use Start Time Window Deviation, a time buffer added to the time window start value, and use of the 'Variable Early/Late Route Start Time' settings. This issue has been resolved, and special stops with 0 service time are now prevented. (1041100)

🟩 Resolved Issue: The application incorrectly created a duplicate Customer Type entry when a shipment's origin was changed to another location and then back to its original location. This occurred when the 'Allow multi-location depots in change depot association' feature was enabled. (1040354)

🟩 Resolved Issue: Several issues have been corrected with the depot-related selection lists when the 'Allow multi-location depots in change depot association' feature was enabled: (1039623)

• Inactive Location depots were incorrectly shown on the Change Depot Association dropdown list.

• In the Edit Route context menu in Map View, depots from other locations were incorrectly shown in the Change Starting Depot list.

• In the Edit Route context menu in Map View, depots from other locations were incorrectly shown in the Change Ending Depot list.

🟪 Enhancement: The 'Organization' configuration abilities to include attribute data for Icon Display and Filters options in Map View and Scheduling Board have been improved. This enhancement allows configuring organization settings for attributes similar to the existing options for 'Location' and 'User' defaults. (1038203)

🟪 Enhancement: Updated the Export feature related to the 'Can Select, Generate and Optional Delete of Unrouted Shipments?' setting. Users can now configure and control the deletion function during the export of unrouted shipments, eliminating the user prompt and confirmation. A new option, 'Can Delete Unrouted Shipments on Export,' was created. (1038173)

🟪 Enhancement: The Export Indicator feature has been included in the UNROUTED tab of the Shipments pane in Map View. This allows users to see which shipments have been exported back to the host system. Additionally, a new column was added to various pages (e.g., Map View, Dispatch) to show the export indicator for unassigned shipments. Hovering over the new column displays the latest export details, including the export name and date/time. Users can also utilize a newly added context menu option to generate and show historical details. (1038168)

🟩 Resolved Issue: An error occurred, causing the Routes quadrant not to display any information while updating data in Map View for certain scenarios. (1034505)

🟩 Resolved Issue: Marking a driver user record as "inactive" did not correctly sync with the Descartes wGLN. The associated driver record remained active in wGLN, thus allowing the driver to log into the Descartes Mobile application. (1034499)

🟪 Enhancement: The Exports configuration has been improved by adding a new 'Filter Results' option to the configurable columns dropdown. This feature, similar to the location selector, helps users select data fields to include in data exports. (1032449)

🟪 Enhancement: The Resource Schedule pages for vehicles and drivers have been improved by adding new options to control the display of data entries: (1032446)

• All: Display all entries regardless of their current state.

• Active: Display all "active", "in-progress", and "valid" (including future) entries. Default applied view on initial load of both the Vehicle/Driver Schedule page.

• Future: Display entries where the 'from' date is in the future.

• Expired: Display entries where the 'to' date has passed.

🟩 Resolved Issue: Creating new Schedule entries (Vehicle, Driver, and Optimization) did not correctly set the Created User-related data. Instead, it incorrectly set the Modified User data or set both the Created and Modified data. The formats for displaying the Created Date and Modified Date columns have been unified to show both date and time. (1030518)

🟩 Resolved Issue: An error was generated and shown when deleting a Compartment Profile with Properties (e.g., CustomerType, Shipment Service Type, Shipment Attribute) found assigned, which prevented the profile from being deleted. (1029150)

🟩 Resolved Issue: A large number value for the quantity field was incorrectly displayed on the View Shipment form on both Map View and Scheduling Board pages. The values were correctly shown in the Shipments pane (UNROUTED, ALL SHIPMENTS) and should now display consistently across all related views. (1027079)

🟪 Enhancement: New failure-related log entries for the Shipment Webservice are now accessible on the Diagnostics > DB Logs > Shipment results table. Previously, only successful entries were displayed, which did not provide a complete history of shipment activities. (1025292)

🟪 Enhancement: The optimization logic for the 'Keep Existing Routes and Insert Shipments' functionality has been improved. This enhancement ensures that when an existing route contains multiple depots requiring servicing, the application will correctly account for this scenario, even if the profile is not configured to allow multi-depot reloads. The application will now automatically consider the multi-depot requirement when evaluating the final result. (1025257)

🟩 Resolved Issue: The following issues found on the Configuration > Add/Edit Export page have been corrected: (1023839)

• The 'Specify roles' section was missing the 'read_only' role from the selection list, and roles are now sorted by name.

• The 'Specify delivery companies' section now sorts delivery companies by name in the selection list.

🟪 Enhancement: The Search Order feature has been improved with the following changes: (1021574)

• Changed the search page fields sequence to display order fields before customer fields.

• Updated the search results page in Map View and Scheduling Board to include options to export grid, Edit and Delete buttons, and a Shipment PDF Report hyperlink, similar to the Order Management > Search Results page.

• Limited search results to a maximum of 500 records.

• Customer fields no longer support the submission of empty search criteria.

🟪 Enhancement: Users can now retrieve related data via the Customer API. This enhancement supports the ability to obtain data from the application using the GET CRUD HTTPS command. (1020797)

🟩 Resolved Issue: Changing an address did not create a new customer record as expected on the editing of shipment, even with the settings 'Create new customer if address was updated?' or 'Create new customer if no match is found for updates?' were found enabled. This issue has been fixed. If an exact match already exists, the existing customer record will be used. (1020113)

🟪 Enhancement: Restrictions for report generation have been introduced into the application to prevent large data-intensive reports during peak operational hours, which may impact dispatching-related activities. Report generation can now be configured by Descartes administrator users to limit them by date range, time, and/or number of locations. Users will receive a message upon attempting to generate a report during the restricted period based on the settings configured. (1019124)

🟪 Enhancement: The setup and configuration of Filters to support item-level metrics in addition to shipment-level metrics have been improved. New options, such as Item Quantity, Item Weight, Item Volume, and Item Dimensions, have been added to the selection list to assist with daily planning scenarios. (1018455)

🟪 Enhancement: The On-demand SSO notification for inactive users attempting to log in has been updated. The message has been changed from 'User not found' to 'User not active'. (1017438)

🟩 Resolved Issue: The Optimize window incorrectly reappeared after selecting 'Use Current Result', which occurred when the user stopped the optimization process before the final result was completed and while peak results were still being processed. (1016242)

🟩 Resolved Issue: The following issues with the Time Window field on the Add/Edit Order pages in Order Management, Map View, and Scheduling Board were fixed: (1015566)

• The warning message "Please correctly fill in all of the red fields below."appeared without indicating which fields required attention when the start and end values were the same.

• When changing the Time Window from 'One segment' to 'Two segments' during order editing, the second segment's time values were incorrectly set to the same value.

🟪 Enhancement: Users can now update and modify existing Hold Spots on the Scheduling Board without needing to delete and create a new entry. (1015264)

🟪 Enhancement: Support for processing duplicate scan quantities from Descartes Mobile has been introduced. The application can now consume and process the Qty attribute from field data reporting. The expected format from Descartes wGLN includes the Qty attribute for each scanned barcode from the driver, which is then processed and reported in the show field data form. (1013144)

🟩 Resolved Issue: Users could incorrectly perform actions on shipments assigned to a Frozen Route: (1002220)

• Users could reassign shipments to another route template by dragging and dropping them from the ALL SHIPMENTS or SELECTED STOPS tabs in Map View.

• Users had the option to 'Unroute' shipments from the context menu in the ALL SHIPMENTS (Map View) and All (Dispatch) tabs.

• Options presented to users in the ALL SHIPMENTS (Map View) and All (Dispatch) tabs did not match the Map View stop context menu options, such as Geocode, Clone, and Edit Time Window.

🟩 Resolved Issue: In Map View, dragging and dropping a routed shipment from the ALL SHIPMENTS tab unexpectedly unrouted the route. This occurred when the route contained only a single shipment/stop, and the same shipment was dragging onto the route, causing an error and the removal of the route from view. (1001925)

🟪 Enhancement: The application now prompts users to confirm the deletion of a Vehicle Profile if found associated with a vehicle, whether its status is active or inactive. This ensures users are aware that the Vehicle Profile assignment will be removed. (997819)

🟩 Resolved Issue: The application failed to validate shipments using the Scan-to-Route feature and provided no response to the respective Descartes Mobile requests. This occurred when the driver had configured access to a location where an active delivery day was not found set. (997607)

🟪 Enhancement: The Customer API now supports null or blank values for service time-related fields. This allows integrating solutions to remove or reset previously updated values to their original state, utilizing organizational settings instead of customer-specific ones, if and when applicable. (986117)

🟪 Enhancement: Users can now define and have added a new Connected Apps option to the Main Menu for seamless integration with other Descartes applications when enabled. A new configuration page has been added, allowing Descartes administrator users the ability to set the display name, URL, and visibility at both the organization and location levels. (986114)

🟪 Enhancement: Assigned helpers can now view route details on the user interface, where previously, this was reserved only for drivers. With this enhancement, both drivers and helpers assigned can view their routes, check their schedules for the next day, and prepare accordingly. (985588)

🟩 Resolved Issue: The exception alert notification incorrectly remained active when a previously inactive depot was reactivated. The application now correctly clears the exception alert upon reactivation of the depot. (984117)

🟪 Enhancement: Users can now drag a Hold Spot stop on the Scheduling Board page to increase or decrease stop service time, similar to the functionality added for regular stops, and the change is reflected in the stop detail window. (975400)

🟪 Enhancement: The On-demand application has been enhanced and added the capability to inform the host system whenever a user manually changes a shipment's origin. A new event trigger has been designed specifically for this scenario. This newly implemented event trigger works with configurable exports (Generic, Generic Shipment, Generic JSON, and Generic Shipment JSON) and Integration Profiles for data transmission. (975293)

🟪 Enhancement: A newly introduced configuration option ('Ignore Unplanned Stop Positions') allows the ability to track GPS unplanned stops without counting them as part of the route order. This helps maintain the accuracy of plan vs. actual (PvA) analysis for stop orders while still tracking GPS unplanned stops for geocode verification and other purposes. (974503)

🟪 Enhancement: The Order Search webservice now includes details on how many stops away the driver is from the respective delivery address. A new data field ('stopsAway') has been added to the webservice response, providing the requesting host with the number of stops remaining until the delivery is next to be serviced. (966196)

🟪 Enhancement: Users can now schedule blocks of time when resources (vehicles, drivers) are unavailable in the respective Schedules feature. This allows blocking a resource's availability for specific hours, not just entire days. If a route overlaps with the set unavailability, the resource will not be assigned. Configured schedule information will override the route and/or profile settings regarding available hours. (963724)

🟪 Enhancement: A new calculation for CO2 emissions per stop has been introduced in addition to the current route level calculation. Users can view this data in a new stop-level column ('CO2Emission'). If no CO2 emission value is set for the vehicle, the output will be empty. (960702)

🟪 Enhancement: Cost-per-stop calculations have been introduced. Previously, costs were only shown for the entire route. This enhancement enables a breakdown of costs per stop, allowing for more accurate customer chargeback for carriage. (960697)

🟪 Enhancement: Users now receive a warning when attempting to clone a shipment that already exists on the selected delivery date. A confirmation box with a confirm/cancel option appears. Confirming this action successfully clones the shipment, creating a duplication. (960689)

🟪 Enhancement: Users can now specify multiple depot access for a user account, allowing the selection of depots within a single or across all locations the user has configured access to. A 'Select All/None' option has been added, along with a tooltip displaying the Location and Type related details for each depot. Users receive a warning message if no depot is selected when the 'Select Depot?' checkbox is selected. (958290)

🟪 Enhancement: Users can now change the color of routes shown on the map for a specific day from within the Map View module. This helps differentiate routes when the optimizer assigns similar colors to adjacent routes. A new control option ('Allow Change Route Color') has been added to the Configuration > Parameters > Dispatch page to enable this option. (949711)

🟪 Enhancement: Vehicles assigned to multiple territories can now service only one territory per route during optimization. This enhancement ensures that each route services only one territory's stops/shipments, maintaining the territory structure. A new setting in the Sequencer/Optimizer profile allows users to specify the number of territories to consider as serviceable. (948276)

🟪 Enhancement: Territory configuration and creation-related options within the Fixed Routes & Territories module have been improved. Users can now plot points on the map to set and modify territories by dragging and dropping the points to adjust the area. Additionally, users can define territories using a polygon, circle, or rectangle. (945773)

🟩 Resolved Issue: Incorrect stop times were calculated for created routes, where the arrival time for the next stop was before the departure time of the previous stop. This occurred in certain use cases when users ran another optimization request using the 'Keep existing routes and insert shipments' option with only used vehicles, leading to additional shipments being added to existing routes with some stops having incorrect times. (914413)

🟪 Enhancement: The system now allows for capturing the position (latitude/longitude) where an item was marked as completed in Descartes Mobile. This feature is a mobile application configurable option in Descartes wGLN for wireless applications that, when enabled, allows the captured position to be displayed and reported in the solution. New fields are to be included in the Complete command message sent from Descartes wGLN. The new 'Item Status Location' column can be configured at the item level and included in export configurations. (742619)

🟪 Enhancement: The application now supports mobile item-related time data to be contained and processed via its integration with Descartes wGLN. The Complete message now includes a dateTime value for item statuses, similar to arrival/complete times based on drivers' actions performed within Descartes Mobile. A new column ('Item Status Time') can be configured to show at the item level in MapView, Scheduling Board, and Dispatch. This column is also available in export configuration options. (742617)

Back to Top