Fusion Approvals: Rule-Based Routing and BPM Composer Deep Dive

Explain advanced Fusion approval configuration beyond basic Task Configuration, including BPM Composer customization

Task Configuration handles common approval routing declaratively. BPM Composer edits the underlying BPMN process, and the line between them is the question.

If Task Configuration is like adjusting settings on a pre-built assembly line (changing which inspection station a product goes to based on its weight), BPM Composer is like actually redesigning the assembly line itself — adding a brand-new station, splitting the line into parallel paths, or wiring in a robotic arm (external system call) mid-process.

Key Concepts

What Task Configuration covers. Stages, participants, and rules within the delivered process shape:

    stage 1   management chain, 2 levels
    stage 2   IF amount > 500000 THEN Finance Director
    stage 3   IF category = CAPITAL THEN Capital Committee

Conditions on transaction attributes, approver resolution up a hierarchy, serial or parallel participants. That is most requirements.

What needs BPM Composer. Changing the process itself rather than its routing:

  - a genuinely new stage that does not fit the delivered pattern
  - a system step inside the approval — calling an external service
    between two approvals
  - a parallel branch active only under a condition, with its own
    logic
  - custom handling of a timeout or an escalation path

Composer shows the actual BPMN — swimlanes, gateways, human tasks — which Task Configuration abstracts away.

The cost of going there.

    Task Configuration   declarative, by a functional administrator,
                         and Oracle carries it through updates
    BPM Composer         a modified process definition. A developer,
                         a deployment, and something to revalidate
                         at each quarterly update.

That last point is the argument. A customised BPMN process is a customisation, with the maintenance that implies, in a system whose main proposition is that Oracle handles upgrades.

So the sequence is the same as everywhere else in Fusion. Try the declarative tool. Exhaust it. Then consider the powerful one, deliberately, with the ongoing cost stated.

The parallel with EBS is exact: Forms Personalization before CUSTOM.pll, Page Composer before JDeveloper, Task Configuration before BPM Composer.

A practical note on testing. Approval routing depends on HR data — hierarchies, positions, who reports to whom. A rule that is correct against clean test data behaves differently in production where somebody has no supervisor, or two.

Testing routing means testing it against realistic hierarchy data, including the broken parts.

What the interviewer is probing.1. "Where are Fusion approval rules maintained?" Probing: the practical knowledge. Stalls: "In the module." Moves up: in BPM worklist task configuration, or the simplified approval rules UI for supported objects.

2. "What is a stage in an approval task?" Probing: the structure. Stalls: "A step." *Moves up:* a grouping of participants evaluated in sequence or parallel, which is how a two-tier approval is modelled.

3. "What is the deployment consideration?" Probing: the operational angle. Stalls: "None." Moves up: rule changes take effect for new tasks, not in-flight ones, so a cutover needs a quiet period or a plan for outstanding approvals.

4. "How do you handle an approver who has left?" Probing: the real-world case. Stalls: "Nothing." Moves up: reassignment rules and vacation delegation, plus a defined escalation so a task does not sit indefinitely.