Lightning App Builder Considerations
Keep these considerations in mind when working with Lightning pages and Lightning apps in the Lightning App Builder.
Required Editions
| Lightning App Builder available in: both Salesforce Classic and Lightning Experience |
| Lightning Home and utility bar pages available in: Lightning Experience |
| Lightning app and record pages available in: both the Salesforce mobile app and Lightning Experience |
| Email application pane pages available in: both Salesforce Classic and Lightning Experience |
Available in: Group, Essentials, Professional, Enterprise, Performance, Unlimited, and Developer Editions |
Tips
- To reduce user confusion, give each tab and Accordion section a unique label.
- If you’re curious about a component on the canvas, click it to see more information in the properties pane.
- Put the Activities component in a place where no other components are beneath it.
- When editing navigation items in a Lightning app, consider how many items you include. Users can’t remove the items that you include in the navigation bar, and they can’t personalize the navigation bar when it contains more than 50 items. For example, if you include 32 items in an app’s navigation bar, users can add 18 more personal items. Users can personalize the navigation to add or move items, but users can’t remove or rename the items that you add.
- We don't recommend putting record fields into a narrow region on the right-hand side of a page. On pages that support Agentforce, the Einstein panel covers up content on the right-hand side of the page. If record fields are behind the Einstein panel, users who use Einstein for field generation can’t see the updated field information.
General
- The Lightning App Builder supports the same browsers as Lightning Experience and isn’t supported on mobile browsers. The minimum recommended resolution for the Lightning App Builder is 1280x1024.
- When viewing a page in the Lightning App Builder:
- The palette shows only the components that are available for the devices supported by the page template. For example, if you’re working on a page whose template supports only desktop, the component palette contains components that support desktop, whether they support desktop only or both desktop and phone.
- The palette shows only the components that are available for the object tied to that page. For person account pages, some of the components that you see apply only to business accounts.
- The form factor switcher shows only the devices that the page template supports. If the canvas view is switched to a form factor that a component on the page doesn’t support, that component displays as a placeholder with a warning.
- User interface controls that appear inside components on the canvas, such as buttons or links, are there to help you design and configure the component, but they aren't functional. For example, the quick action buttons inside a Highlights Panel component aren't clickable. Screen readers and assistive technologies announce the roles of these interface elements, but they don't function at design time.
- When a component is viewed on a device that the component doesn’t support, it’s dropped from the page.
- You can create and edit a record page even if you don’t have permission to access the object that the page is associated with. You can add, remove, delete, and reconfigure components on the page, but you don’t see any of the content for the components that are based on that object.
- In Salesforce Classic, Lightning page tabs don’t display on the All Tabs page when you
click
. Lightning page tabs also don’t appear in the Available Tabs list when you
customize the tabs for your apps. - On Lightning Experience record pages, a Record Detail component that contains more than four external lookup fields breaks the page at runtime.
- When you click a compound address field from a Record Detail component, it opens in Google Maps™ with just the address populated. When you click a compound address field from a Dynamic Forms-enabled page, it opens in Google Maps showing not only the address, but also the latitude and longitude values.
- When you enter a custom label for a tab, that label text is shown in title case at runtime. The only exception is for Location object pages. A custom tab label that appears on a Location object page isn't changed to title case. It appears to users exactly as it was entered.
- When you select the Insert Component button on the canvas (
), focus shifts to the component panel. At the same time, the "Select a component"
element is activated. After you select a component to insert, the "Select a component"
element disappears, and focus shifts to the inserted component. This is the intended
behavior.The "Select a component" element is a placeholder element, not a button. It's not focusable, and can't be tabbed to or selected.
Page Templates
- The Three Regions template and the pinned region templates are designed with Lightning console apps in mind. They feature a main region and two sidebars with fixed proportional widths. The main region is 50%, and the side region widths are each 25%. Three-region templates require more screen width to display correctly. Three-region templates can display incorrectly on certain devices or monitors with low resolutions.
- When switching page templates, if a region in the template that you’re switching to has more than 25 components mapped to it, all components after the 25th are dropped from the page. You can proceed with the template swap, but you must manually add the dropped components from the palette and reconfigure their properties.
- The console pinned region templates let users view and work with records while
navigating subtabs in console apps. These templates also work in apps with standard
navigation. However, we recommend that you use a non-pinned region template in standard
apps, because those apps don’t benefit from a pinned region. When working with pinned
region templates, keep these considerations in mind.
- The templates are available only for record pages.
- Pinned regions don’t support theming. For example, if you use custom theming to brand your app with the color green, the pinned region doesn’t apply the green color.
Page Activation and Assignment
- If a device isn’t on the options list when you try to assign a Lightning page as the org default, the page template doesn’t support it.
- You can see which record pages are activated for which Lightning app and which form factor in the Lightning Record Pages related list in Object Manager.
- If you no longer want a page to be an app or org default, redo the activation process for the page, and select the option to remove it as the default.
- If you activate a page and then return to make changes, you don’t have to activate it again. Clicking Save after you make your edits pushes the changes to your users.
- If you no longer want a page assigned to a particular form factor, redo the activation process, and select the option to remove it.
- If you activate a page for only one form factor, you can add support for another form factor later as long as the page’s template supports it.
- Changes that you make to Lightning record page assignments aren’t immediately reflected in the Salesforce mobile app. To see a newly assigned record page, close and restart the Salesforce mobile app.
- If there are no custom app-level page assignments set for the Service Console or Lightning Sales Console apps, users viewing those apps in the Salesforce mobile app see the org default record page assigned to the object instead of the system app default record page.
- If you assign a custom record page as the org-wide default for an object, it becomes the default page for that object across all your Lightning apps. It also appears as the default record page for that object in Classic apps when you open them in Lightning Experience.
- Accounts and person accounts have different standard default pages to begin with. However, when you create a Lightning page for accounts and assign it as the default for an org or an app, that page becomes the org or app default for business accounts and person accounts. To display a custom record page for person accounts, create a custom account record page, then assign it to the person account record type.
- An activated Lightning record page takes precedence over the Lightning Experience Override setting for the View action on the object.
Pages and Packages
- If you package a Lightning page that references protected labels, then if a subscriber org clones that page, the protected labels cause the components that use them on the cloned page to be invalid.
- A Lightning page installed from a managed package appears in the Lightning pages list with a Clone option rather than Edit or Delete. The Edit and Delete buttons are also replaced with Clone on the installed page’s detail page.
- You must have the Manage Prompt Templates permission to successfully package Lightning pages that reference prompt templates. Without this permission, package creation succeeds, but the prompt template isn’t included in the package.
Did this article solve your issue?
Let us know so we can improve!
