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

ServiceAccount Account Name Generation

ejeong
Valued Contributor
Valued Contributor

Hello 

We have dynamic attribute showing possible account name in list. 

when user selects one of value in the list, we want to populate this value in account name and account name field shouldnt be editable.

Can anyone tell me how to achieve this?

for now, I need to click "generate" button to populate the value

ejeong_0-1658212166640.pngejeong_1-1658212183341.png

 

Also, I can enter different account name as well.. we want to block this..

7 REPLIES 7

sahajranajee
Saviynt Employee
Saviynt Employee

Hi @ejeong ,

The expected approach is to Click Generate. When you click 'Generate', it will evaluate the Account Name Rule for Service Account set on the Endpoint level.

The Service Account Account Name Rule can be used to fetch values of Dynamic attributes and The Account type selected and generate the service account name once the button is clicked.

 


Regards,
Sahaj Ranajee
Sr. Product Specialist

ejeong
Valued Contributor
Valued Contributor

Thanks.

Then can i block user to submit request when dynamic attribute != account name ? There will be a case user enters account name manually instead of clicking generate.. how can we prevent this submitted?

sahajranajee
Saviynt Employee
Saviynt Employee

Hi @ejeong ,

We cannot disable the user input from any configuration. You can have a go at it by making gsp changes but it will not be recommended.
Rather, you could look at handling this in the workflow. 
1. Lets say you have a dynamic attribute 'Name List' form which user selects the name.

2. Now the user clicks Generate and the account name becomes same as the selected name.

4. Lets say the user for some reason chooses to edit and add a name themselves and submits the request.

5. You can then have a condition on the workflow to compare the 'Proposed Account Name' and 'Name List' selection and if it does not match, you can move the workflow to reject block which  can have an email template that tells him via mail why his request was rejected.

 


Regards,
Sahaj Ranajee
Sr. Product Specialist

ejeong
Valued Contributor
Valued Contributor

thanks for quick feedback.. can you please let me know the query i need to add in "if-else" block for auto reject?

 

sahajranajee
Saviynt Employee
Saviynt Employee

Hello,

You can use something like :

dynamicAttributes.get('ACCOUNTNAME') eq dynamicAttributes.get('AccountNameList')

Where ACCOUNTNAME is the accountname generated after clicking 'Generate'/manually editing it  and 'AccountNameList' is the DA that will be having the list of Account Names available as per your design.


Regards,
Sahaj Ranajee
Sr. Product Specialist

ejeong
Valued Contributor
Valued Contributor

got it. 

can I use all upper case for "ACCOUNTNAME"? or do I have to use like 'accountName'?

dynamicAttributes.get('ACCOUNTNAME')

 

sahajranajee
Saviynt Employee
Saviynt Employee

Hello @ejeong ,

Please use the one i suggested on my reply above (full upper case)


Regards,
Sahaj Ranajee
Sr. Product Specialist