New backup vehicle status visibility in the dispatch view, plus fixes to organization-level vehicle settings that were not persisting correctly.
A new Backup Vehicle status has been introduced to the Vehicle Settings page to provide greater control and flexibility during operations.
Vehicles set to Backup Vehicle status will not be assigned automatically to routes.
Backup vehicles can still be manually selected when needed from the Dispatch or Trip Requests pages.
Routes configured to use a backup vehicle will continue to automatically route with that vehicle. Adding or removing trips on a route using a backup vehicle will not affect the vehicle assignment.
Vehicle settings are stored at the organization level. A shared vehicle set as a backup for one organization will not affect its status in another organization, where it may be set to In Service or Out of Service.
In rare cases where a backup vehicle does not have sufficient capacity and another in-service vehicle is available, auto-routing or custom routing may switch to a different vehicle to accommodate the additional capacity.
Previously, when a vehicle was shared between organizations, updating the in-service date range in one organization could unintentionally update it for both. In-service date range settings are now stored and applied at the organization level. As part of this release, all existing in-service date ranges for a given vehicle were standardized to the most recently configured date range. Routing will continue to respect vehicle usage across organization boundaries.
Previously, when a vehicle was shared between organizations, updating the depot location in one organization could unintentionally update it for both. Vehicle depot location settings are now stored and applied at the organization level.
Previously, selecting a route would sometimes result in route paths failing to load. Route paths now load reliably, and performance improvements significantly reduce load times.