Please be sure you’ve read the docs and API specs before asking for help. Also, please be sure you’ve searched the forum for your answer before you create a new topic.
I have a use case I am trying to solve when the user is created in a staged state (not started yet), We are expecting name changes to happen even before the user starts and hence notifications are required to be sent. The AD account gets created in this state and we get the UserDN attribute to check when the changes happen at different LCS states
Looking at your WF, you are looking to take action only when the old UserDn has a value.
If that is the case, you can make use of a filter as below in the Identity attributes changed trigger, so that the WF will trigger only when old UserDn has a value
Currently, the trigger I’m using is designed to detect changes in email addresses - $.changes[?(@.attribute == “email”)].
The rationale behind this trigger is to ensure that when a name is updated in the HR source, the user DN is also updated accordingly. This requirement applies to all lifecycle states.
The trigger works effectively in cases where the userDN is present, such as pre-hire and active states. However, in scenarios where the AD (Active Directory) account is not yet created, as in the staged state, we intend to exclude those cases since they are part of the onboarding process.
Trigger: The workflow is triggered by an event related to changes in email attributes.
Get Identity: Retrieve user’s identity object
Define Variable – now, userstartdate and UserDNold
Check to see if the userDN attribute is null.
If null: End Step – Success 6
Else Compare String where now = Users Start date (Anything before this is considered as an onboarding event and should be ignored)
If True: End Step – Success
If False – Verify Data Type