Objects and Applications19% of the exam
Dynamic Forms, Dynamic Actions and visibility rules
How component, tab, field and action visibility filters work on Lightning pages, what changes when a record page moves to Dynamic Forms (field sections, create and edit windows, mobile, cross-object fields), and how Dynamic Actions put filtered actions on desktop and mobile.
Given a scenario, determine the appropriate solution to enhance or extend the UI/UX with applications (App Manager, Lightning App Builder, Dynamic Forms, standard Lightning page components, Console, and Lightning page analyze button).
~8 min read · 9 practice questions ·
What the exam expects
- Build visibility filters for components, tabs, fields and actions, and know which contexts each page type offers.
- Work around the visibility filter limits (five spans, single values, supported field types).
- Migrate a record page to Dynamic Forms and predict its effect on create, edit and clone, hidden fields and mobile users.
- Add cross-object fields and page-only read-only or required settings without changing field-level security.
- Enable Dynamic Actions on a record page and on mobile for standard and custom objects.
Key terms:
- Visibility filter: a condition that hides a component until its filter logic is met.
- Dynamic Forms: Field and Field Section components that replace the page layout's Record Detail block.
- Record Detail - Mobile: the component that shows page layout fields to mobile users on a Dynamic Forms page.
- Dynamic Actions: actions assigned and filtered in the Lightning App Builder instead of the page layout.
Key facts
Filter span limit
- Detail
- Field values can't span more than five fields
App and Home page filters
- Detail
- User, User Permission, Device and similar contexts; no record fields
Tabs component
- Detail
- Up to 100 tabs; tabs can have visibility rules
Field vs section rules
- Detail
- Fields dynamic in edit; sections only after save
Edited value in hidden field
- Detail
- Not saved
Hidden tab
- Detail
- Its field sections hidden in Create and Edit; blank if all are there
Create, edit, clone fields
- Detail
- From the page's field sections, not the layout
Mobile after enabling
- Detail
- Remove Record Detail - Mobile from existing pages
Dynamic actions on mobile
- Detail
- Default for custom objects; standard objects need Dynamic Actions on Mobile
Action filter values
- Detail
- One value per filter
Sources for this section (6)
- Visibility Ruleshelp.salesforce.com (opens in a new tab)
- Page Componentshelp.salesforce.com (opens in a new tab)
- DF Considerationshelp.salesforce.com (opens in a new tab)
- Dynamic Formshelp.salesforce.com (opens in a new tab)
- DF on Mobilehelp.salesforce.com (opens in a new tab)
- Dynamic Actionshelp.salesforce.com (opens in a new tab)
- Why does a Home page offer no record field filters?
- When is a visibility rule on a Field Section evaluated?
- What happens to the Create and Edit windows when a visibility rule hides a tab that holds all of a page's field sections?
- What must you remove from an existing Dynamic Forms page after enabling Dynamic Forms on Mobile?
The questions are free to read. Answers with their sources and self-grading are included with the pack.
Keep reading with the Platform Administrator II pack
- Core concepts
- Exam traps
- Worked scenario
The pack includes:
- All 29 lessons of the Platform Administrator II guide, with reading progress
- Interactive decision walks and step-by-step sequence steppers
- Inline practice questions and one-click topic practice (9 questions for this lesson)
- An official source cited for every claim
- An AI tutor that answers from the guide
- Unlimited timed practice exams