Steps & transitions
Quick answer
Steps, transitions, approvals and subprocesses in SailPoint IdentityIQ workflows, and how control flows between them.
Key takeaways
- Steps do the work; transitions decide the path
- Transition conditions branch the process
- Approval steps pause and wait for work-item decisions
- Subprocesses keep workflows modular and reusable
Steps
A step is a unit of work: it can run an action (a script or rule), call a subprocess, present an approval, or simply mark Start/Stop. Steps have names, icons and optional result variables.
Transitions
Transitions connect steps and carry a condition. The engine evaluates transitions in order and follows the first whose condition is true, giving you branching logic.
Approvals
Approval steps pause the workflow and create work items for approvers. The workflow resumes when approvals complete, with the decision available to later steps.
Subprocesses
A step can launch another workflow as a subprocess, letting you reuse common logic such as provisioning or notifications across many parent workflows.
Want to learn this properly?
Our live, instructor-led SailPoint Training covers this hands-on, with real projects and a certification path.
Check your understanding
What carries the condition that decides the next step?
- A. The variable
- B. The transition
- C. The handler
- D. The connector
Show answer
B. The transition
Transitions carry conditions and the engine follows the first true one.