This release note describes enhancements and fixes for EROAD 360 Versions 26.3 and 26.2. Unless otherwise indicated, changes apply to all users.

The following enhancements were completed for this release.

We have enhanced the mapping to utilize depart_at and arrive_at fields, if provided in the route payload.

Improvements include:

These changes further align Planned and Actual route timings, optimizing experience for dispatchers reviewing route data.

Previously, the side navigation in Phoenix did not automatically collapse at smaller viewport widths, making it harder to view the map when investigating stops. To improve usability and align with MyEROAD, the side navigation now automatically collapses at 1279px and expands at 1280px, providing a more consistent and user-friendly experience.

Previously, dispatchers could not search for addresses within Route Investigator, making it harder to locate stops on the map. To improve navigation and efficiency, we added an address search field, allowing dispatchers to find relevant stops and view them directly on the map. Addresses and stops unrelated to the selected route are now excluded from search results.

Previously, dispatchers had to click on a vehicle to see which driver was logged in. To improve efficiency, the driver's name now appears in the vehicle popup when hovering over a vehicle on the Tracking page and in Route Manger, or the popup clearly indicates that no driver is logged in.

A change was needed so that a user logging on using SSO would be directed to a Phoenix landing page instead of to a legacy landing page. Now, Sysco users can login to 360 via SSO login. Sysco users with Set Phoenix as default turned on are directed to Phoenix when they login via SSO.

The following issues were fixed for this release.

Previously, there was an issue in which an inactive driver was still associated with a vehicle after the current driver was logged out. Now, when a driver that is driving is marked as inactive, the driver is no longer shown as being associated with the vehicle they were driving.

When generating a Driver Efficiency Report, the report would open as a blank page in a new tab when data exceeded the maximum column width. Now, the report shows an asterisk when the value received is outside the expected range or not valid, and the report generates as expected.

A retry mechanism was added to scheduled reports to support the scenario in which the report server is too busy to handle the generation of a scheduled report at the configured time.

We resolved an issue in which event times in the Driver Log Report were rounded up to the next second. This is now resolved by truncating milliseconds, so event times display only hours, minutes, and seconds, matching the actual driver logs.

The Proposed Edits Report did not correctly reflect supervisor edits to driver logs. The report showed incorrect Date Edited values and misclassified edited events as ADD actions instead of EDIT. The report now correctly displays the edit date and accurately groups and labels edited versus added events.

We resolved an issue in which the Driver Edit report would time out or fail to load when run for a single driver group or all drivers. The report now successfully generates for all filter combinations without timing out.

We resolved an issue in which the Driver Time Card Details Report would not run or returned blank results when the selected date range spanned two months. We updated the report logic to handle date ranges that cross month boundaries, ensuring reports generate correctly for all date selections.

We fixed an issue in which an expanded navigation item would sometimes not collapse when clicked. Now, clicking an expanded navigation item reliably collapses it and hides its sub-items, ensuring consistent toggle behavior across repeated clicks.

We resolved an issue in which the events panel would crash and fail to load for in-progress routes, preventing dispatchers from viewing trip events. Now the events panel loads reliably for in-progress, completed, and not-yet-started routes, allowing dispatchers to monitor trip progress without errors.

We resolved an issue in which the event count label in the events panel showed "0 events found" for in-progress routes even when events were present. Now the correct number of events displays immediately when the panel is opened, without needing to refresh or change filters.

​