Variables & arguments
Quick answer
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. 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.
Key takeaways
- 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.
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 persists state for the whole process?
- A. Arguments
- B. Variables
- C. Transitions
- D. Handlers
Show answer
B. Variables
Variables hold state for the life of the workflow; arguments are per-call.