Match List / Population Selection Configuration

[itzsam91 (Sam Le)]

Which IIQ version are you inquiring about?

Version 8.3

Please share any images or screenshots, if relevant.

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

Hi there,

This is in regards to the “Assignment Rule” on a Business Role.

We’re able to assign a custom population created through Advanced Analytics. But for our Advanced Analytics, we’re unable to utilize filtering for lastLogin / lastLogonTimestamp.

If we change the “Assignment Rule” to “Match List” - we’re able to add “Active Directory” as an Application Attribute and can now select lastLogin / lastLoginTimestamp.

Is there a way to pull the Active Directory attribute(s) into the XML to further filter out the custom Population?

Or is this something we have to configure via Identity Mapping?

On a side note; lastLogin / lastLoginTimestamp only have “Equals, Not Equals, and Is Null” as option. Is there a simple way to check for greater than xyz of Current date?

Thank you!

[enistri_devo (Emanuele Nistri)]

@itzsam91

Hi there,

This is in regards to the “Assignment Rule” on a Business Role.

We’re able to assign a custom population created through Advanced Analytics. But for our Advanced Analytics, we’re unable to utilize filtering for lastLogin / lastLogonTimestamp.

If we change the “Assignment Rule” to “Match List” - we’re able to add “Active Directory” as an Application Attribute and can now select lastLogin / lastLoginTimestamp.

Is there a way to pull the Active Directory attribute(s) into the XML to further filter out the custom Population?

Or is this something we have to configure via Identity Mapping?

On a side note; lastLogin / lastLoginTimestamp only have “Equals, Not Equals, and Is Null” as option. Is there a simple way to check for greater than xyz of Current date?

Thank you!

Hi @itzsam91,

yes, i think the best and easy way is create an IDN attribute like searchable and with ad attribute mapping.

Also, in the assignation rule, you need filtering for all the identities with and account AD and those attributes.

You can choose the second way for dont update DB.

I prefer the first one, because you use the IDN attribut for other operation, the leaver process for example

[uday_kilambi]

Hi @itzsam91 ,

I would suggest to use IdentitySelector rule or the rule type for Assignment rule which offers more flexibility to achieve the customization.

You can use the rule to get the active directory account of the identity and the specific attribute lastLoginTimeStamp from the account. You can add your logic of verification of number of days and return true accordingly.

I do not suggested a dedicated identity attribute for this requirement unless you need it for other requirements too.

Let me know in case of any questions.

Regards,
Uday Kilambi

[ashutosh08 (Ashutosh Singh)]

Hi @itzsam91,

Simple approach will be to have a searchable attribute and then use it. It will be simple to implement.

Thanks