Skip to main content
Omnitracs Knowledge Base

Omnitracs One (Roadnet Anywhere) 6.4 Point Release 3-5-2022

Active Alert

  • NA for this release.

Dispatch

  • NA for this release.

Drive/Command

  • A change was made to the depart task that allows a driver to update their Departure Time called "Allow Driver to Edit Departure Time". The driver only allows the edited Departure Time to be after the last task was completed.

  • All MilesAhead and Drive Host roles including Pipelines and other roles, have been adjusted to mitigate escalation.

  • The following Drive/Command data value have been updated:
    Removed Device Name from Command.
    Updated About page in Drive to remove 2nd piece of Device ID that was showing "unknown" in most cases.
    Updated Data API to publish new values (Device ID, Mobile ID) to user record so they can show in Command.

DVIR

  • NA for this release.

Integrations and APIs/ 3rd Party Integrations

  • VAR Disclosure: The ReadMe.txt file has been deleted from the specified path (LatitudeURL/Shared/ReadMe.txt).

Miscellaneous

  • NA for this release.

Mobile

  • NA for this release.

OTNav Host

  • NA for this release.  

Routing 

  • Added the fields as optional, buildingDeliverySequence, preferredRouteIdentifier, and timeWindowImportance, to Service Locations Post, Put and Patch methods. Refer to the REST website for detailed documentation.

Strategic Planning

  • Implemented web service, "/strategicplan/moveRecurringOrders/{entityKey}", to specify the sequence number for a recurring order on a route.

Webservices

  • Added the fields buildingDeliverySequence, preferredRouteIdentifier, and timeWindowImportance to the REST API Service Location Post, Put and Patch methods as optional fields

XRS

  • Changes have been made to improve the Distance Discrepancy Report.

 

Software Corrections 

Work Item Number Issue Components

RPE-84311

Modified REST API to save orders through the SaveOrdersJob only if the number of orders is greater or equal to a configurable threshold (set to 5 by default)

API

RPE-83700

There was an issue using Roadnet Mobile on an iOS device. When the user adds an order to a stop, the application stops working. This issue has been resolved.

Active Alert/

Mobile Manager

RPE-82422

There was an issue in Active Alert where duplicate emails are sent regarding contact information changes when a custom email sender is used. This issue has been resolved.

Active Alert/

Mobile Manager

RPE-83253

An 'unexpected error' running Create Strategic Routes using 'Adjust Start Time' has been fixed.

Algo

CEV-1394

There was an issue where a triggered critical event value (CEV) always shows events in MPHs. The CEV should be labeled based on the event type. This issue has been resolved.

CEV

RPE-83124

There was an issue when sending messages from the Omnitracs One portal. The messages were received on the mobile app but not seen in the sent folder. This issue has been resolved.

Dispatch

RPE-80984

There was an issue where the Canadian customer was receiving post speed violation exceptions via email and the email contains KM and MILES for the violation. The post speed exception that gets emailed to the customer should be in KM, not miles. This issue has been resolved.

Dispatch

RPE-83266

There was an issue where the customer is getting a server busy error when searching for the latest orders in OT1. This occurs when the customer is filtering on all regions. This issue has been resolved.

Dispatch

RPE-83408

There was an issue after assigning a worker to a planned route card in Fleetview, such that the Save button was greyed out. This issue has been resolved.

Dispatch

RPE-83513

There was an issue in the Omnitracs One website that results in an unexpected error when searching for a location ID by description. This issue has been resolved.

Dispatch

RPE-83560

There was an issue when a user opens Assign Resources in Fleetview, the window was taking too long to load. This issue has been resolved.

Dispatch

RPE-83621

When a user is using Route Actions > Assign Resources to select multiple routes and assign a worker to each route, the first worker assigned was being assigned to the next route as well. This issue has been resolved.

Dispatch

RPE-83625

There was an issue adding location comments to the Mobile workflow that results in a server busy error. This issue has been resolved.

Dispatch

RPE-83570,RPE-836411 Addressed various Server Busy errors performing dispatch task via database index.   Dispatch
RPE-83524

There was an issue when a user attempted to add a RNT device into RNA they received an error saying it was duplicate data due the first save attempt that did not complete. The system now allows the user to add a device even after a failed save attempt.

