Is this an example of a mover lifecycle event? Solution: A contractor whose contract expired and accounts were disabled has a new contract with the…

The scenario describes a "Leaver" event followed by a "Rehire" event. A "Mover" event applies to an active identity that changes roles, departments, or other key attributes while maintaining a continuous relationship with the organization. In this case, the contractor's relationship was terminated when their contract expired and accounts were disabled. The new contract initiates a rehire process, which is a type of "Joiner" event, not a "Mover" event. The break in service is the key factor that disqualifies this from being a mover lifecycle event.

A. Yes: This is incorrect because a mover event requires a continuous employment or contract status. The scenario explicitly describes a termination followed by a new contract.

1. SailPoint IdentityIQ 8.1 Lifecycle Manager Guide, "Chapter 1: Introduction to Lifecycle Manager", Page 5. The guide defines the three primary lifecycle events: Joiner (new user), Mover (changes for an existing user, e.g., transfer), and Leaver (user termination). The scenario clearly depicts a Leaver event followed by a Joiner (rehire) event.

2. SailPoint IdentityIQ Concepts Guide v7.1, "Identity Lifecycle Management", Page 4. This document explains that lifecycle management automates processes for "hiring, termination, and job changes." A mover event is categorized under "job changes" for an existing, active identity, not for an identity that was terminated and is now returning.

3. SailPoint IdentityIQ Administration Guide v8.3, "Chapter 20: Lifecycle Manager", Section: "Lifecycle Events". This section details how events are triggered based on changes in identity attributes. A mover event is triggered by a change in an attribute like department or location for a currently active identity, not by a change from an inactive to an active state after a period of separation.