• State Suggested Answer
  • Locked Locked
  • Replies 1 reply
  • Answers 1 answer
  • Subscribers 62 subscribers
  • Views 1533 views
  • Users 0 members are here
Options
Related
This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

User Creation Workflow - Name Collisions

dylan smith
over 5 years ago

I've set up a workflow that creates secondary Admin Accounts based off of the first character of a first name, last name, and then 'a'. So John Smith would be JSA@xxxx.com. It works great except for when we already have a Jake Sam for instance. It simply does not create the admin account. Is there a way to force error handling to recognize the collision and do anything with the issue?

  • 0 over 5 years ago

    Hi Dylan,

    In this case, I would suggest targeting a specific container for these admin accounts where you can create and assign a Logon Name Generation Policy that will contain a rule to build the logon name with the option of adding a uniqueness number in case an existing account is found. Remove the calculations to provide the logon name from the workflow and let the policy do the work.

    Have a look at the screen shot for the above example rule.