Predecessors

In a workflow, tasks rarely exist in isolation. They are usually connected by dependencies that determine execution order.

Predecessors

Each task can reference one or more predecessor tasks.

• A predecessor is a task that must reach a certain state (usually done, skipped, or cancelled) before the dependent task can activate.

• The relationship is evaluated according to the task’s activation policy (All / Any).

Example:

• Task: Manager Approval

• Predecessors: Upload Invoice

• Activation policy: All

→ Task becomes active once invoice upload is finished.