When configuring a Search 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), then an error condition encountered by the activity causes Active Roles to terminate the workflow. If you select this option, the workflow continues regardless of whether or not the Search activity or any activity within the Search activity encounters an error condition.
“Run as” options
By default, the Search activity is executed 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 by choosing to run the activity under the service account or the account of the user who caused the workflow to start. The account under which the activity is running determines the access rights of the activity in the directory.
A Search activity has the following additional configuration options:
- Terminate the search activity if the search returns more than <number> objects. Use this option to specify the maximum number of objects the activity is allowed to return when performing a search. If you want to receive all the objects that match the search conditions, you can disable this option.
- 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. 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. You can configure the activity to add certain controls to its operation requests (include request controls) or to ensure that certain controls never occur in the activity operation requests (exclude request controls). For information about Active Roles request controls, see the Active Roles SDK documentation.
Stop Search activity
You can use a Stop Search activity within a Search activity to stop the search being performed by the Search activity. Basically, a Stop Search activity is intended to be used within an If-Else activity nested into a Search activity, in order to stop the search if certain conditions occur. In this scenario, the If-Else activity analyzes data returned by the search, and executes the If-Else branch containing the Stop Search activity if the data returned by the search meets the conditions of that If-Else branch.