Fusion Approvals: How "Allow This User To Approve Their Own Transaction" Works With "Prohibit User Self-Approval" When Using Approval Delegation
(Doc ID 2762919.1)
Last updated on MARCH 01, 2024
Applies to:
Oracle Fusion Workforce Compensation Cloud Service - Version 11.13.21.01.0 and laterOracle Fusion Global Human Resources Cloud Service - Version 11.13.21.01.0 and later
Information in this document applies to any platform.
Goal
The scenario is that Person A is designated as the transaction's approver. Person A delegated their approvals to Person B.
Person B submitted a transaction for Person C.
The system should try to send the approval to Person B as that person is the approval delegate and then skip Person B because he is the creator and then go the next approver.
In BPM Worklist, Prohibit User Self-Approval is configured for Task Creator.
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 |
| References |