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?
- Products
- View all products
- Free trials
- Privileged Access Management
- Overview
- PAM Essentials
- Safeguard
- Safeguard On Demand
- Safeguard for Privileged Analytics
- Safeguard for Privileged Passwords
- Safeguard for Privileged Sessions
- Safeguard Remote Access
-
Endpoint Privilege Management
- Privilege Manager for Windows
- Privilege Manager for Unix
- Safeguard Authentication Services
- Safeguard for Sudo
- Access Management
- Identity Governance and Administration
- Active Directory Management
- Log Management
- Solutions
- Resources
- Trials
- Support
- Partners
- Communities