A Salesforce administrator is reviewing Lightning App Builder page activations and assignment options across Home pages and Record pages for a multi-department organization. Which two statements correctly describe the behavior and assignment capabilities of Lightning pages? (Select 2 answers)
- A custom Lightning Home page can be assigned as the Org Default or to specific combinations of Apps and Profiles, but it cannot be assigned by Record Type.Cevap
- BSetting component visibility filters on a Lightning Record Page automatically restricts field-level security permissions for users across reports and API calls.
- Activating a Lightning Record Page using the App, Record Type, and Profile combination overrides both Org Default and App Default page assignments for those specific contexts.Cevap
- DA custom Home page can be assigned directly to specific Record Types to present dynamic component layouts when users view record details.
- ELightning Record Page activations can be assigned directly to individual Permission Set Groups instead of Profiles.
Cevap
The correct statements are that custom Lightning Home pages can be assigned as Org Default or to App and Profile combinations (but not by Record Type), and that activating a Record Page by App, Record Type, and Profile overrides Org Default and App Default assignments.
Lightning Home pages support Org Default and App/Profile level assignments, but not Record Type assignments because they are not record-bound. Additionally, in Lightning Record Page activation hierarchy, assigning a page by App, Record Type, and Profile provides the highest specificity, overriding both App Default and Org Default assignments.
Adım Adım Çözüm
Anahtar Kavram
Lightning App Builder Page Activation Precedence and Scope