This release focuses on backend work and improving usability for all users. For DTNA, the following updates were completed:
- Update mileage unit (miles/kilometers) while creating an asset and a case
- Case created that does not have an ETR value
- When adding recall operations do not add parts.
Update mileage unit (miles/kilometers) while creating an asset and a case
During this release, we worked to properly display the Mileage Unit (miles/ kilometers) for better usability and accuracy when creating an asset or a case for an asset.
Case created that does not have an ETR value
We recently fixed the DTNA integration that results in a Case created without an Estimated Time to Repair if there is no PromiseDate and or PromiseTime.
Add mileage limit of the coverage to the warranty listing
During this release, we have added the mileage limit to the warranty description for DTNA Warranty and Extended Coverage data.
When adding recall operations do not add parts.
We worked on the DTNA Operations so that when it’s added to a case, it will no longer add parts to it because it will not give the ability to filter parts by VIN.
COMING SOON: Data Privacy and Compliance
We will have more information on this new initiative soon, but wanted to give our customers a quick heads-up about this coming change. We will start implementing a data privacy control feature that allows customers to select their data privacy and cookie settings.