Certified Platform App Builder User Interface

User Interface Detailed Explanation

The User Interface (UI) in Salesforce is designed to make interactions with data intuitive and customizable for different user roles. This section focuses on configuring the layout, structure, and tools available for records and apps in Salesforce.

Core Feature 1: Page Layouts

What are Page Layouts?

• Page Layouts control how fields, buttons, related lists, and other components appear on a record page. They are central to customizing the user experience.

Capabilities:

1. Field Visibility:

   • Determine which fields are visible, editable, or read-only for users.
   • Example: A sales rep might only see "Contact Name" and "Phone," while a manager can see additional fields like "Revenue."

2. Different Layouts for Different Roles:

   • You can assign different layouts based on user roles or profiles.
   • Example: Sales reps and service agents can have different views of the same Account record.

Practical Steps for Beginners:

• Experiment with the Page Layout Editor:
  • Add, remove, or rearrange fields.
  • Adjust the placement of buttons and related lists.

Core Feature 2: Record Types

What are Record Types?

• Record Types allow you to create variations of a single object to meet different business requirements.
• Example: An "Opportunity" object can have different record types for "New Business" and "Renewal," with tailored fields and picklist values for each.

Use Cases:

1. Custom Picklist Values:

   • Provide unique picklist values for different business processes.
   • Example: For a "Case" object:
     • Support team sees picklist values like "Technical Issue" or "Billing Query."
     • Sales team sees picklist values like "Product Inquiry" or "Upgrade Request."

2. Specific Field Visibility:

   • Show or hide fields based on the record type.
   • Example: On a "Contact" object, show a "Subscription Details" field only for customers and not for prospects.

Practical Steps for Beginners:

1. Create a new Record Type in an object.
2. Assign the record type to specific profiles.
3. Customize Page Layouts to match the record type.

Core Feature 3: Lightning App Builder

What is Lightning App Builder?

• A drag-and-drop tool for building custom pages and applications in Salesforce. It’s used to create dynamic and user-friendly interfaces.

Capabilities:

1. Drag-and-Drop Customization:

   • Add and arrange components on a page without coding.
   • Example: Embed a chart, related list, or custom button directly into a record page.

2. Embed Components:

   • Use prebuilt components or custom ones to add features to your pages.
   • Example:
     • Standard Components: Record details, related lists, or reports.
     • Custom Components: Built using Lightning Web Components (LWC) for advanced functionality.

Practical Use Cases:

• Build a Custom Home Page:
  • Add performance charts, recent activity feeds, and tasks.
• Enhance a Record Page:
  • Include a section showing the latest customer interactions for an Account.

Practical Steps for Beginners:

1. Open Lightning App Builder.
2. Choose a page type (e.g., Home Page, App Page, Record Page).
3. Drag standard components like reports or fields onto the page.
4. Save and activate the page for specific users or profiles.

Core Feature 4: Quick Actions

What are Quick Actions?

• Quick Actions are buttons that let users perform frequently used tasks with a single click, saving time and effort.

Types of Quick Actions:

1. Object-Specific Quick Actions:

   • These actions are tied to a specific object.
   • Example: On an Opportunity record, you can have a "Log a Call" action to quickly document a conversation.

2. Global Quick Actions:

   • These actions are available across all objects and records.
   • Example: A global "Create Task" action allows users to add a task from anywhere in Salesforce.

Use Cases:

• Add an "Update Status" action to the Case object to let users quickly change the status.
• Provide a global "Log Meeting" action to track meetings across all objects.

Practical Steps for Beginners:

1. Go to Object Manager in Salesforce.
2. Create a new Quick Action for an object.
3. Specify the fields and layout for the action.
4. Add the action to the appropriate Page Layout or Global Actions Menu.

Summary Table for Core Features

Feature	What It Does	Use Cases
Page Layouts	Controls the display of fields, buttons, and related lists.	Customize layouts for different roles (e.g., sales reps vs. managers).
Record Types	Differentiates record categories for specific business needs.	Tailor picklists and layouts for product lines, processes, or user profiles.
Lightning App Builder	Drag-and-drop tool for creating custom app pages.	Build dynamic home pages, app pages, and record pages with embedded reports and components.
Quick Actions	Adds buttons for common tasks.	Create shortcuts for tasks like logging calls, updating statuses, or creating records.

Beginner’s Practical Steps

1. Experiment with Page Layouts:

   • Customize layouts for standard objects like Accounts and Contacts.
   • Practice assigning different layouts to different profiles.

2. Create a Record Type:

   • Use the Opportunity object to create separate record types for new deals and renewals.
   • Assign unique picklist values to each record type.

3. Build a Page with Lightning App Builder:

   • Create a new record page and add standard components like charts, related lists, and reports.

