Oracle Fusion Technical: Reports, Data, Integrations and Extensions · Module 14 · Approvals and BPM workflow
Delegation, escalation and timeouts
Lesson 141 of 177 · 2 min
What happens when an approver is on leave. Configure it deliberately, rather than discovering the default during a month end. DELEGATION is the approver handing their tasks to somebody else, either by their own action before going on leave or by an administrator. The decision remains attributed to the delegate, which matters for the audit trail: it is a different record from the original approver having approved it. ESCALATION is the system moving a task on when nobody acted — typically up the hierarchy after a period. It is what stops a queue forming behind one person. A TIMEOUT is the period before that happens, and choosing it is a business decision with a real cost either way: too short and approvers are bypassed while they are in a meeting, too long and the month-end run misses its deadline. Ask what the transaction's own deadline is, and set the timeout…
The full lesson is part of the course
The video, the complete written lesson and the module quiz are included in Oracle Fusion Technical: Reports, Data, Integrations and Extensions, with a certificate on completion and a fourteen-day refund window.
In this module: Module 14 · Approvals and BPM workflow
- 1How approvals are actually structured
- 2Approval rules and how they are evaluated
- 3Supervisory and position hierarchies
- 4Parallel, serial and FYI participants
- 5Delegation, escalation and timeouts
- 6Notifications and what they say
- 7Testing an approval rule properly
- 8Diagnosing a stuck transaction
- 9What breaks: the approval nobody received
- 10Lab briefing · Build and break an approval chain