Getting Dynamic attribute values via Analytics

[tpawle]

Hi Team,

We have a requirement create a disconnected application where we want the tasks to get created for dynamic attributes based on the selection of roles. This requirement is just the +1 additional step of the following requirement Re: Assigning default dynamic attribute multiselec... - Saviynt Forums - 61883

Now, since we cannot create tasks for dynamic attributes, we are trying to achieve this via actionable analytics but we are unable to get the values being populated in the dynamic attributes so that actionable analytics can trigger tasks for those dynamic attribute values.

Is there any way we can get the dynamic attributes values or schema where these values are stored in Saviynt database? Please feel free to drop your suggestions or any questions. 

Thanks

[pmahalle · Accepted solution]

Hi @tpawle ,

You need to use below tables in order to get dynamic attribute value

• ars_requests
• request_access
• request_access_attrs

Sample Query:

select distinct(raa.ATTRIBUTE_VALUE) from ars_requests ar, request_access ra, request_access_attrs raa where ar.REQUESTKEY = ra.REQUESTKEY and ra.REQUEST_ACCESSKEY = raa.REQUEST_ACCESS_KEY and ar.JBPMPROCESSINSTANCEID like '%<Provide your Request ID>%' and raa.ATTRIBUTE_NAME='<Provide your dynamic attribute name>'

Hope it helps.

[tpawle]

Hi @pmahalle 

Thanks for your response. I will try this approach and keep you posted.

Additionally, I need to get all the dynamic attribute values with not just one request but all the existing requests for the given endpoint so that whenever actionable analytics is triggered, the required set of tasks are created.

Also, would like to understand how actionable analytics can create tasks for these dynamic attributes.

Much Thanks 🙂

[rushikeshvartak]

Instead of using analytics convert dynamic attribute to entitlement type which will create task

[tpawle]

Hi @rushikeshvartak ,

Thanks for your response.

The request form should contain the dynamic selection of roles,region and branch and treating dynamic attributes as role would trigger the tasks.  We have created dynamic attributes so that request form can be designed in a way where it offers selection as per requirement.

The catch here is, how will the enduser who doesn't have access to this endpoint will be able to select different regions/branches if the mapping is already present between role-->region-->branch.

Thanks

[rushikeshvartak · Accepted solution]

You can make entitlement combination of Role-Region-Branch