Message step failing as Obsolete (Activity_was_rescheduled)
(Doc ID 2956907.1)
Last updated on JULY 10, 2023
Applies to:
Oracle Fusion Cloud Field Service - Version 23.B.02 and laterInformation in this document applies to any platform.
Goal
Let's say we have a Manual Message Scenario with a step that is invoked when specific service request is submitted and the business workflow of the technicians assume that they first submit the service request, then start the activity. In this particular business use case, all activities are non-scheduled in tech pools, so OFS will essentially move the job from non-scheduled pool to scheduled/next in route then it will start the activity. If the step is not in final status by the time the technician is moving the activity, the step will fail in Obsolete status with description "Activity was Rescheduled"
Question:
Is there any tweak we can implement so OFSC can fire the message step even though the activity is changed?
Solution
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
Goal |
Solution |