How to handle users with same name
Hi, I'm asking community what type of solutions are you using to handle users with same first name and surname. As you know the Identity is created based on user first name and last name and in def...
Forum Discussion
Good Morning
Personally, I would recommend keeping the user's actual First Name and Last Name intact and making only the Alias Identity unique. For example, the provisioning process could automatically create identities such as:
- John Smith
- John Smith (2)
- John Smith (3)
or
- John Smith
- John Smith [jsmith2]
This keeps forms, searches, workflows, and notifications displaying the user's real name while satisfying the Identity uniqueness requirement.
I would avoid adding identifiers directly to the Last Name field, as that can become visually distracting and affect the user experience throughout the system.
Regards
Michael
Hi,
The visibility issue is that what I'm thinking also. The user itemtype first name and last name is not unique and thus user is created Aras automatically creates the Alias Identity that name needs to be unique. This is combination of user first name and last name.
Problem is that this is one of the core methods and I'm not keen of poking that,
