Configuring error handling for a Search activity
When configuring a Search activity, you can configure error handling to suppress errors encountered by that Search activity and all activities included in that Search activity.
To configure error handling for a Search activity
-
In the process diagram, right-click the name of the Search activity and click Properties.
-
Go to the Error handling tab in the “Search” Activity Properties dialog, and select or clear the Continue workflow even if this activity encounters an error check box on that tab.
If the Continue workflow even if this activity encounters an error check box is not selected (default setting), then an error condition encountered by the activity causes Active Roles to stop the workflow. If you select this check box, the workflow continues regardless of whether or not the Search activity or any activity within the Search activity encounters an error condition.
Configuring “Run as” options for a Search activity
By default, the Search activity is started under the user account specified by the “Run as” setting in the workflow options and start conditions. This could be the service account of the Active Roles Administration Service or the account of the user who caused the workflow to start. You can configure the activity to override the default “Run as” setting.
To configure “Run as” options for a Search activity
-
In the process diagram, right-click the name of the Search activity and click Properties.
-
Click the “Run as” options hyperlink at the bottom of the “Search” Activity Properties dialog.
-
To override the default “Run as” setting for this activity, select the Run this activity under check box, and then choose the account under which you want the activity to run:
-
Click The service account of Active Roles if you want this activity to run under the service account of the Active Roles Administration Service.
-
Click The account of the user who started the workflow if you want this activity to run under the account of the user who caused the workflow to start. Depending on the type of the workflow, this is either the user who requested the operation that started the workflow or the user who started the workflow on demand.
The account under which the activity is running determines the access rights of the activity in the directory.
Configuring additional settings for a Search activity
By using additional settings, you can configure a Search activity to stop the search if the number of the objects that meet the search conditions exceeds a certain threshold. It is also possible to modify behavior of a Search activity using so-called request controls to pass additional information to Active Roles on how to process operation requests created by that activity.
To configure additional settings for a Search activity
-
In the process diagram, right-click the name of the Search activity and click Properties.
-
Click the Additional settings hyperlink at the bottom of the “Search” Activity Properties dialog.
-
To have the Search activity stop the search if the number of the objects found by the search exceeds a certain threshold, select the Terminate the search activity if the search returns more than check box, and specify the maximum number of objects the activity is allowed to return when performing a search.
-
Add, change, or remove request controls in the Include or exclude these controls from the activity operation requests list.
To add or change a control, click Add or Change, and then, in the dialog that opens, specify the name and, if applicable, the value of the control. If you want the activity to add the control to the requests, click Include this control in the activity operation requests. If you want to ensure that the control never occurs in the requests created by this activity, click Exclude this control from the activity operation requests.
Request controls are certain pieces of data in an operation request that can be used to pass additional information to Active Roles on how to process the request. Request controls are optional. If no request controls are added to a request, then Active Roles determines how to process the request based solely on the type of the request. For more information about request controls, see the Active Roles SDK documentation.
Configuring CRUD activities
Active Roles offers a number of workflow activities, collectively referred to as CRUD activities, intended to create new objects, and modify or delete existing objects in Active Directory. The CRUD abbreviation designates the key operations that can be performed by using these activities: Create, Read, Update, Delete.
-
Create activity: Creates an object, such as a user, group, or computer, in Active Directory.
-
Update activity: Changes properties of an object, such as a user, group, or computer, in Active Directory.
-
Add to group activity: Adds an object, such as a user, group, or computer, to specified groups in Active Directory.
-
Remove from group activity: Removes an object, such as a user, group, or computer, from specified groups in Active Directory.
-
Move activity: Moves an object, such as a user, group, or computer, to a specified container in Active Directory.
-
Deprovision activity: Deprovisions a user or group, by applying the Active Roles deprovisioning policy.
-
Undo deprovision activity: Restores a user or group that was deprovisioned by using Active Roles.
-
Delete activity: Deletes an object, such as a user, group, or computer, in Active Directory.
The following topics in this section provide the steps for configuring the settings that are common to CRUD activities: