This release note describes enhancements and fixes for EROAD Drive Microservices Version 24.10.
What's New in This Release?
What's New in This Release?
Enhancement:
Enable five new vehicle types for DVIR
Fixed Issues - General:
Clean-up Drive legacy API hub
Exception in Drive Microservice when enabling capture syncing to topic
Review topic ms-360 TTL and add monitoring
Create/replace monitors for Service Bus Microservice
Fixed Issues - DVIR:
Accept DVIR repair from topic
Drive Portal inspection assignment deletion issue
Environment | Pre-Production | Production |
Release Version | v24.10 |
|
Proposed Date | February 16, 2025 |
|
Proposed Time | 7 PM, CST |
|
Deployment Duration | Approximately 2 hours |
|
Expected Downtime | None expected |
|
Enhancements
The following enhancement was completed for this release.
Enable Five New Vehicle Types for DVIR (CAB-1756)
We added additional vehicle types for DVIR inspections, each with a unique icon. The vehicle types are: Utility, Beverage Van, Utility Pickup, Passenger Van, and Moffet.
Fixed Issues: General
The following general issues were fixed for this release.
Clean-Up Drive Legacy API Hub (CAB-1810)
We removed all device and core-data related APIs that are not functional.
Exception in Drive Microservice When Enabling Capture Syncing to Topic (CAB-1809)
Fixed a bug that was found in the new dev environment when trying to enable capture syncing to topic via policy.
Review Topic ms-360 TTL and Add Monitoring (CAB-1773)
We added Datadog alerting to improve monitoring of the topic that receives Drive data to 360.
Create/Replace Monitors for Service Bus Microservice (CAB-801)
As part of a Sysco monitoring uplift, we are improving Datadog monitoring and alerting so that we can be notified of critical events, allowing us time to address them early, ideally before they become incidents.
Fixed Issues: DVIR
The following DVIR issues were fixed for this release.
Accept DVIR Repair from Topic (CAB-1768)
To support additional use cases, we expanded our support for how DVIR repairs are communicated in our product.
Drive Portal Inspection Assignment Deletion Issue (CAB-1580)
Previously, deleting a Vehicle Inspection Configuration Assignment from the Drive Portal did not remove it from 360, which caused errors when trying to edit the assignment. To resolve this, the Delete button (trash can icon) for inspection assignments was removed from the Drive Portal. Deletions are now only permitted from 360, ensuring consistent data and preventing assignment duplication or errors.