...
The four options and outcomes are:•Do
Do Nothing - No changes are made.
...
Move - In the case of user accounts, moves the user object to the OU specified by the RET or as determined through the mapping of OUs to Business Roles and Locations.
...
Delete and Recreate - In the case of user accounts, deletes and recreates the user.
...
Register Event - Raises the event specified.
| View file | ||
|---|---|---|
|
On Transform Action
The four options and outcomes are:•
Do Nothing - No changes are made.
...
Move - In the case of user accounts, moves the user object to the OU specified by the RET or as determined through the mapping of OUs to Business Roles and Locations.
...
Delete and Recreate - In the case of user accounts, deletes and recreates the user.
...
Register Event - Raises the event specified.
| View file | ||
|---|---|---|
|
On Revoke Action
The four options and outcomes are:•
Do Nothing - No changes are made to the resource.
...
De-provision - Deletes the resource.
...
Disable - Disables the resource.
...
Register Event - Raises the event specified.
| View file | ||
|---|---|---|
|
Register Event Option•This
This is an optional setting that allows you to enter the name of a predefined EmpowerID event registration.
...
The RET action will "fire" this event which then triggers the initiation
...
of all workflows that subscribe to the event.
...
The specified event workflows must have an input property of the type Resource named "resource" (case sensitive).
...
The RET process will pass in the resource of the Person's RET (Account, Home Folder, Exchange Mailbox, etc.) that triggered the event for further processing by the custom workflow(s).
...
The custom workflows can be used to implement more advanced processes for deprovisioning or other events.
| View file | ||
|---|---|---|
|
User Interface for Viewing the RET Inbox
AD/LDAP Account Creation Location Logic
When provisioning users automatically via provisioning policies into AD or LDAP directories, EmpowerID must determine into which OU a person’s account should be provisioned. The default logic is to follow the RBAC mapping for the Location portion of a Person’s Business Role and Location to create the account in the Account Store OU mapped to that EmpowerID Location. In some cases, this default logic is not desired and a custom rule should be implemented. For these cases, EmpowerID allows the creation of a plugin in Workflow Studio to handle this unique RET AD/LDAP Account Creation Location logic.
| View file | ||
|---|---|---|
|
| Info |
|---|
Related Docs Topics: |