Overview of Instant Validation for the new Visibility Rules in Studio

Note:

• Instant Validation can be enabled from the Whatfix Guidance Dashboard. To enable the feature, see Enable Instant Validation for new Visibility Rules on Studio.

• Instant Validation is only supported for the new Visibility Rules in Studio. For more information on the new Visibility Rules, see Understand the new Visibility Rules for Content.

Overview

Instant Validation provides content authors with immediate feedback on new Visibility Rules while creating content and widgets in Studio. While adding the rules, Visibility Rules are evaluated directly within the context of the current application, showing whether each rule is valid or invalid.

This real-time validation helps authors understand how their rules behave in the live application environment, reducing trial-and-error cycles and ensuring that content appears as intended.

Benefits of Instant Validation for the new Visibility Rules

Instant Validation enables authors to:

• View the real-time status of applied Visibility Rules, showing whether each rule is valid or invalid during content creation.

• Save time by eliminating repeated save-and-preview cycles for Visibility Rules.

• Troubleshoot issues efficiently by pinpointing failing conditions directly within Studio.

• Gain confidence in content targeting, knowing that evaluation happens within the context of the current application.

How does Instant Validation work in Studio?

When configuring the new Visibility Rules in Studio, each rule is evaluated instantly as soon it is added. The evaluation occurs within the context of the current application, and Whatfix immediately displays whether a rule is valid or invalid on the current page. This eliminates the need for repeated save and preview cycles to verify rule behavior.

Evaluation occurs at two levels:

• Individual rule level: Each rule in a step displays whether it is valid or invalid.
  
  

• Group-level evaluation (Where, When, Who): Each set of conditions provides an overall status, helping content authors identify which group of rules causes a failure.
  

Example:

Consider you are configuring a Beacon that should appear only on the Sales Dashboard page. You configure the following rule:

Where Rule: URL Contains - salesdashboard

Here’s how the rule is validated:

Scenario 1: You are on the Sales Dashboard page.

The rule matches the current application context. Whatfix displays Applied condition is valid on this page message, and the Beacon displays as intended.

Scenario 2: You navigate to a different page, such as /reports.

The rule does not match the current application context. Whatfix displays Applied condition is invalid on this page message, and the Beacon does not display on the page.

Note:

• Deterministic rules, such as URL, Domain, URL path, and more, show a Valid or Invalid evaluation instantly during content creation because they can be fully evaluated within the current application context.

• Non-deterministic rules, such as User Actions or Events related to Whatfix content, are validated but require actual user interaction or completion of specific actions to fully evaluate. For example, a Beacon is configured to appear only after a user clicks a Submit button, its evaluation depends on the user performing that action. Until the action occurs, the rule cannot be determined as valid or invalid, even though it is correctly configured.