I had a question regarding lifecycle states and attribute sync behavior in ISC.
If an identity is moved to “Inactive(long-term)”, does ISC automatically stop attribute synchronization/updates from sources (e.g., HR aggregation)?
Or do we still need to explicitly handle this using transforms or rules to prevent updates for those identities?
I came across documentation suggesting long-term terminated identities are excluded from processing, but I want to confirm whether that applies only to lifecycle events/provisioning or also to attribute sync.
Thanks, Manish. We are looking to stop attribute sync for these identities and are not seeking any updates to the identities unless they are rehired. So, we are good with SailPoint not updating. Thankyou.