Using special system settings for Limit Scope and Query Criteria in automation rules and web actions

Summary: In Cayosoft Administrator Hybrid and Active Directory rules have the Limit Scope and Query Criteria parameters. Both parameters define the search query scope. This article describes how to use special system settings, that can be selected in these parameters.   Applies to: Cayosoft Administrator 5.x and above.

Get scope from runbook session setting in the limit scope parameter

Suppose you have a runbook that includes three automation rules: Rule 1, Rule 2, and Rule 3.

To define the scope for the runbook, you must configure the limit scope parameter in Rule 1 by selecting OU 1 as the target container.

If you want Rule 2 and Rule 3 to use the same OU 1 as their scope, set their limit scope parameter to get scope from runbook session setting.

If Rule 1 has additional filters applied, Rule 2 and Rule 3 must have the same filters. Otherwise, they may process objects outside the intended scope of Rule 1.

Use get scope from runbook session setting in an automation rule only when:

• The rule runs as part of a runbook.

• The first rule in the runbook has a specific Active Directory container defined as its scope.

NOTE: Rules in a runbook support get scope from runbook session setting only if the first rule is one of the following:

• Text file | Create AD Users

• Import SQL Data | Create AD Users

• Import Oracle Data | Create AD Users

Use web query scope in limit scope and ObjectGUID of user created in Web UI in query criteria

Suppose you have Rule 1, Action 1, and Rule 2, and you need Rule 2 to run immediately after Rule 1 or Action 1 is completed.

• If Rule 2 is a pre-configured rule from HOME > RULES > WebAdmin Rules (Pre-configured), select use web query scope setting in the limit scope parameter.
• If Rule 2 is a template rule, use default domain in the limit scope parameter.

In Rule 2, set the query criteria parameter to ObjectGUID of user created in Web UI. This ensures that Rule 2 processes only the object created in Rule 1 or Action 1, based on its GUID.