“Delete” activity is intended to delete a particular object in Active Directory. The activity allows you to specify the object you want the activity to delete. You can select the object when you configure the activity, or you can configure the activity to select the appropriate object at workflow run time. See Activity target for further details.
“Delete” activity also has a number of configuration settings that are common to CRUD activities:
The execution of a CRUD activity results in a request to perform a certain operation on a certain object. For example, an “Update” activity requests Active Roles to make changes to the properties of a certain object, an “Add to group” activity requests Active Roles to add a certain object to particular groups, and so forth. The object on which the operation is requested by a CRUD activity is referred to as the target object of that activity, or simply activity target.
When you configure a CRUD activity, you can use the following options to specify the activity target for that activity:
The following table helps distinguish CRUD activity targets.
Activity |
Activity target |
Update |
The object whose properties are to be changed. An Update activity requests Active Roles to change certain properties of a particular object. That object is referred to as the activity target of the Update activity. |
Add to group |
The object to be added to the groups. An “Add to group” activity requests Active Roles to add a certain object to particular groups. That object is referred to as the activity target of the “Add to group” activity. |
Remove from group |
The object to be removed from the groups. A “Remove from group” activity requests Active Roles to remove a certain object from particular groups. That object is referred to as the activity target of the “Remove from group” activity. |
Move |
The object to be moved. A Move activity requests Active Roles to move a certain object to a particular container in Active Directory. That object is referred to as the activity target of the Move activity. |
Deprovision |
The object to be deprovisioned. A Deprovision activity requests Active Roles to deprovision a certain object. That object is referred to as the activity target of the Deprovision activity. |
Undo deprovision |
The object to be restored. An “Undo deprovision” activity requests Active Roles to restore a certain object that was deprovisioned. That object is referred to as the activity target of the “Undo deprovision” activity. |
Delete |
The object to be deleted. A Delete activity requests Active Roles to delete a certain object. That object is referred to as the activity target of the Delete activity. |
You can configure a CRUD activity to subscribe recipients to the notifications of the following events:
The notification settings specify the event to notify of, and notification recipients. When executed by the workflow, the activity prepares a notification message appropriate to the specified event. Active Roles retains the message prepared by the activity, and sends the message to the specified recipients upon occurrence of that event. The notification settings are similar to the notification settings of a Notification activity (see Notification activity earlier in this document).
When configuring a CRUD activity, you can choose whether to suppress errors encountered by that activity. The following option is available: Continue workflow even if this activity encounters an error. If this option is not selected (default setting), an error encountered by the activity causes Active Roles to terminate the workflow.
If you configure a CRUD activity so that the workflow is allowed to continue in case of an error encountered by that activity, then you can have the workflow take an appropriate compensation action. This could be accomplished by using an If-Else activity with a branch condition that evaluates the “Encountered an error” execution status of the CRUD activity. Add an If-Else activity following the CRUD activity and configure a condition on an If-Else branch to detect the “Encountered an error” execution status of that CRUD activity. Then, configure that If-Else branch to contain the activities you want to perform the compensation action. As a result, once the CRUD activity has encountered an error, the “Encountered an error” branch condition evaluates to TRUE, causing the workflow to execute the activities intended to perform the compensation action.
© 2021 One Identity LLC. ALL RIGHTS RESERVED. Feedback Terms of Use Privacy