Configuring a notification for a CRUD activity
You can configure a CRUD activity to subscribe recipients to the notifications of the following events:
-
Activity completed successfully: When configured to notify of this event, the activity causes Active Roles to send a notification email if no significant errors occurred during the run of this activity.
-
Activity encountered an error: When configured to notify of this event, the activity causes Active Roles to send a notification email if any significant errors occurred during the run of this activity.
To configure a notification for a CRUD activity
-
In the process diagram, right-click the name of the activity and click Properties.
-
Go to the Notification tab in the Properties dialog, and configure the notification settings. For more information, see Configuring a Notification activity.
The notification settings specify the event to notify of, and notification recipients. When initiated 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.
Configuring error handling for a CRUD activity
When configuring a CRUD activity, you can use error handling to suppress errors encountered by that activity.
To configure error handling for a CRUD activity
-
In the process diagram, right-click the name of the activity and click Properties.
-
Go to the Error handling tab in the 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 activity encounters an error condition.
Configuring “Run as” options for a CRUD activity
By default, CRUD activities are executed under the user account specified by the “Run as” options 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 CRUD activity
-
In the process diagram, right-click the name of the activity and click Properties.
-
Click “Run as” options at the bottom of the 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.
-
View or change the settings under the Approval enforcement option heading.
The Approval enforcement option settings determine whether to apply approval rules to the operation requested by the activity if the activity is executed under a privileged account, such as the Active Roles service account, an Active Roles Admin account, or the account of the user who is designated as an approver. The following settings are available:
-
Inherit from the workflow options and start conditions: Select this option if you want the activity to use the approval enforcement option selected in the workflow options and start conditions.
-
Use the following option for this activity: Click this option and then select or clear the Enforce approval check box if you want this activity to override the approval enforcement option selected in the workflow options and start conditions.
When selected, the Enforce approval check box causes the approval rules to be applied, submitting the operation for approval regardless of the account under which the activity is executed. Otherwise, the operation requested by the activity bypasses approval rules if the activity is executed under the Active Roles service account, an Active Roles Admin account, or the account of the user who is designated as an approver, so the operation is not submitted for approval.
Configuring additional settings for a CRUD activity
By using additional settings, you can override the default operation reason text, and add request controls to modify the behavior of the activity.
To configure additional settings for a CRUD activity
-
In the process diagram, right-click the name of the activity and click Properties.
-
Click the Additional settings link at the bottom of the Properties dialog.
-
In the Additional Settings dialog, view or change the following options:
-
Use this text instead of the original operation reason text: If the operation requested by the CRUD activity is subject to approval, you can specify the operation reason text to be shown to the approver instead of the reason text specified in the operation request that started the workflow.
-
Select Use this text instead of the original operation reason text check box and type the appropriate reason text to replace the original reason text. Select the Use only if the operation reason is not originally specified check box if you want the activity to use your reason text only if the operation request that started the workflow does not have any reason text specified.
-
Allow the request created by this activity to start a new instance of the workflow containing this activity: When selected, requests created by the activity can start new instances of the workflow containing the activity.
TIP: One Identity recommends leaving this setting clear in most cases, so that you can prevent the recurrent initialization of the activity if the operation requested by the activity within a specific workflow matches the start conditions of that same workflow.
NOTE: Selecting this setting may result in a loop of workflow instances that repeatedly initializes the same activity, eventually resulting in an overflow.
-
Exclude or include request controls from the activity operation request: 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. For information about request controls, see the Active Roles SDK documentation.
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.