Page layouts, record types, and Dynamic Forms

Record types let one object serve different business processes with different picklist values and layouts. Page layouts decide which fields, buttons, and related lists appear. Dynamic Forms move fields onto the Lightning record page so they can show or hide based on rules.

Page layouts

• What a layout controls: Field placement and sections, which fields are required or read-only on the layout, buttons and quick actions, and related lists.
• Layout assignment: Assigned by profile and record type. Two users with different profiles can see the same record with different layouts.
• Layout vs field-level security: A layout can make a field read-only or required on that screen, but field-level security is the real control. A field hidden by FLS can't be shown by a layout.
• Compact layouts: Choose the key fields in the highlights panel at the top of a record page and in the Salesforce mobile app's record header.

Record types and business processes

• Record types: Offer different picklist values and page layouts for the same object, such as separate support and billing case types.
• Assignment: Profiles and permission sets grant access to record types. Each profile has a default record type for new records.
• Business processes: Control the main status picklist values per record type: sales processes for Opportunity stages, support processes for Case status, and lead processes for Lead status.
• A sales process must exist before you can create an opportunity record type that uses it.

Dynamic Forms and Dynamic Actions

• Dynamic Forms: Place fields and field sections directly on a Lightning record page and set visibility rules, such as showing a Discount Reason field only when Discount is filled in.
• Dynamic Actions: Show buttons and actions on the record page based on rules, such as the user's profile or a field value.
• Why use them: One Lightning page can replace several page layouts, and users see only what is relevant to the record in front of them.

Actions and buttons

• Object-specific quick actions: Create or update records related to the current record, such as a Log a Call or New Case action on an account.
• Global actions: Work from anywhere, such as the global actions menu, and create records that aren't tied to a specific parent.
• Predefined field values: Quick actions can fill fields automatically, so users enter less and data stays consistent.