Activation Policies
Activation policies define when a task should become active within a workflow.
They describe how the workflow engine evaluates predecessors and conditions before moving a task into the ready/active state.
All
The task becomes active only when all predecessor tasks are completed (done, skipped, or cancelled) and its activation condition (if any) is met.
“CFO Approval” requires both Manager Approval and Data Validation to be finished.
Any
The task becomes active as soon as one predecessor task is completed. Late predecessors are automatically marked as skipped.
Parallel approvals where only one department needs to approve.
XOR-style workflows (exclusive path).
Additional Notes
Activation condition (IF rule):
Can be combined with activation policy. Example:
Activation Policy = All
Activation Condition = context.invoice.amount > 20,000
→ Task activates only if all predecessors are closed and condition is true.
Terminal tasks - Tasks can be marked as terminal, meaning their completion signals the end of the process, regardless of other pending tasks.
Last updated