Message steps triggered by 'Add' launch condition are not triggered/get obsolete if the activity was suspended
(Doc ID 3005688.1)
Last updated on JUNE 23, 2024
Applies to:
Oracle Fusion Cloud Field Service - Version 24.A.04 and laterInformation in this document applies to any platform.
Symptoms
After updating to version 24A we noticed that message steps created during the activity creation ("Add" Launch condition) are not delivered at night when we expect. This used to work fine in version 23D.
STEPS TO REPRODUCE:
- Configure a message step using the Add launch condition as a Set property and with the following pattern (for example):
action - unschedule_activity
- Configure the message step to be delivered before the end of the day of the activity's route.
- After the expected time, the message appears as OBSOLETE in the Messages screen. The messages disappears from the Message screen after some hours.
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 |