User Interface17% of the exam
Lightning apps, compact layouts, Dynamic Forms and Path
Which declarative tool shapes each part of the Lightning Experience UI: Lightning apps and the utility bar, compact layouts in the highlights panel, Dynamic Forms fields and sections, Path, and how Classic page layout elements carry over.
Describe the user interface customization options.
~8 min read · 11 practice questions ·
What the exam expects
- Configure a Lightning app's branding, navigation, profiles and utility bar in App Manager, and upgrade Classic apps.
- Choose the compact layout, not the page layout, to change the record header, and assign it per record type.
- Use Dynamic Forms visibility rules, knowing which objects support it and that visibility is not security.
- Set up Path with key fields and guidance for each record type.
- Predict how each Classic page layout element renders, or fails to render, in Lightning Experience.
Key terms: Lightning app (a branded bundle of navigation items); utility bar (a fixed footer of tools in one app); compact layout (the highlights panel's key fields); Dynamic Forms (fields and sections as separate page components); Path (a step bar built on a picklist).
Key facts
Lightning Experience highlights panel
- Detail
- Up to the first seven compact layout fields
Compact layout assignment
- Detail
- One per record type; never per profile or user
Unsupported compact layout fields
- Detail
- Text area, long text area, rich text area, multi-select picklist
Utility bar from the App Builder or wizard
- Detail
- Assigned to only one Lightning app; no Visualforce
Classic app navigation
- Detail
- Not personalizable until upgraded in App Manager
Dynamic Forms objects
- Detail
- Most LWC-enabled objects; not Products, Events or Tasks
Create, edit and clone fields on Dynamic Forms pages
- Detail
- Come from the Lightning page, not the page layout
Field Section visibility rules
- Detail
- Evaluated only after the record is saved
Path per step
- Detail
- Up to five key fields and 1,000 characters of guidance
Unsupported layout elements
- Detail
- Expanded lookups, mobile cards, s-controls, Edit Page section header visibility, tags
Sources for this section (8)
- Compact Layoutshelp.salesforce.com (opens in a new tab)
- Compact Layout Considerationshelp.salesforce.com (opens in a new tab)
- Utility Barhelp.salesforce.com (opens in a new tab)
- Adjust Your Existing Customizationshelp.salesforce.com (opens in a new tab)
- Dynamic Formshelp.salesforce.com (opens in a new tab)
- Dynamic Forms Considerationshelp.salesforce.com (opens in a new tab)
- Create a Pathhelp.salesforce.com (opens in a new tab)
- Page Layout Elements in Lightning Experiencehelp.salesforce.com (opens in a new tab)
- Why does a field that is tenth on the compact layout show on a phone but not on desktop?
- When does a Field Section visibility rule re-evaluate after a user changes a field?
- Why does a field added only to the page layout not appear in New on a Dynamic Forms page?
- What must you do before users can personalize the navigation bar of a Classic app?
The questions are free to read. Answers with their sources and self-grading are included with the pack.
Keep reading with the Platform App Builder pack
- Core concepts
- Exam traps
- Worked scenario
The pack includes:
- All 26 lessons of the Platform App Builder guide, with reading progress
- Interactive decision walks and step-by-step sequence steppers
- Inline practice questions and one-click topic practice (11 questions for this lesson)
- An official source cited for every claim
- An AI tutor that answers from the guide
- Unlimited timed practice exams