IIQ Leaver Workflow Rule not triggering

IdentityIQ (IIQ) IIQ Discussion and Questions
,
1

Which IIQ version are you inquiring about?

8.3

Share all details about your problem, including any error messages you may have received.

Hello,

I have a leaver workflow that should trigger whenever an identity’s endDate attribute is not null. However, I noticed that some users with a non-null endDate did not trigger the workflow. I am not sure why this happened. How can I troubleshoot this issue?

2

Hi @AlaaKhaled ,

Could you share the identity data snippet from debug page for the impacted user?
There may be possibility there exists some space/blank characters

3

Thanks @amit_1140 for your reply.
I will provide this information, but I have a question: even if there are spaces, why would the value be treated as null? I checked the Identity Warehouse, and the value for the endDate attribute is 30-OCT-2025.

4

How are you triggering this workflow. Is it through some rule or Lifecycle event.

Thanks

5

Hello @msingh900

It is triggered based on a rule which check for the current date to have a value
That’s why I cannot figure out what might be wrong

6

Are you converting the date value using date time Java api and then checking with current date or what is the logic in your rule. If you can explain that then it will be helpful to help you.

7

Hello @msingh900
Sorry I meant that the end date to have value which is attribute for the identity cube.
It has no value for all users , then when the user is a leaver the end date is set then the leaver rule has to trigger,

8

Take an identity with a non-null endDate that hasn’t triggered the workflow. Then, set endDate to null. Perform an initial Identity Refresh to update the identity cube. Next, verify that the end date is indeed null.

Then, change the end date of this identity from null to a non-null value, and perform a second identity refresh with the Process Events option enabled to see if this triggers the workflow. If it does, the rule works, and your logic is correct, except that it only triggers when there’s a change (event) and not due to a permanent state. This means that if the value was already non-null, it doesn’t process. But if it changes from non-null to null, it does.
The system compares the current state of the identity with its last snapshot to identify if a monitored attribute has changed. If the endDate attribute was already non-null in the last snapshot, and it’s still non-null, the system doesn’t consider that a new starting event has occurred.

SO, please do this test and let me know
@Manish Singh Do you agree with that?

9

Thanks @Hamza10 for your reply
I will try this and let you know the result
but I’m still confused why at first time of change from null to non-null it didn’t trigger the rule is there any way to troubleshoot this to avoid the behavior from happening again?
However the rule and logic is correct because lot of leavers already triggered once end date changed from null to non-null this is the first time we encounter this behavior for 4 users at same day which is suspicious .

10

Hi @AlaaKhaled Please create a separate rule try the same rule logic on an identity.

Question - Can you please share the rule code that you are using? Might be helpful to see what logic the rule has. It might be due to the two snapshots that you ususally have as part of this rule (previousIdentity and newIdentity)

11

This topic was automatically closed 60 days after the last reply. New replies are no longer allowed.