Unfeasible Appointment Times When Scheduling Appointment From Agent After Tracking Event Modification
(Doc ID 2905363.1)
Last updated on AUGUST 05, 2024
Applies to:
Oracle Transportation Management Cloud Service - Version 22.3 and laterInformation in this document applies to any platform.
Symptoms
When scheduling an appointment after having modified a check-in tracking event, you are getting feasible times that shouldn't be feasible due to the check in at the first stop.
Cause
To view full details, sign in with your My Oracle Support account. |
|
Don't have a My Oracle Support account? Click to get started! |
In this Document
Symptoms |
Cause |
Solution |
References |