SailPoint Variables & arguments
Workflow variables, arguments, the workflow context and how data flows between steps in SailPoint IdentityIQ.
In an IdentityIQ workflow, variables hold state for the life of the process and can be initialised from a script, flagged as input, output or required, and read or written by any step. Steps and calls take arguments in and return results out, usually as scripts or variable references. Inside scripts, the workflow, step and workflowcontext objects reach them.
- Variables persist process state; arguments move data per call
- Variables can be input, output or required
- workflowcontext exposes engine services to scripts
- Know the common LCM variables: plan, project, approvalSet, flow
Variables
Workflow variables hold state for the life of the process. They can be initialised from a script, marked input/output/required, and read or written by any step.
Arguments
Steps and calls pass arguments in and return results out. Argument values are usually scripts or references to variables, letting you shape data as it moves.
The workflow context
Inside scripts, the workflow, step and workflowcontext objects give you access to variables and engine services such as launching subprocesses or adding messages.
Common variables
identityName, plan, project, approvalSet and flow are variables you will meet constantly in Lifecycle Manager workflows.