The Omnitracs One (Roadnet Anywhere) 6.1.1 release contains several new features and software corrections to make your fleet management operations more efficient and cost effective.
- You can add a new active alert recipient when you create an Active Alert Subscription for a service location.
- You can choose whether to include the route path on the map in Drive.
- You can choose whether to include the trip distance on the trip header on the Day Planner tab.
- You can specify the inspection type for a DVIR.
- You can now specify headers that will be included in the output file if you are using the Outgoing Data Feed option.
Adding Recipients When Creating Service Location Subscriptions
When you are adding an active alert subscription to a service location, you may realize that the recipient you want to assign has not been added to Omnitracs. So that you do not have to stop in the middle of adding the subscription, the ability to add new active alert recipients has been added to the Active Alert tab for the service location.
To add a new recipient when creating a subscription, simply press the Add Active Alert Recipient button. The Add Active Alert Recipient window displays, so that the recipient’s information can be added to Omnitracs. Press Save to save your recipient. Press Close to close the Add Active Alert Recipient window. Once the recipient is added, when you search for the recipient’s name it is found and available for you to assign to the subscription.
Disable the Map Route
You can choose to have the route path not displayed on the map in Drive.
- In Command, select the workflow you want to update.
- Click Universal Config, then Core Maps/Navigation. The Core Maps/Navigation page opens.
- To keep the route path from displaying on the map in Drive, check Disable Map Route.
- Click [Save].
Hiding the Trip Distance on Day Planner
You can choose to have the trip distance not be included on the Day Planner in Drive.
In Command, select the workflow you want to update.
- Click Universal Config, then My Day Planner. The My Day Planner page opens.
- To keep the distance from displaying on the Day Planner page in Drive, check Disable Distance Calculation on Trip Header.
- Click [Save].
Specifying the Inspection Type for a DVIR
You can specify whether a DVIR is Pre-Trip, Post-Trip, Mid-Trip, or Ask User.
- In Command, select the workflow you want to update.
- Click Task Library, then DVIR. The DVIR page opens.
- Click the Inspection Type arrow and choose the proper type for the DVIR. If Ask User is selected, the driver will need to select the type when completing the DVIR.
- Click [Save].
Specifying Headers for the Outgoing Data Feed File
If you are using the Outgoing Data Feed option to pull Telematics information from Omnitracs, you can now specify headers that will be included in the file.
- Click on Admin to open Administration.
- Select the business unit you want to update, then click the Edit icon. The Business Unit window opens.
- Click Outgoing Data Feed. The Outgoing Data Feed page opens.
- In the Custom Headers are, click Add Header.
- Enter the Header Name and Value.
Note: Omnitracs recommends following standard http format recommendations when creating your headers.
- Click [Save].
|XRS-5726||If a driver clocked in using the Driver Clock and the driver's region did not have a default reporting location, the system displayed the company's HOS address rather than the region's address. This issue has been resolved.||Compliance|
|RPE-18268||There was an issue that could cause an error when importing service locations. This has been corrected.||Data Transfer|
|RPE-18314||An issue that was preventing the map from filling the entire map area, leaving gray areas along the edges, has been corrected.||Dispatching|
|RPE-18215||There was an issue that was causing users to see both MPH and KPH on speed exception notifications. This has been corrected.||Dispatching|
|RPE-18365||There was an issue that could prevent users from being able to clear a panic button incident for a vehicle. This has been resolved.||Dispatching|
|RPE-18890||There was an issue that could cause an error on the Routes view in FleetView if specific FleetView settings were selected. This has been corrected.||Dispatching|
|RPE-18134||There was an issue preventing Scorecard KPIs from being shared with other users. This has been corrected.||Insight|
|RPE-18222||There was an issue trying to add workers to compliance alerts when all regions were selected. This has been corrected, and the workers now appear.||Maintenance|
|RPE-18383||There was an issue that could prevent historic routes from being migrated from the Roadnet Transportation Suite. This has been corrected.||Miscellaneous|
|RPE-18176||There was an issue that caused an unexpected error when plotting a route with Show Unassigned enabled. This has been corrected.||Miscellaneous|
|RPE-18114||There was an issue preventing some customers from being able to access Mobile Device Diagnostics. Now customers who have purchased Omnitracs Navigation, Omnitracs Drive, Omnitracs Compliance, and have at least 1 mobile license will be able to access Mobile Device Diagnostics.||Miscellaneous|
|RPE-18111||An issue was reported where routes originating in the Newfoundland timezone were not accurately reflecting the change to DST. This has been resolved.||Miscellaneous|
|RPE-17873||There was an issue that was preventing the OK button from taking the user to the UVA editor when there were unassigned vehicle activities to address when logging into the route in Roadnet Mobile. This has been corrected.||Mobile|
|There was a rare issue where the distance was calculated incorrectly if the last stop on the route was an unknown stop and the driver manually arrived the route. This has been corrected.||Mobile|
|RPE-18112||If a driver attempted to update the equipment on the route, and that equipment was assigned to an auto-generated route, the driver would receive an error. Now, the auto generated route will be completed, and the driver will be able to update the equipment on the route.||Mobile|
|RPE-17502||There was an issue that could cause the application to crash when generating a route. This has been corrected.||Navigation|
|RPE-17410||There was an issue that was causing Navigation to load very slowly when shifting display modes. This has been corrected.||Navigation|
|RPE-17504||Some values in the Route Status screen were displaying incorrectly. This has been resolved.||Navigation|
|RPE-17087||There was an issue that could cause the application to crash when running OS9 and generating a route to Oklahoma. This has been corrected.||Navigation|
|RPE-16933||There was an issue that could cause the spoken instructions to always say 3 miles. This has been corrected and the correct distance is now spoken.||Navigation|
|RPE-17369||There was an issue that caused the volume to be very low when Omnitracs Navigation was launched from Roadnet Mobile. This has been corrected.||Navigation|
|RPE-13258||The Alerts menu option has been changed to Alerts and Reports in the Omnitracs Navigation application.||Navigation|
|RPE-18176||There was an issue that caused an unexpected error when plotting a route with Show Unassigned enabled. This has been corrected.||Planning|
|RPE-18304||There was an issue that could cause an error when using Transfer Session. This has been corrected.||Planning|
|RPE-18177||The Route and Stop lists were not properly refreshing once Shift Days was run. This has been corrected.||Planning|
|RPE-18363||An issue that could cause incorrect values on the Distance by Jurisdiction report has been corrected.||Reporting|
|XRS-8479||The Distance Fix column in the Driver Payroll Summary and Time Clock reports were not reflecting miles from log edits. This has been corrected.||Reporting|
|RPE-18201||There was an issue where the algorithm was not choosing the least expensive equipment when a large number of resources were available on the pass. This has been corrected.||Routing|
|RPE-18200||There was an issue that could cause the route to exceed the Max Runtime if the worker had a service time adjustment. This has been corrected.||Routing|
|RPE-18365||There was an issue that could prevent users from being able to clear a panic button incident for a vehicle. This has been resolved.||Telematics|
|RPE-18355||The Route Actuals report REST API as had the following information added:
BreakStopInfo now includes Coordinates
MidRouteDepotStopInfo now includes Running, Pickup, and Delivery planned and actual quantities
|DCMD-5235||There was an issue preventing users from being able to close the Map Features window. This has been corrected.||Drive|
|DVIR-755||There was an issue that could prevent a driver from adding an unlisted asset to a DVIR. This has been corrected.||Drive|
|DVIR-757||There was an issue preventing assets from being found if the driver typed the search in lower case letters. This has been corrected.||Drive|
|DCMD-5356||There was an issue causing the slide out menu to be partially hidden when opened from a map. This has been corrected.||Drive|
|DCMD-5345||There was an issue that was preventing the Map Features and some other dialogs from closing properly. This has been corrected.||Drive|
|DCMD-5339||An Add icon has been added to the Document page so that a document can be added.||Drive|
|DCMD-5343||The Map Tab has been removed for Drive Mobile customers.||Drive|
|DCMD-5233||The Ad Hoc menu will no longer be available if no Ad Hoc tasks are configured for the workflow.||Drive|
|DCMD-5350||There was an issue that was preventing the Map Features window from closing properly. This has been corrected.||Drive|
|DCMD-5355||There was an issue that could cause Skip Stop to not work properly. This has been corrected.||Drive|
|DCMD-5349||There was an issue preventing all trips from being completed even when all the stops had been completed. This has been corrected.||Drive|
|DCMD-5348||Drivers in Off Duty status were able to start a task without being reminded to change their duty status. This has been corrected.||Drive|
|DCMD-5232||There was an issue preventing co-driver login events from being properly recorded. This has been corrected.||Compliance|
|DCMD-5352||New messages were not being read aloud when received in Drive. This has been corrected.||Drive|
|DCMD-5334||There was an issue that caused the wrong workflow to be assigned to the worker. This has been corrected.||Drive|