4. Set Up a Quick Action:

   • Add a quick action to log calls or update statuses on Opportunities.

User Interface (Additional Content)

User Interface (UI) in Salesforce is designed to enhance user experience by providing intuitive, customizable layouts and actions.

1. Page Layouts

Page Layouts control how fields, actions, and related lists appear on a record page. They help define the UI experience for users based on their role and profile.

Actions & Related Lists

• Actions: These are buttons such as "New Task", "Send Email", and "Log a Call" that can be added to a Page Layout.

  • Example: Sales reps may have a "New Opportunity" action, while service agents may have a "Create Case" action.
  • Actions are defined in Page Layouts but can also be controlled dynamically using Dynamic Actions.

• Related Lists: These display related records on an object’s record page.

  • Example: On an Opportunity record, Related Lists can show Contacts, Quotes, and Cases linked to that Opportunity.

Page Layouts vs. Lightning Record Pages

Feature	Page Layouts	Lightning Record Pages
Supported UI	Classic UI & Lightning	Lightning Only
Controls	Fields, buttons, related lists	Components, dynamic fields, layouts
Custom Components?	No	Yes
User-Specific Customization?	Limited to different Page Layouts	Dynamic Forms, Dynamic Actions
Best For	Standard field & button control	Custom UI with enhanced flexibility

Key Takeaway: Use Page Layouts for basic field and button control, while Lightning Record Pages provide advanced UI customization with dynamic visibility settings.

2. Record Types

Record Types allow different variations of a record within the same object, enabling customized layouts, picklist values, and business processes.

When to Use Record Types vs. Page Layouts

Scenario	Use Record Types	Use Page Layouts
Different business processes (e.g., Retail Sales vs. Enterprise Sales)	Yes	No
Different field requirements based on department (e.g., HR vs. Finance)	Yes	No
Same business process, different UI layout for different roles	No	Yes

Limitations of Record Types

• Does not affect non-picklist fields:
  • You cannot change the visibility of text fields, number fields, or formula fields based on Record Types.
• Impacts automation:
  • Workflows, Flows, and Approval Processes often need to account for Record Types, adding complexity.
  • Example: A Flow may need multiple decision elements to handle different Record Types.

Best Practice

• Use Record Types only when necessary (e.g., different business processes).
• For UI changes without business process differences, use Page Layouts or Dynamic Forms.

3. Lightning App Builder

Lightning App Builder allows users to create customized pages in Lightning Experience using drag-and-drop components.

Dynamic Forms & Dynamic Actions

• Dynamic Forms:

  • Allow field visibility to be controlled based on criteria such as User Profile or Record Field Values.
  • Benefit: Eliminates the need for multiple Page Layouts.
  • Example: Show the "Discount Percentage" field only if the "Deal Size" is greater than $10,000.

• Dynamic Actions:

  • Allow buttons and actions to be conditionally displayed based on record data or user permissions.
  • Example: A "Submit for Approval" button only appears if a record's status is "Pending".

Lightning Record Page vs. Page Layouts

Feature	Lightning Record Page	Page Layout
Field Visibility Control	Yes (Dynamic Forms)	No
Button Visibility Control	Yes (Dynamic Actions)	No
Supports Custom UI Components?	Yes	No
When to Use?	Advanced UI customization	Standard field layout

Best Practice:

• Use Dynamic Forms to reduce the number of Page Layouts required.
• Use Dynamic Actions to show context-aware actions.

4. Quick Actions

Quick Actions improve efficiency by providing shortcuts for users to perform frequent actions.

Differences Between Quick Actions & Custom Buttons

Feature	Quick Actions	Custom Buttons
Purpose	Standard UI actions (e.g., create/update records)	Custom navigation or external API calls
Visibility	Can be added to Page Layouts & Global Actions	Placed on related lists, detail pages, or custom components
Customization	Form-based UI	Can execute JavaScript, Apex, or Visualforce

Best Practices for Quick Actions

• Use Global Quick Actions for commonly used actions available across multiple objects.
  • Example: A "Log a Call" action should be available on Leads, Contacts, and Opportunities.
• Avoid excessive Object-Specific Quick Actions.
  • Why? If each object has custom actions, users may experience inconsistent workflows.
  • Instead, consider Lightning Components or Screen Flows for multi-object processes.

Conclusion

The additional concepts covered in this section refine our understanding of User Interface customization in Salesforce:

1. Page Layouts control standard field and button placement, while Lightning Record Pages allow advanced UI customization.
2. Record Types should be used only for different business processes, not just different field layouts.
3. Lightning App Builder provides powerful customization tools like Dynamic Forms & Actions for user-specific experiences.
4. Quick Actions provide efficient task execution, but should be used strategically.