Hello everyone.
I have this point of uncertainty about this use case, I’m not sure if this is expected or if I a missing something.
We have identities in LONG TERM INACTIVE state and their cloud life cycle state seems to be stuck and never recomputed. Is it the expected behavior ?
I thought at least, the LCS would be recomputed, because how do you manage a rehire else for example ?
Best regards
It depends on how you configured cloud Lifecycle attribute (Transform/Rule) in your Identity Profile, of course it will and it has to be re-computed.
Once your LCS change, LCS state will be updated as per your LCS.
Hello. Thank you for your answer.
What do you mean by “It depends on how you configured cloud Lifecycle attribute (Transform/Rule) in your Identity Profile” ?
In our case, it is a Static Transform.
How do you calculate your LCS, based on some attribute from your HR Source ?
Yes, it is mostly based on start and end date from the HR source.
Ok got it.
Do you mean to say, even though start/end dates are changed at HR system, your logic in static transform is working fine, still identity LCS is not re-calculated ?
If yes, then can you preview that Identity in your Identity Profile and see what is the value for LCS attribute.
The use case is that, identity has LCS “none” in LONG TERM INACTIVE when it arrives in ISC, then, some days before its start date, the LCS should change to “active”, but it is not, it stays in “none”, like LCS is not automatically computed each day. If we process the identity manullat, then it changes.
After getting start/end date, there might be no changes on that Identity, no events to trigger any refresh, so no re-calculation.
Better to add requirePeriodicRefresh to your transform. Check this post for more info.
Alright thank you we will definitely try this.
Any luck in next refresh if you added requirePeriodicRefresh to your Transform.
This topic was automatically closed 60 days after the last reply. New replies are no longer allowed.