Visibility and Display Rule Conditions
- 03 Apr 2024
- 5 Minutes To Read
-
Print
-
DarkLight
-
PDF
Visibility and Display Rule Conditions
- Updated On 03 Apr 2024
- 5 Minutes To Read
-
Print
-
DarkLight
-
PDF
Article Summary
Share feedback
Thanks for sharing your feedback!
Overview
Visibility Rules: Used to define where and to whom you want to display the widgets (Self Help, Task List, Pop-ups, Beacons, and Smart Tips). Users can configure Visibility Rules only while creating segments on the Whatfix Dashboard.
Display Rules: Used to define when to show the tooltips based on the conditions met. Also, some conditions let you define where you want to show the tooltips. Users can configure Display Rules while creating Whatfix Content (Flows, Smart Tips, Beacons, User Actions) on the Studio or after creating on the Whatfix Dashboard.
List of Visibility and Display Rule conditions
The following table lists all the conditions used while configuring the Visibility Rules to segment widgets or Display Rules to show the tooltips. These rules determine where and when Whatfix content is to be displayed on your application.
Condition | Description |
| URL Properties | URL Properties enable you to uniquely identify a web page to show Whatfix content and widgets. These properties can be added as a Visibility or Display Rule condition to your Whatfix content and widgets, as required. For more information, see URL Properties. The following are the URL Properties that you can use: URL: If you want to use the entire URL as a Visibility Rule, you can use the URL condition rule. URL Hostname: If you want to uniquely identify a page using the domain name, you can use the condition where the URL Hostname is the first part of any URL. URL Path: If you want to identify your web page using the pathname on the URL, you can use this condition. The website pathname is the part that you see after your domain name but before the parameters or hashes.URL Parameter: If you want to identify your web page using the parameters on the URL, you can use this condition. URL Hash: If you want to identify a page using the hash value of your URL, you can use this condition. Hashes are usually present in Single-page applications made using AngularJS or ReactJS. There are no page refreshes but only Hash changes. |
| Other Elements on Page | If you want to identify a page based on the presence of a particular element (other than the one selected by you) on your web page, you can use this condition. The values passed to this condition are CSS selectors like #ID, class, or JQuery. For more information, see Other Element on a Page condition rule. |
| Window Variable | If you choose to include Advanced Customization, you can identify users based on the value of a specific Javascript global variable. This variable, called a Window Variable, can then be used as a Visibility or Display rule. For more information, see Window Variable condition rule. |
| Attribute Condition | Attribute condition rules enable you to fetch specific information based on roles, departments, geography, accounts, etc. and segment content to show to particular users. Once the attributes are integrated with Whatfix, you can see them in the visibility rules of widgets for content segmentation. For more information, see Attributes condition rules. The following are the Attribute Conditions that you can use: User Attribute: If you need to segment content based on end-user information from your application, User Attributes enable you to fetch this data for use within Whatfix. Enterprise Attribute: If you need to fetch your application information for content segmentation, Enterprise Attributes can enable you to fetch this data for use within Whatfix. |
| Selected Element | The Selected Element rules enable you to add identifiers or properties for unique elements on your web page as a Display Rule. For more information, see Selected Element condition rules. The following are the Selected Elements that you can use: Selected Element Is- CSS Selector/ JQuery: If you want to uniquely identify an element using its distinct ID, you can use this condition. For example, specifying the specific element ID enables you to identify and select the accurate element from a list of similar elements. Selected Element Text: If you want to uniquely identify an element using the displayed text on the element, you can use this condition. Tip: Whatfix recommends that you use the Selected Element Is rule, followed by the Selected Text rule while adding Visibility Rules to any content/widget. Adding CSS Selectors ensures that Whatfix can easily search for the required element and reduce the possibility of displaying content/widgets on the wrong element. |
| User Action | If a User Action is created on an element, it acts as a trigger to display content based on the action your end-users perform. For more information, see User Action condition rule. |
| Launcher | If you want to limit content access to only those who trigger it from a Launcher, using Launcher as a Visibility Rule enables you to do so. For more information, see Launcher as a Visibility rule condition. |
| Tags | If you want to organize information into categories and identify specific pages or roles on your application to display relevant content or widget, you can use a Tag, which is a word, title, or group that enables categorization. Two types of Tags can be used as a Visibility Rule: For more information, see Tags condition rules. |
| Action Element | If you want to ensure that action on a particular element triggers the branched Flow, you can use the Action Element Is or Action Element Text as a display rule. This enables you to add identifiers or properties to ensure that the branched Flow starts on the correct element. For more information, see Action Element conditions as Display rules. |
Your title goes here
Add more than one visibility and display rule condition only if required. Adding extra conditions can sometimes fail to display content. For example, the breaking of Flows.
Supported Operators
Operators in Whatfix refer to the logical expressions that are used to determine whether a Visibility or Display rule condition is met according to a set value. These operators can be used to compare two values, such as "equals", "greater than", "less than", or "not equals", and thus decide whether to show or hide a particular content element based on the condition.
For example, if the Visibility rule is set to "show content only if the user has the 'editor' role", the operator used would be "equals" to compare the user's role with the set value of 'editor'. If the user's role matches the set value, the content will be displayed; otherwise, it will be hidden. For more information, see Supported Operators for Visibility and Display Rules.
Was this article helpful?