Usage of Included Identities option in LifecycleEvent

IdentityIQ (IIQ) IIQ Discussion and Questions
, , ,
1

Which IIQ version are you inquiring about?

8.4 P2

Hi Team

I need to trigger lifecycleevent for a list of users ID’s. The list of users is available in custom object. How can I read the user list in custom object and trigger life cycle event?

Trying to use the dropdown “Script” in the “Included Identities” option. What should be the return type of the script? and how the returned objects will be used by the lifecycle Event? Please share if any documentation is there around this.

Also, any of you have used this option in your implementation? If yes, Please share sample code.

Thanks

Divya M

2

In the included identities, you can select rule and, in that rule, check if the identity for which the LCE is evaulated is part of the custom object or not. if it’s then return true else false;

3

@DivyaSubha What are your other conditions to trigger LCE? If it is just that user part of the custom object, trigger the event. Then you can try keeping in the IdentityTrigger Rule (Event Type → Rule), then return true or false and no need to set the Included Identities.

4

There is another one criteria to be considered. isDormantUser should be true.

But the lifecycle event should be triggered for all the users having isDormantUser=true. IF the user is not present in custom file, then the user should be skipped.

5

@DivyaSubha You can write a rule in the IdentityTrigger to check if user is part of custom object and is dormantUser. Here is the sample code:



Custom customObj = context.getObjectByName(Custom.class, "customobjectname");
Attributes attr1 = customObj.getAttributes();
List includedUsers = attr1.get("keyname");

boolean isDormant = newIdentity.getAttribute("isDormantAttrName");

if(isDormant && includedUsers.contains(newIdentity.getName()))
return true;

return false;
6

Hi @neel193 Having the code to check the custom object increases the number of times the custom object is read. As a temporary solution, we added check in the Identity trigger rule. Keeping the Event “Disabled” helps reducing the number of times the custom object is read.

7

@DivyaSubha You can also store it in customGlobal to avoid accessing custom object multiple time. You can load it once and check if entry is there, if yes, then use the value which is there in custom global.

8

You can also use context.decache() at the end of you code. This will make the rule run faster.

9

It is not recommended to use context.decache(), always use context.decache(object). If you use decache(), it may lead to lazily initialization exception.

However, decache is not needed in IdentityTrigger rule.. When you are iterating over multiple identities, or handling multiple objects, then it is required to do decache periodically..

In identity trigger, you are only dealing with the single user at a time. so it’s not needed to do it.