Escalation of Transaction in BPM Does Not Work. The Task Expires with Emails and Bell Notifications at Assignee Level
(Doc ID 2414459.1)
Last updated on NOVEMBER 15, 2023
Applies to:
Oracle Fusion Global Human Resources Cloud Service - Version 11.13.18.02.0 and laterOracle Fusion Payables Cloud Service - Version 11.13.18.02.0 to 11.13.18.02.0 [Release 1.0]
Information in this document applies to any platform.
Symptoms
The escalations expire at the assignee level and the manager does not get notifications.
1. First approval triggers fine. 1st manager is able to receive the
notification without any issue.
2. Customer is using Management hierarchy to setup the line of approvers.
3. If within 2 mins, 1st manager doesn't approve, the approval notification
should be received by next in line approver in the Management Hierarchy.
4. 2nd Manager is not able to receive the notification and escalation is not
working properly
Error in SOA_ESS Server logs
Changes
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 |
| Changes |
| Cause |
| Solution |
| References |