Workflow examples in SailPoint Examples

Workflow examples

Example IdentityIQ workflows for approvals and provisioning.

Quick answer

These workflow examples show approval routing and provisioning steps in the IdentityIQ workflow XML model.

Key takeaways

Approval and provisioning workflows
Step, approval and transition patterns
Adapt to your process
Test in a lower environment first

Workflows orchestrate approvals and provisioning as ordered steps in XML. These examples show the core patterns, an approval step, a transition, and calling a rule, that combine into real processes.

A manager-approval step

<Step name="Manager Approval">
  <Approval owner="ref:manager">
    <Arg name="workItemDescription" value="Approve access request"/>
  </Approval>
  <Transition to="Provision"/>
</Step>

Branching with a transition

<Transition to="High Risk Approval" when="script:identity.getAttribute(riskScore) > 500"/>
<Transition to="Provision"/>

Computing an approver in a step

<Step name="Compute Approver" resultVariable="approver">
  <Script><Source>return roleOwner != null ? roleOwner : identity.getManager();</Source></Script>
  <Transition to="Approval"/>
</Step>

Guidance

Start from the standard LCM workflows and customise.
Keep branching shallow and logic in named rules.
Add escalation so approvals cannot stall.
Test in a lower environment, a broken workflow blocks real access.

Common pitfalls

Deeply nested transitions that are impossible to debug.
No escalation on approvals.
Deploying untested workflow changes.

Practice challenge

+0 XPStreak ×0

Question 1 of 3

What do workflow examples show?

Frequently asked questions

What does the term Workflow examples refer to in SailPoint?

Workflows orchestrate approvals and provisioning as ordered steps in XML. These examples show the core patterns, an approval step, a transition, and calling a rule, that combine into real processes.

What is the practical takeaway on Workflow examples?

Start from the standard LCM workflows and customise. Keep branching shallow and logic in named rules. Add escalation so approvals cannot stall.

What tends to go wrong with Workflow examples?

Deeply nested transitions that are impossible to debug. No escalation on approvals. Deploying untested workflow changes.

Want this with a live instructor and a lab tenant?

SailPoint Developer training →