Hello,
I understand that SailPoint process events based on snapshots.
For example, if a Leaver is triggered based on Inactive attribute changed, can those pending events be found based on comparison between Identiy cube and a snapshot.
Is it possible to find Lifecycle Events that have been identified but not yet triggered?
@smergea If it is based on certain attributes, you can do it. You can join your identity table and audit table to figure out how many users with inactive=true but there is not audit for termination event.
what I do is create populations base on same filters as the events. easy way of looking at what identities match.
this is an effective way of telling the in-scope population. but you need another searchable identity attribute to support the population conditions to determine if event trigger or not.
Hi @neel193 ,
my request was something like this:
If I trigger now an Identity Trigger task to process events, how could i know how many JMLs will be triggered, how many are in this ‘awaiting/pending’ state?
Thank you,
Sergiu
@smergea Identity Refresh task with Process Events options doesn’t know before hand how manys users will be eligible for JML. It initiate the task and start processing the user one by one against the active life cycle events. to do so, it evaluates the identity against the IdentityTrigger condition (Event Type) which is written and returns true or false for each active events in the system.
One way to know how many JMLs will be triggered before hand to write a rule to evaluate all users against the identity trigger condition and store the result. This will tell you how many users are flagged for JMLs.
Note: Found a fix? Mark it as a solution! Want to say thanks? Give Kudos to anyone who helped you understand or solve the problem. Thanks..!!!