This release note describes enhancements and fixes for EROAD 360 Version 24.12 for Sysco. Unless otherwise indicated, the changes apply to all users.

The following enhancements were completed for this release.

For a specified date range, Route Manager listed all actioned routes, which included routes that started, ended, and were in progress during the date range. This made it difficult to discern relevant routes from irrelevant routes and slowed loading times.

We updated the filtering logic so that Route Manager now only displays routes with planned start dates within the selected date range. This decreases loading time. Additionally, the default date range is now current day to next day rather than current day to current day, thus improving visibility of upcoming routes.

Superusers only. In Vehicle Manager, you can now select electric as the fuel type for a vehicle. When adding or editing a vehicle, the Settings tab > Fuel Type dropdown includes Electric as an option.

Superusers only. The Select Facility Geofence option was added to the Add Fleet and Edit Fleet windows in Fleet Manager. This option enables easy selection of a fleet’s facility geofence when a company has a large volume of locations.

Previously, a Vehicles > DVIR menu option was visible on the 360 navigation menu. This option was removed since it is unused.

Location Summary, Overspeed and Vehicle Inspection History Reports are now in French. Additionally, some English report headers in the vehicle alerting page have been translated along with the filtering options for multiple EROAD 360 screens.

The following issues were fixed for this release.

Superusers only. In the Admin > User Manager > Edit User window, the Test button associated with the Email field did not work. The button was supposed to send an email with login instructions to the specified user email address. The button is fixed so that now it sends the login instructions to the user.

In some cases, the Driver ELD Log Report displayed USDOT # “156275” for carrier “Sysco USA I, Inc” rather than the correct USDOT # and carrier associated with the driver’s terminal. Now, the report pulls the correct data to populate the report’s Carrier, USDOT #, and Carrier Principle Place of Business (Canada only) fields. This issue did not apply to FMCSA and CCMTA reports, which report the correct information.

When vehicle data was not available, the CSV (.csv) report generated for FMCSA compliance displayed “0” values for vehicle miles and engine hours for events originating from the ELD or the unidentified driver profile. ​Per the FMCSA, these fields in the report should be left blank when the data is not available. We fixed the report to ensure that vehicle miles and engine hours are left blank in this case.

After a page refresh, while a vehicle trip with breadcrumbs was displayed, the breadcrumbs would disappear. This was fixed so that the breadcrumb state remains after screen refreshes.