Announcing the Saviynt Knowledge Exchange unifying the Saviynt forums, documentation, training,
and more in a single search tool across platforms. Read the announcement here.

Is there a way to generate Display Name as part of the user registration

Community_User
Saviynt Employee
Saviynt Employee
Originally posted on March 31 2020 at 02:58 UTC


Instead of allowing the user to mention the display name in the ARS-Create User form, we could like to generate it based of a combination of First name Last name.


Please suggest.

This message was previously posted on Saviynt's legacy forum by a community user and has been moved over to this forum for continued exposure.
3 REPLIES 3

Community_User
Saviynt Employee
Saviynt Employee
Originally posted on March 31 2020 at 07:16 UTC

As a part of Post-processing, a users import job could be utilized by considering Saviynt DB as source and in the SQL in XML for users import the logic to generate the display name could be mentioned.

This message was previously posted on Saviynt's legacy forum by a community user and has been moved over to this forum for continued exposure.

Community_User
Saviynt Employee
Saviynt Employee
Originally posted on April 2 2020 at 09:23 UTC

Hi Srikanth,


Trying to figure out a solution to generate the display name based on two attributes, and will come back to you as soon as possible.


In the meantime, here's a first lookup that you can do on your dynamic attribute to ensure the display name matches Firstname and Lastname :

Insert into "Validation Conditon" parameter the following value : ${displayName==(firstname+' '+lastname)} by updating it accordingly with your attributes' name.

You can also add a Failure Message to guide your users.


This message was previously posted on Saviynt's legacy forum by a community user and has been moved over to this forum for continued exposure.

Community_User
Saviynt Employee
Saviynt Employee
Originally posted on April 2 2020 at 16:51 UTC

Thank you so much for the reply. I will wait a you mentioned.

This message was previously posted on Saviynt's legacy forum by a community user and has been moved over to this forum for continued exposure.