Component Visibility

Overview

Instead of always showing all components, you can define rules that determine when a component is visible. Show a section only when a checkbox is checked, hide a chart on mobile, or display a form only after the user picks an option.

Visibility rules work on Lightning Pages and Experience Cloud sites (both Aura and LWR). The conditions you define in the Component Builder apply at runtime regardless of where the Dynamic Component is deployed.

Info

If you're building on an Experience Cloud site and find that Salesforce Audiences are too broad for your needs, visibility rules give you field-level and interaction-level control over what appears on the page. See Experience Sites Integration for setup details.

---

How Dynamic Visibility Works

Every Avonni component has a Set Component Visible property (in the Properties Panel) that controls its display. You can set it to:

• Always Visible (true): The default; the component is always shown.

• Always Hidden (false): The component is never shown.

• Conditional Visibility: The component is shown only when specific conditions are met.

---

Setting Up Conditional Visibility

To make a component's visibility conditional:

1. Select the Component: Click on the component in the canvas whose visibility you want to control.

2. Find the "Set Component Visibility" Property: In the Properties Panel (right side), locate the Visible property.

3. Click the Resource Selector: Click the icon next to the Visible property (usually a variable/tag icon). This opens the resource selection menu. Do not simply type true or false unless you want the component to be always visible or always hidden.

4. Choose your condition:

• Component Attribute: Base visibility on the state or value of another component (e.g., show Component B only if @MyCheckbox.checked is true).

• Variable: Use a Boolean Variable resource you created. The component shows when the variable is true.

• Formula: Use a Formula resource that evaluates to true (visible) or false (hidden). Allows complex logic.

• Global Variable: Use system-provided information.

  • New: For Device Type: Select $Component, then choose the FormFactor attribute. This holds the current device type as text: 'Desktop', 'Tablet', or 'Phone'.

---

Examples

Conditionally Displaying a Calendar

Let's create an example in which an Avonni Calendar component is visible only when the user selects the "Calendar" option from an Avonni Button Menu.

1

Add a Button Menu

• Drag an Avonni Button Menu component onto the canvas.

• In its properties, configure the Items:

  • Add an item with Label: Table, Value: table

  • Add an item with Label: Calendar, Value: calendar

• Give the Button Menu a descriptive API Name (e.g., ViewModeMenu).

2

Add the Calendar

Drag an Avonni Calendar component onto the canvas

3

Set the Calendar's Visibility

• Select the Calendar component.

• In the Properties Panel, find the Visible property.

• Click the resource selector icon.

• Select Component Attribute.

• Select your Button Menu component (e.g., ViewModeMenu).

• Choose the value attribute.

• Set the operator to equals

• Set the value to calendar.

How It Works

The Calendar's Visible property is now directly linked to the value of the ViewModeMenu Button Menu. When the user selects "Calendar" in the Button Menu, the value becomes 'calendar', the condition evaluates to true, and the Calendar component is displayed. If any other option is selected, the condition is false, and the Calendar is not loaded.

Device-Specific Layout

Let's show a detailed Data Table on desktops/tablets, but a simpler List component on phones.

1

Add Data Table

Add your Data Table component (e.g., MyDataTable).

2

Set Data Table Visibility

• Select MyDataTable.

• In the Visible property, set the condition: Global Variable $Component.FormFactor not equal to 'Phone'.

3

Add List Component

Add your List component (e.g., MyList) designed for mobile viewing.

4

Set List Visibility

• Select MyList.

• In the Visible property, set the condition: Global Variable $Component.FormFactor equals 'Phone'.

Result: Users on desktops or tablets will see the Data Table, while users viewing on a phone will see the List component, providing an optimized view for each device form factor.

---

Common Use Cases

• Conditional Forms: Show/hide form fields based on previous selections.

• Personalized Dashboards: Display different components based on user role or profile.

• Progressive Disclosure: Gradually reveal information as the user interacts.

• Error Messages: Show error messages only when an error occurs.

• Loading Indicators: Show a loading indicator while data is being fetched, then hide it and show the data component.

• Creating Responsive Layouts that adapt to Desktop, Tablet, and Phone screens

• Experience Cloud sites: Control component visibility based on record data or user interactions when Salesforce Audiences don't offer enough granularity. For example, show a Flow only to users whose Account has a specific Type value, or hide a section until the user selects a tab. This works on both Aura and LWR sites.

---

Tips

• Start Simple: Begin with simple conditions and gradually increase complexity.

• Test Thoroughly: Test your visibility conditions with different data and user interactions.

• Use Formulas Carefully: While powerful, complex formulas can be more complicated to maintain.

• Use Boolean Variables: Create boolean variables to make it more readable.

---

In Summary

Link the Visible property to data, component attributes, formulas, or $Component.FormFactor to control when components appear. This works on Lightning Pages and Experience Cloud sites alike. In Experience Cloud, visibility rules provide the fine-grained, condition-based control that Salesforce Audiences doesn't cover.