Changing Lifecycle State Calculation Logic

[dominick-miller]

Hi all,

I am going to update my lifecycle state transform to change how my organization calculates certain lifecycle states. I know that by doing this, the “source input” changes and SailPoint will recalculate all lifecycle states (even lifecycle states that have been manually set). I want to minimize disruption by turning off provisioning to AD while this is being done. After the transform has been changed, I will move the previously manually set identities back to their previous manual state. After this, I will reenable AD provisioning.

I want to ensure that I am not missing something in this process outlined above and there isn’t some queueing task mechanism where upon reenabling AD provisioning, SailPoint tries to perform a bunch of unnecessary changes.

If anyone has experience with this or has any thoughts, please let me know.

[naveenkarthikkrk (NAVEEN KARTHIK)]

Hi @dominick-miller
I have worked on similar use where I have disabled provisioning in AD so to prevent unnecessary changes in AD later I made changes in the logic of LCS.Now when I turn on the AD provisioning I starts to provisioning as we have configured ,when I tried there wasn’t any queueing task that happened,This is because when you are in a particular LCS it will try to provisioning as given in the below image

So ,it’s better to enable AD provisioning after 3 hrs of disabling it so that there won’t be any queuing task available.
Thanks!!