The identity attribute rule natively provides the oldValue for the attribute rule it is assigned to, but I am looking to incorporate logic that depends on the old value of another identity attribute that I am expecting to change inside a rule for a different attirbute.
For example, in my cloudLifecycleState rule, I want to know if during a refresh, the old (most recent previous) value of department is different from the current value that would have been set during the authoritative source refresh that provoked the identity refresh.
From the triggered rule you want to check the source of the refresh task that triggered this rule?
If the above is the use-case that you want to achieve then it is not possible using the rule. If there is something specific you want to check or trigger based on attribute change then you may take look on workflow.
Hi @ashutosh08 ,
I have several cases where I had hoped to achieve this. I can maintain the current lifecycle state in the rule and move the logic into a workflow.
Suppose that if I decide the current active lifecycle state should be set to disabled in the workflow due to the changes I detect, how do I transition the cloudLifecycleState value from within the workflow?