Examkin

Question

Difficulty: MediumDynamic Forms and Dynamic Actions

A Salesforce Administrator is configuring a custom object record page in Lightning App Builder. The finance team requires that a specific field section containing sensitive billing metrics is displayed on the page only when the record status is set to 'Completed' and the viewing user holds the 'Finance Director' role. Furthermore, this section must be hidden entirely when viewed on mobile devices. Which configuration approach should the administrator use to satisfy these requirements?

  1. Upgrade the page to Dynamic Forms and configure component visibility filters on the Field Section component based on Record Status, User Role, and Device.Answer
  2. B
    Restrict Field-Level Security for the billing fields to the Finance Director profile so that the standard page layout automatically hides the section on mobile and non-completed records.
  3. C
    Create separate page layouts for each combination of record status and user role, then assign mobile page layout overrides in Object Manager.
  4. D
    Configure conditional visibility rules directly within the standard Page Layout editor properties under Object Manager.

Answer

The administrator should upgrade the Lightning record page to Dynamic Forms and apply component visibility filters on the Field Section component using Record Status, User Role, and Device as filter criteria.
Upgrading the record page to Dynamic Forms in Lightning App Builder allows field sections to be placed as modular components. Administrators can configure visibility filters directly on the Field Section component using filter logic that checks record field values (Status = Completed), user profile/role details (Role = Finance Director), and device environment (Device = Desktop).

Step-by-Step Solution

1
Identify the Lightning App Builder features required for section-level control.
Dynamic Forms enables field sections to act as individual components on a Lightning record page.
Standard page layouts render record details as a single monolithic block without conditional component visibility.
2
Migrate the page layout details to Dynamic Forms using the page upgrade wizard in Lightning App Builder.
Fields and field sections become customizable Lightning components on the canvas.
Upgrading converts fields into independent elements that can accept visibility rules.
3
Add visibility filters to the specific Field Section component.
Filter set: Record > Status equals 'Completed', User > Role > Name equals 'Finance Director', and Device equals 'Desktop'.
Component visibility rules seamlessly evaluate record data, viewing user attributes, and device context simultaneously.

Key Concept

Dynamic Forms Component Visibility Rules
Rate this question

Topics

Dynamic Forms and Dynamic Actions

More questions from this topic