Hi Daniel! Thank you for idea! I already have an extra state (in fact I have 1 active state, 3 states that disable accounts -vacations and medical leave (short) - and terminated, and let’s call it “manually deactivated”). Manually Deactivated turns all accounts to disabled. Problem is that at following aggregation from RH, it will prevail what comes from RH. That’s why I am tring to find some flag that can use in the Lifecycle transform to let prevail the manual assigned state.
At now we found a workaround. I have now a workflow that triggers reacts to the Identity Attributes Changed trigger, when it is going into the “Manually Disabled” state. Then it performs an API call to RH so ISC inform to send some flag which can be captured by the LCS transform.
This will work, but if something arises that can prevent RH from make changes should be welcome.