Saviynt unveils its cutting-edge Intelligence Suite products to revolutionize Identity Security!
Click HERE to see how Saviynt Intelligence is transforming the industry.
Saviynt Copilot Icon

Hide a dependent Dynamic attribute from the Form || REST

DG1811
New Contributor III
New Contributor III

Hi Team,

We have a requirement where we are passing entitlements in the Create Account JSON using dynamic attributes.
Example :

Entitlement Value  :ABCD

Entitlement CP1 : 1(ID for ABCD)

Now we have two Dynamic attributes : 

DA1 :  Pulling the Entitlementvalue.

DA2 : Based on the selection of DA1, it will populate the corresponding ID value.

 

End user will have to select the DA1 and select the entitlement. Upon selection the DA2 will autopopulate and the user need to select that.

DA2 is the value that we are passing in the createaccount json.

Requirement is to hide the DA2 value in the ARS form, and when the user selects the DA1 value it will autopopulate the id value and pass it in create account json. 

Is there anyway we can achieve this to hide a DA value but pass the value in the create account json. 

Thanks

 

e

26 REPLIES 26

Raghu
All-Star
All-Star

@DG1811  you can only check it hide on create /update check it once

Raghu_0-1728042509440.png

 


Thanks,
Raghu
If this reply answered your question, Please Accept As Solution and hit Kudos.

DG1811
New Contributor III
New Contributor III

Hi @Raghu ,
Clicking on Hide to Create, will remove the DA visibility in the creation time. Whereas Clicking on Hide On Update will remove the DA visibility on the update scenario. 

 

But here the requirement is to pass the value after hiding also. So selecting DA1 should populate the DA2 value automatically (must not show in ARS form) and pass the value in the create account json. 

Thanks

NM
Esteemed Contributor
Esteemed Contributor

Hi @DG1811 hiding the DA won't allow you to pass the value.


If this helped you move forward, click 'Kudos'. If it solved your query, select 'Accept As Solution'

DG1811
New Contributor III
New Contributor III

Hi @NM ,
Is there any way we can check the DA1 selection value and then store the corresponding id value in Customproperty of accounts and then pass it in the create account json?

Thanks

We can't show like .


Thanks,
Raghu
If this reply answered your question, Please Accept As Solution and hit Kudos.

NM
Esteemed Contributor
Esteemed Contributor

@DG1811 if it is created account json you want to use then it means account doesn't exist so we can't store it anywhere.


If this helped you move forward, click 'Kudos'. If it solved your query, select 'Accept As Solution'

NM
Esteemed Contributor
Esteemed Contributor

@DG1811 make DA2 not editable. So it automatically computes the values.


If this helped you move forward, click 'Kudos'. If it solved your query, select 'Accept As Solution'

DG1811
New Contributor III
New Contributor III

Hi @NM ,

Thanks for the update. So in case of update account can we use it?

Thanks

NM
Esteemed Contributor
Esteemed Contributor

@DG1811 store in one of the customproperty and use the value.

If the suggestion helped you plus click on kudos button and accept the solution.


If this helped you move forward, click 'Kudos'. If it solved your query, select 'Accept As Solution'

rushikeshvartak
All-Star
All-Star
  • If you hide DA2 then it won't be parsed on create account json.
  • You need to keep editable and if you want to be prepopulated then keep same query in default value so user can't even change.

Regards,
Rushikesh Vartak
If this helped you move forward, click 'Kudos'. If it solved your query, select 'Accept As Solution'.

Hi @rushikeshvartak / @Raghu  / @NM,

Thanks for the update.We will proceed with the knowledge on this.

Can you also please confirm, is there a way we can just populate DA1 in the ARS form on update scenario just as a non editable attribute. I tried deselecting the "hide on update" and only marked editable option, but in that case the user can change the DA1 in the update scenario.
Whereas the requirement is to have DA1 in create account json and in update/modify request , it will just be visible to the user but it wont comeup as editable. 

Can this be done? Please suggest. 

Thanks

You can add note to end user - don’t change value. In case user change you can validate in workflow and auto reject


Regards,
Rushikesh Vartak
If this helped you move forward, click 'Kudos'. If it solved your query, select 'Accept As Solution'.

DG1811
New Contributor III
New Contributor III

hi @rushikeshvartak , thanks for the update. We are connecting with the app team. 

