Sequential Approvals and Catalog Tasks in Dynamic Activities
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
10-09-2026 03:10 AM
Hello,
I have a catalog item with 3 levels of approvals and 4 catalog tasks (SCTASKs). I need to implement a fully sequential approval and task process without using Flow. I am using Catalog Approval Rules, Catalog Task Rules, and Dynamic Activities.
Expected Flow
- A RITM is created.
- Approval Level 1 is generated.
- Once Approval Level 1 is approved, SCTASK 1 is generated.
- The user manually closes SCTASK 1.
- Only after SCTASK 1 is closed, Approval Level 2 is generated.
- Once Approval Level 2 is approved, SCTASK 2 is generated.
- The user manually closes SCTASK 2.
- Only after SCTASK 2 is closed, Approval Level 3 is generated.
- Once Approval Level 3 is approved, SCTASK 3 is generated.
- The user manually closes SCTASK 3.
- Finally, SCTASK 4 is generated.
@Ankur Bawiskar
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
2 weeks ago
Hi,
The reason this is hard with rules alone is the key point: Catalog Approval Rules and Catalog Task Rules are condition evaluators, not a sequencer. A rule fires whenever its condition becomes true on the RITM - it has no built-in concept of "only after step 5, and only once." If you write Level 2's Approval Rule as just a condition on the item/variables, it will be evaluated at the same time as Level 1 and Level 3 (typically when approval is requested on the RITM) and you will get all approvals up front. To get a strictly alternating chain you have to give the RITM an explicit sequence state and make every rule check it.
Design that works without Flow:
1. Add a sequence/step field on the RITM for this item (a choice field, e.g. u_sequence_step) with values in your exact order: level_1_approval, task_1, level_2_approval, task_2, level_3_approval, task_3, task_4, done. Set it to level_1_approval on RITM creation.
2. Gate every rule on that field, and on nothing earlier:
- Approval Rule Level 1: condition includes u_sequence_step = level_1_approval.
- Catalog Task Rule SCTASK 1: condition includes u_sequence_step = task_1.
- Approval Rule Level 2: condition includes u_sequence_step = level_2_approval - which can only be true after SCTASK 1 closes, so it cannot be created at submission.
- And so on: Task 2 rule on task_2, Level 3 rule on level_3_approval, Task 3 rule on task_3, Task 4 rule on task_4.
3. Advance the step with small after Business Rules, which are the actual sequencer:
- On sysapproval_approver, after update, when the approval is for this RITM, state changes to approved, and the RITM step is the matching level_X_approval: set the step to task_X.
- On sc_task, after update, when the task belongs to this RITM/item, state moves to a closed state, and the step is task_X: set the step to the next value (level_(X+1)_approval, or task_4 after Task 3, or done after Task 4). Match the specific task by its sequence identity/order, not just "any task on the RITM," or a manually created extra task will advance the chain by mistake.
Updating the RITM step is what re-triggers rule evaluation for exactly the next step.
4. Protect against the two usual breakages:
- Duplicates: rules re-evaluate whenever the RITM is updated, so each rule's condition (or a scripted check) should also verify that no approval/task for that level already exists for this RITM. The single-step field already makes a second firing window very small - once the step advances, the previous rule's condition is false again.
- The RITM approval field: do not let the RITM's own approval field flip to approved after Level 1. Keep the RITM approval as requested until the final approval completes, otherwise out-of-the-box catalog behaviour that hangs off "RITM approved" (stages, other rules, notifications) fires three steps early. Drive everything off your step field and only set the RITM approval to approved when Level 3 is approved, and handle rejection at each level by moving the step to a rejected/end state and cancelling any later approvals/tasks (which should not exist yet if the gating above is in place).
Honest caveat: this works, but you are hand-building a state machine, and it is brittle if someone edits a rule condition later without the step check. If the constraint is only "not Flow Designer," a legacy Workflow on the RITM (Approval activity -> Catalog Task activity -> Approval activity, in sequence) is still a sequencer by design and is less fragile than rules. If it must be rules only, the step field above is not optional - it is the mechanism that makes the sequence strict.