We are delighted to share our new EIC Delivery Methodology for efficiently managing Saviynt Implementations and delivering quick time to value. CLICK HERE.

Endpoint -Dynamic Attribute - Parent and Child attribute - auto populate values in child attribute

sreehariv
New Contributor III
New Contributor III

Hello Team,

We have a requirement to auto populated and non editable  dynamic attribute filed in ARS page based on the value selection of parent dynamic attribute filed. 

We have configured "Refresh" as a value for "What action to perform when Parent attribute changes?" instead of mapping for Parent Dynamic Attribute configurations.

So when we select some value in parent attribute the page is refreshed and some value has to be selected in child attribute but that's not working.

 

Child attribute is non editable.

 

Parent attribute - Service_Location

child attribute: WorkLocationRID:  

Query:

select ev.entitlementID as ID from entitlement_values ev join entitlement_types et on et.ENTITLEMENTTYPEKEY = ev.ENTITLEMENTTYPEKEY join endpoints ep on ep.ENDPOINTKEY = et.ENDPOINTKEY where et.ENTITLEMENTNAME = 'WorkLocation_XXX' and ep.endpointname = 'XXXXX' and ev.entitlement_value = ${Service_Location}

We have configured "Mapping" as a value for "What action to perform when Parent attribute changes?"

 

Requirement: 

Based on selection of Parent attribute value , child attribute value has to be selected and non editable. 

 

Please let us know if we have any resolution for this to make this as works as expected. 

 

 

Thanks 

Sreehari

6 REPLIES 6

Dhruv_Sharma
Saviynt Employee
Saviynt Employee

Hi @sreehariv 

Could you please share the full screenshot from the parent and child Dynamic attribute along with the query. You should use the mapping instead of refresh when you want to map the child attribute based on the value of parent attribute.

Regards,

Dhruv Sharma

Yes Dhruv, We have tried that initially and it did not work. Hence we have tried refresh for parent attribute and even this doesn't work for child attribute.

 

I can give you the screenshots in my next reply. Facing some issues with the encvironment.

 

Thanks

Sreehari

 

sreehariv
New Contributor III
New Contributor III

Hello @Dhruv_Sharma ,

attached the screenshots for Parent and Child attributes.

Parent Dynamic Attribute query:

select ev.ENTITLEMENT_VALUE as ID from entitlement_values ev join entitlement_types et on et.ENTITLEMENTTYPEKEY = ev.ENTITLEMENTTYPEKEY join endpoints ep on ep.ENDPOINTKEY = et.ENDPOINTKEY where et.ENTITLEMENTNAME = 'XXXXXX' and ep.endpointname = 'XXXXXX'

 

Child Dynamic Attribute query:

select ev.entitlementID as ID from entitlement_values ev join entitlement_types et on et.ENTITLEMENTTYPEKEY = ev.ENTITLEMENTTYPEKEY join endpoints ep on ep.ENDPOINTKEY = et.ENDPOINTKEY where et.ENTITLEMENTNAME = 'WorkLocation_XXX' and ep.endpointname = 'XXXXX' and ev.entitlement_value = ${Service_Location}

Please refer to the screenshots and let us know if you need anything on this.

Issue: Based on the selection of parent attribute, child attribute value is not being auto selected (in non editable mode)

Thanks

Sreehari

Hi @sreehariv 

Please find the below findings based on the queries you have mentioned.

1. Both the queries works fine after removing the portion where et.ENTITLEMENTNAME = 'XXXXXX' . Could you please elaborate what you are using as ENTITLEMENTNAME attribute with example.
2. Refresh is used in child DA to make the child attribute refreshed with the value based on parent attribute.
3. Child query gives nothing but same value as parent value hence not clear what is the purpose of using it as the child attribute here.

 

Please find the working queries tested in our environment along with the screenshot. Based on the below you can modify queries as per your environment. I would recommend you to test the queries in the data analyzer before using it in Dynamic attributes.

Working parent query
select ev.ENTITLEMENT_VALUE as ID from entitlement_values ev join entitlement_types et on et.ENTITLEMENTTYPEKEY = ev.ENTITLEMENTTYPEKEY join endpoints ep on ep.ENDPOINTKEY = et.ENDPOINTKEY where ep.endpointname = 'testad'


Working child query
select ev.entitlementID as ID from entitlement_values ev join entitlement_types et on et.ENTITLEMENTTYPEKEY = ev.ENTITLEMENTTYPEKEY join endpoints ep on ep.ENDPOINTKEY = et.ENDPOINTKEY where ep.endpointname = 'testad' and ev.entitlement_value = ${Service_Location}

DA_TEST_Attributedetails.PNGDA_TEST.PNG

Regards,
Dhruv Sharma
If this reply answered your question, please accept it as Solution to help others who may have a similar problem.

Hello @Dhruv_Sharma ,

We have tried the above suggested solution and again its the same issue, the child attribute value  is not getting auto populated based on the selection of parent.

Below are the further details and attached the screenshots for reference.

For Parent we kept "Mapping" and for child we kept "Refresh" as action of change. Modified the queries suggested as per the above and still no change. Issue persists.

Actually we need to send the entitlement ID value in the create account when we select the Entitlement value from the UI. 

(When user selects entitlement name in ui, entitlement ID value should sent in the create account json)

seems like saviynt doesn't support this requirement through dynamic attributes, we have added two dynamic attribute fields -  one is for entitlement name display and the other is for entitlement id display in the ARS page. Once you select the entitlement value, the corresponding entitlement id should get auto selected with read only  in next filed (Parent - child). But this is not working with the above suggested solution. 

The reason why we are checking for Entitlement name from Entitlement type table is we want to display only one particular type of entitlements in the Service_Location field. 

 

Do we have any other approaches for this requirement?

We found the below but that doesn't fulfil our requriement. Please suggest.

https://forums.saviynt.com/t5/identity-governance/endpoint-dynamic-attribute-display-and-actual-valu...

Hi @sreehariv 

1. Please remove Mapping from Parent attribute and keep Refresh in child attribute.

2. Also please validate both the queries in data analyzer if they give expected results. If both the queries work in data analyzer then it is supposed to work in DA as well.

3. When you go to ARS and select the value of the Parent attribute, please collect the logs at that time and share.

4. One more thing I observed from the ARS screenshot is that the value of Service location is showing with double quotes ("VIP"). It may cause an issue with comparison in child attribute query.

Logs can provide more information.

Regards,

Dhruv Sharma