How to use special system settings for Limit Scope and Query Criteria parameters in automation rules and Web actions

Summary: In Cayosoft Administrator Hybrid and Active Directory rules have 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 Limit Scope parameter

When configuring a Runbook with multiple automation rules (e.g., Rule 1, Rule 2, and Rule 3), the Limit Scope parameter must be set correctly to ensure consistent object processing.

1. Defining the Scope in Rule 1:

   • In Rule 1, set the Limit Scope parameter to a specific Active Directory container (e.g., OU 1).

2. Applying the Same Scope to Subsequent Rules:

   • If Rule 2 and Rule 3 should use the same OU 1 scope, set their Limit Scope parameter to "Get scope from runbook session setting".

   • This ensures they inherit the scope from Rule 1 instead of defining a separate one.

3. Maintaining Additional Filters:

   • If Rule 1 includes additional filters, the same filters must be applied to Rule 2 and Rule 3.

Without these filters, the subsequent rules might process unintended objects that were not part of Rule 1’s scope.

Key considerations

• Use the Get scope from runbook session setting only when the automation rule runs within a Runbook.

• The first rule in the Runbook must define a specific Active Directory container as its scope.

• The Get scope from runbook session setting is supported only if the first rule in the Runbook is one of the following:

  • Text file | Create AD users rule

  • Import SQL Data | Create AD Users rule

  • Import Oracle Data | Create AD Users rule

Configure Limit Scope and Query Criteria for Web Query

Configuring rule 2 execution after rule 1 or action 1.

To ensure Rule 2 runs immediately after Rule 1 or Action 1, configure the Limit Scope and Query Criteria parameters correctly.

• Setting the Limit Scope Parameter:

  • If Rule 2 is a pre-configured rule (located in HOME > RULES > WebAdmin Rules (Pre-configured)), set Limit Scope to Use Web Query Scope setting.

  • If Rule 2 is a template-based rule, set Limit Scope to Default Domain.

• Configuring the Query Criteria parameter:

  • In Rule 2, set the Query Criteria parameter to ObjectGUID of user created in Web UI.

This ensures Rule 2 processes only the object created in Rule 1 or Action 1, based on its GUID.