Study guide

5.1 Lifecycle Events and Their 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

5.1 Lifecycle Events and Their Workflows

Key Takeaways Explain This Topic AI

Lifecycle events are configured on Setup > Lifecycle Events and are evaluated by Identity Refresh when the Process Events option is enabled.

The event types are Create, Manager Transfer, Attribute Change, Rule, Native Change, Alert, and Rapid Setup.

Attribute Change events can filter on previous and new values, and Manager Transfer events can filter on previous and new managers.

Each event selects a business process to launch; lifecycle events are the one place where workflows of any type can be triggered.

Identity processing thresholds (fixed or percentage) stop the refresh before a flood of accidental events is processed.

Last updated: September 2026

Lifecycle Events and Their Workflows

Objective 2.4 asks you to configure lifecycle events and their associated workflows . A lifecycle event is a rule that watches for a change to an identity, such as a new hire, a new manager, or a status changing to inactive. When the change is detected, it launches a business process that grants, changes, or removes access. This is IdentityIQ's native joiner-mover-leaver engine. Rapid Setup (section 5.4) is a guided layer on top of the same ideas.

Where and When Events Fire

Configure events on Setup > Lifecycle Events . Each row shows the name, type, attribute (for Attribute Change), owner, and whether it is disabled.

Events are evaluated by the Identity Refresh task when Process Events is selected. Aggregation stores snapshots that approximate each identity's previous state. Refresh compares that snapshot with the updated identity to decide which events apply.

Aggregation alone does not launch lifecycle events. The usual schedule is: aggregate the authoritative source, then refresh with Process Events . Many teams use Refresh only identities marked as needing refresh during aggregation to keep this incremental.

The Seven Event Types

  • Event type Fires when Type-specific settings
  • Create A new identity is discovered None beyond the population
  • Manager Transfer An identity's manager changes Previous Manager Filter , New Manager Filter (blank means any)
  • Attribute Change A chosen identity attribute changes Attribute , Previous Value Filter , New Value Filter
  • Rule A rule returns true Rule (the IdentityTrigger rule type)

Native Change A change is detected directly on an application configured to report it Native change detection on the application

  • Alert An alert is triggered None beyond the population
  • Rapid Setup The selected Rapid Setup process is detected RapidSetup Process

A classic leaver is an Attribute Change event on inactive with New Value Filter = true . A classic mover is a Manager Transfer event, or an Attribute Change on department or location. A classic joiner is a Create event.

Common Settings for Every Event

Name and Description . The name identifies the event but is not shown on the requests it creates.

Include Identities limits which identities the event applies to: None (only listed identities), All , Match List (identity attributes, application attributes, or permissions), Filter , Script , Rule , or Population . Use it, for example, to run a contractor leaver process only for identities whose type is Contractor.

Threshold Type and Threshold Value set an identity processing threshold . Fixed needs a whole number greater than 1. Percentage needs a whole number from 1 to 100. If an HR mistake marks a whole department as terminated, the threshold stops the Identity Refresh task before any identity is updated and fails the task result with a message. With partitioned refresh, the count is cumulative across partitions. The refresh option Disable identity processing threshold switches the check off for one task.

Business Process is the workflow to launch.

Disabled turns the event off without deleting it.

The Associated Workflows

IdentityIQ ships lifecycle workflows of the Identity Lifecycle type: Lifecycle Event – Joiner , Lifecycle Event – Manager Change , Lifecycle Event – Leaver , and Lifecycle Event – Reinstate . They build provisioning plans (for example, disabling accounts for a leaver or notifying the new manager for a transfer). They reuse the same Identity Request subprocesses as LCM, so approvals, forms, provisioning, and notifications work as they do in section 4.3.

Customizing follows the usual pattern: copy the product workflow, change its variables or steps, and select the copy in the event's Business Process field. The workflow-types documentation adds that workflows with custom types can be triggered only from Lifecycle Events , which can launch a workflow of any type.

Loading diagram... How a lifecycle event runs

Worked Example: A Contractor Leaver

Requirement: when a contractor's inactive flag becomes true, disable their accounts, notify their manager, and never run the process for employees.

Event Type: Attribute Change. Attribute: inactive . Previous Value Filter: false . New Value Filter: true .

Include Identities: Match List with type = Contractor , so employees are never selected.

Threshold: Percentage, 5. If the number of identities triggering the event reaches the threshold (five percent of identities), the refresh stops before updating anyone.

Business Process: a copy of Lifecycle Event – Leaver with its notification variables set to include the manager.

Schedule: HR delta aggregation, then Identity Refresh with Refresh identity attributes , Process Events , and Provision assignments , limited to identities marked as needing refresh.

Test it by editing a test contractor's inactive value in a non-production HR file. Run the two tasks, check Task Results for the launched workflow, and read the redirected email (section 3.4).

Lifecycle Events vs. Certification Events

A lifecycle event launches a business process . A certification event (Setup > Certifications) uses the same kinds of triggers to launch an access review , for example certifying a mover's access when the manager changes. If a question asks you to "launch a workflow," it is a lifecycle event. If it asks you to "launch a review," it is a certification event (section 6.1).

Troubleshooting Checklist

Did aggregation actually change the attribute? Check the identity's attributes and history.

Did Identity Refresh run with Process Events selected?

Is the event enabled , and do its filters and Include Identities match the identity?

Did a threshold stop the refresh? Check the task result message.

Did the business process start? Check Task Results or the workflow case, and turn on trace in the workflow if needed.