Overview
This update provides finer control over when the Security Sign-Off process should re-trigger based on specific trip updates.
Problem
Previously, Security Sign-Off would re-trigger automatically for every update or change made to a trip — such as employee additions, driver changes, or timing adjustments.
This often led to unnecessary re-triggers and operational inefficiencies.
Solution
The new enhancement introduces a property-based configuration that allows selective control over which actions or updates should trigger a Security Sign-Off again.
⚙️ Configuration Details
Behavior Logic
Sample Value:
["EMPLOYEE_ADDITION","EMPLOYEE_REMOVAL","EMPLOYEE_READDITION",
"DRIVER_CHANGE","EMPLOYEE_TIMINGS_CHANGED","VEHICLE_CHANGE","EMPLOYEE_REARRANGEMENT"]
Dependencies
Driver App: v6.6.0 or above
ETS: v25.08.03 or above
Why This Matters
This enhancement provides flexibility and control — allowing admins to decide which specific actions should trigger a new security sign-off. It reduces redundant workflows, saves time, and improves trip management efficiency.
Was this article helpful?
That’s Great!
Thank you for your feedback
Sorry! We couldn't be helpful
Thank you for your feedback
Feedback sent
We appreciate your effort and will try to fix the article