12-04-2022 10:02 AM
Hi Team,
We are restricting the user attributes based on the SAV role (ROLE_A, ROLE_H,ROLE_M)
Parent attribute: Email required?(YES,NO)
And it's Child attribute:- O365 License? ("E1","E3")
I'm not sure if it something issue with the version
I could able to hide the parent attribute for ROLE_M by adding it in the Action String of the role attribute, Since the parent attribute was hidden for ROLE_M, saviynt should hide its child attribute as well, but saviynt is not hiding those attributes.
After that, I directly added the child attribute to the Action string of ROLE Attribute, but still, saviynt is not hiding those attributes for ROLE_M
Can the team help me with this?
12-04-2022 11:40 AM
Can you share dynamic attribute configuration
12-04-2022 07:36 PM
Hi Rushikesh
PFA the configuration details
Parent attribute
Action String :
HIDE###C_UdynO365LicenseType_W###Please select Email required or not___HIDE###C_UdynO365LicenseType2_W###Please select Email required or not___SHOW###C_UdynO365LicenseType_W###Yes___SHOW###C_UdynO365LicenseType2_W###No___HIDE###C_UdynO365LicenseType_W###No___HIDE###C_UdynO365LicenseType2_W###Yes___
1st Child attribute
Values : select distinct customproperty13 as ID from users where customproperty13 in ("E1","E3","E1_EMSE3")
2nd Child attribute
Values : select distinct customproperty13 as ID from users where customproperty13 ="No License"
SAV Role management role attribute
Values : select case when rolename='ROLE_HELPDESK' then 'HELPDESK' when rolename='ROLE_MANAGER' then 'MANAGER' when rolename='ROLE_ENDUSER' then 'ENDUSER' end as ID from users u, savroles s, user_savroles us where u.userkey=us.userkey and s.rolekey=us.rolekey and u.userkey = ${requestor} and rolename in ('ROLE_HELPDESK','ROLE_MANAGER','ROLE_ENDUSER') order by ID desc
Default Values : select case when rolename='ROLE_HELPDESK' then 'HELPDESK' when rolename='ROLE_MANAGER' then 'MANAGER' when rolename='ROLE_ENDUSER' then 'ENDUSER' end as ID from users u, savroles s, user_savroles us where u.userkey=us.userkey and s.rolekey=us.rolekey and u.userkey = ${requestor} and rolename in ('ROLE_HELPDESK','ROLE_MANAGER','ROLE_ENDUSER') order by ID desc
Action String SHOW###C_UdynLaptopRequired_W###ENDUSER___HIDE###C_UdynAccessCard_W###MANAGER___SHOW###C_UdynAccessCard_W###HELPDESK___SHOW###C_UdynAccessCard_W###ENDUSER___HIDE###C_UdynEmailRequired_W###MANAGER___SHOW###C_UdynEmailRequired_W###HELPDESK___SHOW###C_UdynEmailRequired_W###ENDUSER___HIDE###C_UdynO365LicenseType2_W###MANAGER___SHOW###C_UdynO365LicenseType2_W###HELPDESK___SHOW###C_UdynO365LicenseType2_W###ENDUSER___HIDE###C_UdynO365LicenseType_W###MANAGER___SHOW###C_UdynO365LicenseType_W###HELPDESK___SHOW###C_UdynO365LicenseType_W###ENDUSER
In the UI of update user form (attribute still present)
12-04-2022 07:50 PM
++Adding
1st page of parent attribute
12-04-2022 08:50 PM
There are extra underscore at end of action string
12-04-2022 09:30 PM
Hi Rushikesh
I removed the extra underscore from the Action String of the parent, still there is no change,child attribute is still visible in the update form
HIDE###C_UdynO365LicenseType_W###Please select Email required or not___HIDE###C_UdynO365LicenseType2_W###Please select Email required or not___SHOW###C_UdynO365LicenseType_W###Yes___SHOW###C_UdynO365LicenseType2_W###No___HIDE###C_UdynO365LicenseType_W###No___HIDE###C_UdynO365LicenseType2_W###Yes