Native Change is not getting detected while using selector rule

Which IIQ version are you inquiring about?

Version 8.3

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

Hi Team,

I am facing issue while working on Lifecycle event based on Native Change Detection, when I select All or Match List in selection criteria it works fine, but when I switch to identity selection rule, Native Change is not coming in Identity profile, any idea why?

Regards,
Saket

Share your rule, is the config same as matchlist

Well, first thought that comes to my mind is that the selection ryle is not correct and does not include identity you want. Can you confirm if it is correct?

import sailpoint.object.Identity;
import org.apache.commons.logging.Log;
import org.apache.commons.logging.LogFactory;

List nativeChangeList = new ArrayList();
boolean notificationFlag = false;

try{
if(identity!=null){
nativeChangeList = identity.getNativeChangeDetections();
if(nativeChangeList!=null && !nativeChangeList.isEmpty()){
notificationFlag = true;
}
}
}
catch(Exception e){
log.error(“Exception occured in Native Change Rule Notification” + e);
}
return notificationFlag;

@Saket95606

Your Included Identities rule should be doing the same as you did in match list, it is filtering the identities and I don’t think you should rely on Native change detections here

Your rule should return condition to satisfy if for the user life cycle event should trigger if there is a native change.

Can you please share your exact requirement here, so that we can suggest accordingly.

looks like there is a confusion between event type and include identities.

Hi Saket,
As Satish already mentioned - identity selector in identity lifecycle events is used to limit scope of identities that are impacted by the event trigger. It can be used if you want to for example create a trigger which will work only for people within some certain departament. In your case you have to just create and identity event for native change trigger (and if you want to limit it only to certain identities - with identity selector) - than you start the workflow and in the workflow you have to decide what to do.

Simply speaking you don’t have to handle native change detection manualy - you can just do that OotB - like here

@kjakubiak and @iamksatish: Let me give it a shot :slight_smile:

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