An administrator is designing a custom Lightning Record Page for a custom object named Service_Contract__c. The business requires that a specific high-value metrics component on the record page only appears to managers who are viewing contracts with a status of 'Active'. Additionally, the administrator must ensure that this custom page serves as the default layout specifically for the Customer Support application without overriding the record page for other applications across the organization. Which two configuration steps must the administrator complete to satisfy these requirements?
- Set a Component Visibility rule on the high-value metrics component based on the user profile title and the contract Status field.Cevap
- Activate the Lightning Record Page and assign it as the App Default for the Customer Support application.Cevap
- CConfigure Field-Level Security (FLS) on the Service_Contract__c object to restrict access to the high-value metrics component.
- DAssign available picklist values for the contract Status field under the newly created Record Type assignment settings.
- EActivate the page as the Org Default and filter the component by Record Type assignment.
Cevap
The administrator must set component visibility rules based on the user's profile and record fields, and activate the page as the App Default for the Customer Support application.
To meet the requirement of showing a component conditionally based on user role and record state, Lightning App Builder provides component visibility filters that evaluate both record fields and user context. To restrict the custom page layout default to a single application without altering global defaults, the activation must be set to App Default for that targeted Lightning App.
Adım Adım Çözüm
Anahtar Kavram
Lightning App Builder Activation Hierarchy and Dynamic Component Visibility Rules