Element Precision Rules for Launchers on Studio
- 06 Aug 2025
- 3 Minuten zu lesen
- Drucken
- DunkelLicht
- pdf
Element Precision Rules for Launchers on Studio
- Aktualisiert am 06 Aug 2025
- 3 Minuten zu lesen
- Drucken
- DunkelLicht
- pdf
The content is currently unavailable in German. You are viewing the default English version.
Artikel-Zusammenfassung
Fanden Sie diese Zusammenfassung hilfreich?
Vielen Dank für Ihr Feedback
Note:
Display Rules are now available as Visibility Rules and Element Precision Rules on Studio.
Currently, this update is in the Beta stage and is available only for Launchers and Beacons. It will be available for other content types, such as Flows and Smart Tips in upcoming phases. To enable the feature, contact support@whatfix.com.
What are Element Precision Rules?
Element Precision Rules help ensure that a Launcher appears on the correct UI component, preventing misalignment or flickering. These rules provide precise control over positioning, ensuring the Launcher consistently appears in the intended location.
Types of Element Precision Rules
Rule | Description | Example |
Using CSS selector | Identifies an element using a CSS selector. It is useful when elements have unique identifiers or specific class names. CSS selectors help in precisely targeting elements based on attributes such as class, ID, or hierarchy. | Display the Launcher only if an element with .help-button exists. |
Using jQuery selector | Identifies an element using a jQuery selector, which enables more advanced element selection, including filters and conditions. It is useful when you need to select elements dynamically based on complex conditions. | Display the Launcher when an element matching |
Using Element Text | Identifies an element based on the visible text it contains. It is useful when targeting buttons, labels, or other text-based elements. | Display the Launcher if the button text is Login. |
Note:
Adding CSS Selectors ensures that Whatfix can easily find the required element and reduce the possibility of displaying content or widgets on the wrong element.
Use Cases
Display Launchers on options inside a dropdown
Consider that you want to show a Launcher on options inside a dropdown in your application. These options have a unique identifier, ID (CSS Selector), used to identify the element. Use the Using CSS selector rule and specify the CSS selector value to ensure the Launcher appears correctly on the desired element.
On Whatfix Studio, click Element Precision.
.png?sv=2022-11-02&spr=https&st=2025-10-17T07%3A40%3A42Z&se=2025-10-17T07%3A50%3A42Z&sr=c&sp=r&sig=NdF2uYSXr7lTisU7%2FAI3MYC7DTMgba2sZZVRxCYOcnk%3D)
From the How would you like to identify the element? dropdown, select Using CSS selector.
.
Enter the selector Value.
.png?sv=2022-11-02&spr=https&st=2025-10-17T07%3A40%3A42Z&se=2025-10-17T07%3A50%3A42Z&sr=c&sp=r&sig=NdF2uYSXr7lTisU7%2FAI3MYC7DTMgba2sZZVRxCYOcnk%3D)
Complete creating the Whatfix content.
Display Launchers when there are no unique identifiers for the elements
Consider that you want to display a Launcher on a button in your application. The button has no unique identifiers such as IDs or specific classes. The only distinguishing factor is the button text. In such cases, use the Using Element Text rule to ensure that the Launcher appears correctly on the intended button.
Note:
Whatfix recommends that you use the Using CSS selector rule, followed by the Using Element Text rule while adding Element Precision Rules to Launchers.
On Whatfix Studio, click Element Precision.
From the How would you like to identify the element? dropdown, select Using CSS selector.
In the Value field, enter the CSS selector for the button.
Click Add condition.
From the How would you like to identify the element? dropdown, select Using Element Text.
.png?sv=2022-11-02&spr=https&st=2025-10-17T07%3A40%3A42Z&se=2025-10-17T07%3A50%3A42Z&sr=c&sp=r&sig=NdF2uYSXr7lTisU7%2FAI3MYC7DTMgba2sZZVRxCYOcnk%3D)
Select Contains from the dropdown.
Enter the button Value.
Complete creating the Whatfix content.
Frequently Asked Questions (FAQs)
How are rules at the Widget level different from rules at the individual Launcher level?
Widget-level rules are configured using the Dashboard and apply to all Launchers in a collection. Every Launcher linked to the Widget follows the same conditions.
Individual Launcher rules are configured using Studio and apply only to a specific Launcher. It provides more control over when and where a single Launcher appears without affecting others.
What happens if there is a conflict between Studio rules and Dashboard rules?
If there is a conflict between the Visibility rules set for a single Launcher and the rules set for the Widget (which includes multiple Launchers), Whatfix follows a prioritization criteria. First, it checks the rules at the Widget level. Then, it looks at the rules for each individual Launcher.
For more information on Prioritization, see Understand prioritization criteria for Launchers.
War dieser Artikel hilfreich?