@Raghu @NM 
Also there is a case, please see below. 

DA1 value is = abcd,uk

DA2 we are referring the value selected in DA1 using the below query.

SELECT DISTINCT ev.customproperty1 AS ID FROM entitlement_values ev where ev.entitlement_value in (${DA1}) and ev.entitlementtypekey = KEY

But the query is unable to fetch the DA2 value on the selections which has a Comma (',') field in the displayname. I tried using the below formats for the entitlement_value also.

ev.entitlement_value in (${DA1})

ev.entitlement_value = '${DA1}'

ev.entitlement_value = "${DA1}"

 

None of them worked, whereas if there are any special character other than ',' then its displaying the value of DA2 based on DA1 selection. 

Can you please suggest the changes in the query.

Thanks

NM
Esteemed Contributor
Esteemed Contributor

@DG1811 is DA1 multiselect or single select?

Same for DA2 multi select or single ..

If single select 

Use this 

SELECT DISTINCT ev.customproperty1 AS ID FROM entitlement_values ev where ev.entitlement_value = ${DA1} and ev.entitlementtypekey = KEY

 

Or 

SELECT DISTINCT ev.customproperty1 AS ID FROM entitlement_values ev where ev.entitlement_value = '${DA1}' and ev.entitlementtypekey = KEY


If this helped you move forward, click 'Kudos'. If it solved your query, select 'Accept As Solution'

DG1811
New Contributor III
New Contributor III

Hi @NM ,

DA1 is single select.

DA2 is single select too. 

I used the 1st suggestion, we are getting the query to populate in the field, rather than the value. 

DG1811_0-1728981439206.png

And the second query does not work. It does not even show the ones with proper data also. 

 

NM
Esteemed Contributor
Esteemed Contributor

@DG1811 does query populate for all or only for the comma one?


If this helped you move forward, click 'Kudos'. If it solved your query, select 'Accept As Solution'

DG1811
New Contributor III
New Contributor III

@NM , its just for the comma ones, others are populating the data.

NM
Esteemed Contributor
Esteemed Contributor

@DG1811 one provided by me also show the same behaviour?


If this helped you move forward, click 'Kudos'. If it solved your query, select 'Accept As Solution'

DG1811
New Contributor III
New Contributor III

@NM ,

I used this query provided by you.
SELECT DISTINCT ev.customproperty1 AS ID FROM entitlement_values ev where ev.entitlement_value = ${DA1} and ev.entitlementtypekey = KEY

and using this it shows the behavior that I have highlighted in the snapshot.

Thanks

NM
Esteemed Contributor
Esteemed Contributor

@DG1811 try this 

In DA1 query replace the comma with a different seperator.

In DA2 do the same and keep in instead of = in DA2 query


If this helped you move forward, click 'Kudos'. If it solved your query, select 'Accept As Solution'

DG1811
New Contributor III
New Contributor III

Hi @NM ,

DA1 query is as below.

SELECT DISTINCT ev.entitlement_value AS ID FROM entitlement_values ev where ev.entitlementtypekey = KEY and ev.customproperty2 like 'false';

Based on the selection from the above query we are passing the value in DA2 in the below query.

SELECT DISTINCT ev.customproperty1 AS ID FROM entitlement_values ev where ev.entitlement_value = ${DA1} and ev.entitlementtypekey = KEY

 

Can you please suggest what modifications needed in the DA1 please. 

Thanks

Please share logs


Regards,
Rushikesh Vartak
If this helped you move forward, click 'Kudos'. If it solved your query, select 'Accept As Solution'.

Hi @rushikeshvartak , @NM , @Raghu ,
We have noticed that the DA1 AND DA2 values are not auto populating upon entitlement import for the existing users. although the details are coming in the entitlement heirarchy. How to get the details visible in the ARS form, please suggest. 

Thanks

Did you stored in accounts column?


Regards,
Rushikesh Vartak
If this helped you move forward, click 'Kudos'. If it solved your query, select 'Accept As Solution'.

Hi @rushikeshvartak ,
Yeah the details are getting imported in the account import in one of the CP value.

 

Please share all required screenshot/account. ARS and logs in text file


Regards,
Rushikesh Vartak
If this helped you move forward, click 'Kudos'. If it solved your query, select 'Accept As Solution'.