Workflow basics
How SailPoint IdentityIQ workflows work: the workflow engine, process definitions, steps, variables and when workflows run.
How SailPoint IdentityIQ workflows work: the workflow engine, process definitions, steps, variables and when workflows run.
- Workflows are XML Workflow objects run by the IdentityIQ workflow engine
- Steps are connected by transitions from Start to Stop
- They power Lifecycle Manager, refresh and certification remediation
- State is persisted so long-running approvals survive restarts
What a workflow is
A workflow in SailPoint IdentityIQ is a business process modelled as a Workflow object (XML) and executed by the workflow engine. It orchestrates the steps that run when identities change, access is requested, or a lifecycle event fires.
The workflow engine
The engine walks a process definition from a Start step to a Stop step, following transitions. Each step can run a script, call a rule, launch a subprocess, or wait for an approval. State is persisted so long-running processes survive restarts.
Where workflows are used
Workflows drive Lifecycle Manager (access requests, joiner/mover/leaver), identity refresh triggers, certification remediation and custom automation. They are the glue between an event and the provisioning that results.
Anatomy of a Workflow object
Every workflow has variables, steps, transitions and optional handlers. You edit them in the Business Process Editor or directly in XML for full control.