Dispatch

RPE-79250

There was an issue in Exception Rules when a User Defined - Arrival Time - Save rule fails when it contains the Not Equal To option. This issue has been resolved.

Dispatch

DCMD-6376

There was an issue with the Drive app not clearing its cache upon logout, even when the setting in Command is enabled. This issue has been resolved.

Drive/CMD

DCMD-6519

There was an issue when editing User Groups in Command in which you cannot save changes unless you change the Group name. This issue has been resolved.

Drive/CMD

DCMD-6555

There was an issue with an Unplanned stop that becomes stuck when a new stop sequence and/or stops are added. This issue has been resolved.

Drive/CMD

DCMD-6639

There was an issue in the Drive App when an unplanned stop is incorrectly positioned after swapping planned stops and then removing the next planned stop in the sequence using the replaceDocs Postman call. This issue has been resolved.

Drive/CMD

DCMD-6640

There was an issue where the Detailed Notification, that should be limited to the current active trip, was including all of the  trips in the device. This issue has been resolved.

Drive/CMD

DCMD-6563

There was an issue using the Drive workflow when drivers pressed 'DONE' on the Depart task workflow which invoked a Co-Pilot screen that was blank. This issue has been resolved.

CoPilot Nav

DCMD-6551

There was an issue where CoPilot was not using the vehicle settings configured for the equipment type in RNA and CoPilot routing options in Command were not synced up with CoPilot. This issue has been resolved.

CoPilot Nav

RPE-83447

There was an issue when a user attempts to save a session using a different date other than the original session date receives an unexpected error. When the user used the original session date the issue did not occur. This issue has been resolved.

Routing

RPE-81496

There was an issue when a user is working with routes with a large number of stops that could cause the error "Data Retrieval Error. The Server is busy. Please retry".  This issue has been resolved.

Routing Client

RPE-83151

There was an Unexpected Error when opening Unassigneds view is Sorting Order in the view configuration was set to Order Classes.  This issue has been resolved.  

Routing Client
RPE-83700 Roadnet Mobile crashed when order is added to stop on an iOS device Roadnet Mobile iOS

RPE-84140

The Territory GET operation no longer returns a 500 Internal Server Error when a valid planning session 'entitykey' is used.

Strategic Planning

RPE-80619

There was an issue in the Equipment Position History Report showing the wrong driver when sharing the same truck. This issue has been resolved.

Telematics

RPE-81139

There was an issue where updates for the route were not shown in real-time from beginning to end. This occurred when a driver started a route in Canada and continues across the border to the United States. The GPS positions and updates did not display until after crossing the border. This issue has been resolved.

Telematics

RPE-81940

There was an issue in the Distance by Jurisdiction Report that displayed inaccurate mileage for some vehicles. This issue has been resolved.

Telematics

RPE-82030

There was an issue in Roadnet Anywhere when a user attempts to run the Telematics Diagnostics Report in two regions which results in an unexpected error. This issue has been resolved.

Telematics

RPE-82948

The Drive route workflow works properly for the driver until an unplanned route card is generated in Fleetview, which sometimes results in some stops being canceled out when the original route is completed. This issue has been resolved.

Telematics

RPE-83524

There was an issue when a user attempted to add a RNT device into RNA they received an error saying it was duplicate data due the first save attempt that did not complete. The system now allows the user to add a device even after a failed save attempt.

Telematics

XRS-11316

There was an issue in the worker compliance integration. When looking at the worker's 'last status' appeared to be a few days off compared to the Driver Log Report. This issue has been resolved.

XRS Host

XRS-12036

There was an issue for organizations using metrics, where the distance data in the header of the Driver Log Report doesn't match up due to a rounding error. This issue has been resolved.

XRS Host

XRS-12390

There was an issue where some drivers had incorrect distance values on the ELD Driver Log Report and Payroll Summary Report. This issue has been resolved.

XRS Host

XRS-13524

There was an issue after generating a Black Box Summary by Driver report. When the user clicks on the Eye Icon and generates the Black Box Summary report, the Summary Report page contains a link to the map of the location. Clicking on this link with the mouse did not activate the hyperlink. This issue has been resolved.

XRS Host

  • Was this article helpful?