Study guide
4.3 Configuring LCM Workflows
SailPoint Certified IdentityIQ Engineer Exam
Track your progress as you read
Finished sections get a check mark.
1 Chapter 1: The IdentityIQ Engineer Exam
1.1 Exam Format, Official Blueprint, and Study Strategy
2 Chapter 2: Infrastructure, Installation, and Extended Attributes
2.1 IdentityIQ Infrastructure Components 2.2 Installation Steps and Procedures 2.3 Creating Extended Attributes and the Objects That Support Them
3 Chapter 3: Build, Deployment, Patching, Access, and Email
3.1 Ongoing Build and Deployment 3.2 Installing Patches and Performing Upgrades 3.3 Configuring End-User Access 3.4 Email Server Settings and Email Redirection
4 Chapter 4: Lifecycle Manager Configuration, Provisioning Policies, and Workflows
4.1 Configuring Lifecycle Manager 4.2 Identity Provisioning Policies 4.3 Configuring LCM Workflows
5 Chapter 5: Lifecycle Events, QuickLinks, Batch Requests, and Rapid Setup
5.1 Lifecycle Events and Their Workflows 5.2 QuickLinks and QuickLink Populations 5.3 Configuring and Using Batch Requests 5.4 Rapid Setup in Lifecycle Events and Identity Operations
6 Chapter 6: Certification Campaigns and Certification Rules
6.1 Configuring and Scheduling Certification Campaigns 6.2 The Purpose of Common Certification Rules
7 Chapter 7: Policies and Policy Violations
7.1 Configuring and Leveraging Policies 7.2 Responding to Policy Violations
8 Chapter 8: Reporting, Advanced Analytics, and Auditing
8.1 Executing and Leveraging Reports 8.2 Leveraging Advanced Analytics 8.3 Configuring and Using Auditing
9 Chapter 9: Rules, Rule Libraries, and the SailPoint API
9.1 The Purpose and Use of Rule Libraries 9.2 Rule Input and Output Arguments 9.3 Common SailPoint API Objects and Methods
10 Chapter 10: Workflow Development
10.1 Workflow Variables, Transitions, and Step Conditions 10.2 Workflow Steps That Generate Work Items 10.3 The Different Workflow Step Usages 10.4 Leveraging Sub-Workflows
11 Chapter 11: Email Templates, Branding, and Localization
11.1 Customizing and Using Email Templates 11.2 Branding the SailPoint User Interface 11.3 Localizing the SailPoint UI
12 Chapter 12: Application Definitions, Connector Settings, and Rapid Setup Aggregation
12.1 Configuring Application Definitions 12.2 Configuring Common Connector Settings 12.3 Configuring Rapid Setup Aggregation Settings
13 Chapter 13: Data-Loading Tasks and Application and Connector Rules
13.1 Scheduling Tasks for Data Loading and Processing 13.2 Common Application Rule Types 13.3 Common Connector Rule Types
14 Chapter 14: Debugging with log4j, Syslog, and the IdentityIQ Console
14.1 Configuring and Leveraging log4j 14.2 Configuring and Leveraging Syslog 14.3 Leveraging the IdentityIQ Console for Debugging
15 Chapter 15: Debug Pages and the Administrator Console
15.1 Leveraging the Debug Pages for Debugging 15.2 Leveraging the Administrator Console for Debugging
16 Chapter 16: Role Model and Identity Attribute Mappings
16.1 Default Role Models and Role Types 16.2 Configuring Roles and Role Options 16.3 Configuring Identity Attribute Mappings
17 Chapter 17: Data Objects, Relationships, and Group Types
17.1 Common IdentityIQ Data Objects 17.2 Relationships Between Common Data Object Models 17.3 The Difference Between Group Types
4.3 Configuring LCM Workflows
Key Takeaways Explain This Topic AI
The default LCM business processes are LCM Provisioning, LCM Create and Update, LCM Manage Passwords, and LCM Registration.
LCM Provisioning runs the Identity Request Initialize, Violation Review, Approve, Provision, Notify, and Finalize subprocesses, plus the Provisioning Approval Subprocess.
approvalScheme chooses who approves (for example manager, owner, securityOfficer, or none), and approvalMode chooses how several approvers act (serial, serialPoll, parallel, parallelPoll, or any).
policyScheme decides how policy violations found during a request are handled, and notificationScheme decides who is emailed.
Copy an out-of-the-box workflow under a new name and select the copy on the Business Processes tab, because upgrades overwrite product workflows.
Last updated: September 2026
Configuring LCM Workflows
Objective 2.3 is configure LCM workflows . In IdentityIQ, workflow and business process mean the same thing. The UI says "business process," and implementers working with the object model say "workflow." Each Lifecycle Manager action launches the workflow selected for it on gear icon > Lifecycle Manager > Business Processes .
The Default LCM Workflows
- Workflow Handles
- LCM Provisioning Request Access (roles, entitlements, removals) and Manage Accounts
- LCM Create and Update Create Identity and Edit Identity
LCM Manage Passwords Password changes and resets on applications. By default it needs no manager or owner approval and emails the user.
LCM Registration Self-service registration from the login page
The workflow-type table in the documentation lists LCM Provisioning (Lifecycle Manager provisioning tasks), LCM Identity (identity tasks such as LCM Create and Update), and LCM Registration as separate types.
These four, plus Identity Update , appear in the Basic View of the Business Process Editor. That is a form view of the most commonly changed process variables. The Advanced View exposes every variable and step. Workflow types matter: the drop-downs on configuration pages list only workflows of the matching type.
How LCM Provisioning Is Built
LCM Provisioning is a master workflow that calls subprocess workflows:
Identity Request Initialize builds the IdentityRequest, compiles the plan into a project, and checks policies.
Identity Request Violation Review lets the requester review policy violations when the policy scheme is interactive.
Identity Request Approve , through the Provisioning Approval Subprocess , builds the approval set and creates approval work items.
Do Provisioning Forms collects missing data (section 4.2).
Identity Request Provision provisions the approved items, with retries through Provision with Retries .
Identity Request Notify sends notifications.
Identity Request Finalize completes the IdentityRequest record that powers request tracking.
Knowing this chain helps with troubleshooting. For example, a request that is stuck with no approval work item is a problem at the approval step, not a connector failure.
The Process Variables You Must Know
Variable Purpose Typical values
approvalScheme Who must approve none , manager , owner , securityOfficer , or a comma-separated combination such as manager,owner
approvalMode How multiple approvers interact serial , serialPoll , parallel , parallelPoll , any
fallbackApprover Receives the approval when the resolved approver does not exist Commonly initialized to spadmin
- policyScheme What to do when the request causes policy violations none , continue , interactive , fail
- notificationScheme Who gets emails For example user,requester,manager,securityOfficer
- securityOfficerName The identity used for the securityOfficer scheme An identity or workgroup name
- foregroundProvisioning Provision in the requester's session instead of in the background true / false
optimisticProvisioning Update the identity cube as if provisioning succeeded, without waiting for aggregation true / false
- enableRetryRequest Allow retries when a connector returns a retryable error true / false
- trace Write workflow trace output to the log true / false
- Approval Modes in Detail
serial – approvers are asked one after another, and one rejection rejects the item.
serialPoll – one after another. All answers are collected, and AfterScript logic decides the outcome.
parallel – everyone is asked at once, and one rejection rejects the item.
parallelPoll – everyone at once. Answers are collected, and AfterScript logic decides.
any – everyone at once, and the first response decides for the group.
Policy Scheme and What Requesters See
The request-violation behaviors in the documentation map to the policy scheme: reject and cancel a request with violations, reject interactively (the requester can change or cancel it), allow non-interactively (the request proceeds without notice), or allow interactively (the requester can change, cancel, or continue, possibly with a required comment or sunset date).
What the Variables Look Like in XML
Process variables are <Variable> elements with an initializer . The initializer is used only when no value is passed in when the workflow starts: <Variable name="approvalScheme" initializer="manager,owner" input="true"/>
- <Variable name="approvalMode" initializer="serial" input="true"/>
- <Variable name="policyScheme" initializer="interactive" input="true"/>
- <Variable name="notificationScheme" initializer="user,requester" input="true"/>
- <Variable name="trace" initializer="string:false"/>
The Basic View edits the same values through a form, so you rarely need XML for these changes.
Customizing Safely
Copy, do not edit, the product workflow. Clone LCM Provisioning (for example, "ACME LCM Provisioning"). Out-of-the-box workflows are overwritten during upgrades (section 3.2).
Change variables first, steps second. Most requirements, such as manager plus owner approval, parallel approvals, or failing on violations, are variable changes.
Point LCM at the copy on the Business Processes tab.
Test with trace on and email redirection (section 3.4), then turn trace off.
Run it from the console if needed. workflow "LCM Provisioning" provFile.xml runs a workflow with variables from a file, and validate checks a workflow definition without running it (section 14.3).
Beyond LCM Requests
Other workflows are wired in elsewhere. Lifecycle events are set on the Lifecycle Events page (section 5.1). The Identity Update , Identity Refresh , and role-change processes are set in Global Settings > IdentityIQ Configuration (Identities, Roles, and Miscellaneous tabs). Value change workflows are set on identity attributes, and policy violation workflows are set on each policy.