Application Validation (AV) mode

Application Validation (AV) mode is used during rule validation to determine which rules are valid to reference at design time without having to use ruleset prerequisites. Using AV mode is recommended over the alternative Ruleset Validation (RV) mode due to the significant performance advantages of AV mode.

Versions

Within a given ruleset name, you cannot call rules in a higher ruleset version. For example, rules in App:01-01-01 cannot reference rules in App:01-01-03 (at design time). For versions across different ruleset names, standard AV mode logic is applied.

Branches

A branched ruleset using AV mode can access all rulesets in an application, including other rulesets in the same branch, as well as any other branches included in the same application definition. Therefore, all branches within a given application definition can refer to each other.

Rules in non-branched rulesets cannot reference rules in any branch.

A branched ruleset is initially set to the same validation mode as the non-branched ruleset. However, if the validation mode of the branched and non-branched rulesets do not match, a warning displays, since there is the potential for a conflict upon merge. Accordingly, best practice recommends using the same validation mode for both the branched and non-branched ruleset instances for the same ruleset name.

Update the validation mode by selecting the corresponding radio button under the Versions tab on the rule form.

Mobile and local rulesets

Mobile and local rulesets have their own ruleset validation mode. If set to AV mode, a mobile or local ruleset can refer to all rules in the application (or built-ons). An application ruleset cannot explicitly refer to local or mobile rulesets unless they are added to the application.

Note: Adding local or mobile rulesets to the base application ruleset is not recommended since non-local or non-mobile rulesets could call into the local/mobile rulesets.

Production rulesets

Production rulesets get placed on top of the stack and can reference the application rulesets, although application rules cannot directly reference a production ruleset. A non-production version of the rule must exist for validation.

Component/shared ruleset

These ruleset types are in the process of possible being deprecated as such we currently will not allow them to be set to AV mode.

Related Topics IconRelated terms