Salesforce Certified Administrator Object Manager and Lightning App Builder

Object Manager and Lightning App Builder Detailed Explanation

This section is critical as it lays the groundwork for customizing the system to fit business processes.

Object Management

Objects are the foundation of Salesforce. They store data in records and can be customized to meet various business needs.

2.1 Standard Objects

Standard objects are pre-built by Salesforce and cater to common business use cases. Below are the most commonly used ones:

1. Account:
   • Stores information about businesses or organizations you interact with.
   • Example: A company like "Tech Corp" is an Account.
2. Contact:
   • Stores details of individuals associated with Accounts.
   • Example: "John Doe," who works at "Tech Corp," is a Contact linked to that Account.
3. Opportunity:
   • Tracks potential revenue-generating deals or sales.
   • Example: A $50,000 software deal in progress with "Tech Corp."
4. Lead:
   • Represents potential customers that are not yet qualified.
   • Example: Someone who downloaded your company’s whitepaper and is interested in your products.

2.2 Custom Objects

Custom objects allow you to create and structure data that doesn’t fit into standard objects.

1. When to Use Custom Objects:

   • If your business needs specific types of data that Salesforce doesn't cover with standard objects.
   • Example: A "Project" object to track client projects.

2. How to Create Custom Objects:

   • Navigate to Setup > Object Manager > Create Object.
   • Define key properties:
     • Object Name: "Project."
     • Record Name: Use "Auto Number" for unique identifiers or "Text" for manual entries.

3. Configuration for Custom Objects:

   • Fields:
     • Add fields such as "Project Deadline" (Date) or "Budget" (Currency).
   • Page Layouts:
     • Decide how information is displayed to users.
   • Validation Rules:
     • Ensure only valid data can be saved (e.g., Budget must be greater than $0).

2.3 Field Management

Fields hold individual pieces of data in an object. Here's a breakdown of field types and relationships:

1. Common Field Types:

   • Text: For descriptive entries like names or titles (e.g., "Project Name").
   • Number: For quantitative data like quantities or scores.
   • Formula: Automatically calculates values based on other fields.
     • Example: Calculate "Total Revenue" by multiplying "Quantity" by "Unit Price."

2. Relationships Between Objects:

   • Master-Detail Relationship:
     • A strict parent-child relationship.
     • Child records cannot exist without a parent.
     • Allows roll-up summaries (e.g., Total Sales for all opportunities under one account).
   • Lookup Relationship:
     • A looser association between objects.
     • Example: Linking a "Project" to a "Contact" for reference.

2.4 Validation Rules

Validation rules enforce data quality by ensuring that entered data meets specified criteria.

1. How Validation Rules Work:

   • They use formulas to check if a condition is met.
   • If the condition is not met, an error message is displayed, preventing the user from saving the record.

2. Examples:

   • Prevent negative numbers:
     • Formula: Amount < 0
     • Error Message: "Amount cannot be negative."
   • Require an email address for Leads:
     • Formula: ISBLANK(Email)
     • Error Message: "Email address is required for all Leads."

Page Layouts

Page layouts control the user interface for records. They determine how data fields, buttons, and related lists appear.

2.5 Page Layouts

1. Purpose of Page Layouts:

   • Organize the fields, sections, and buttons users see when viewing or editing a record.

2. How to Configure a Page Layout:

   • Navigate to Setup > Object Manager > [Select Object] > Page Layouts.
   • Add or rearrange fields, related lists, or custom buttons.
   • Example:
     • Move "Contact Phone Number" to the top of the layout for quicker access.

3. Field Properties:

   • Read-Only: Users can view but not edit the field.
   • Required: Users must fill in the field before saving the record.

2.6 Record Types

Record Types enable different business processes for the same object by using different layouts.

1. Why Use Record Types:

   • To create variations of page layouts for different user groups or scenarios.
   • Example:
     • A "Domestic Opportunity" might have a simpler page layout compared to an "International Opportunity."

2. How to Configure Record Types:

   • Navigate to Setup > Object Manager > [Select Object] > Record Types.
   • Assign Record Types to specific profiles or users.
   • Example:
     • Sales reps in the U.S. see one layout, while reps in Europe see another.

Lightning App Builder

The Lightning App Builder is a drag-and-drop tool used to create and customize dynamic pages for different use cases.

2.7 Lightning Pages

Lightning Pages offer a flexible way to organize and display information.

1. Types of Lightning Pages:

   • Home Page: The default landing page for users.
   • Record Page: The layout for a specific object’s records.
   • App Page: A custom page containing dashboards, reports, or other components.

2. How to Build a Lightning Page:

   • Navigate to Setup > Lightning App Builder > New Page.
   • Choose a layout template.
   • Drag components (e.g., fields, lists, charts) into the page canvas.

3. Embed Components:

   • Standard Components:
     • Dashboards, related lists, or activities.
   • Custom Components:
     • Built using Visualforce, Aura, or Lightning Web Components.

2.8 Dynamic Forms

Dynamic Forms allow you to customize which fields or components are visible based on user roles or record data.

1. How to Enable Dynamic Forms:

   • Dynamic Forms are available for custom objects and some standard objects.
   • Navigate to a Lightning Page and enable "Dynamic Forms" for the object.

2. Examples of Dynamic Fields:

   • Show the "Approval Status" field only if the "Opportunity Amount" exceeds $10,000.
   • Hide irrelevant sections for users in different departments.

Summary

The Object Manager and Lightning App Builder section empowers administrators to create custom data structures, relationships, and user interfaces tailored to specific business needs. By understanding these concepts, you can design a Salesforce environment that’s intuitive, efficient, and aligned with your organization’s processes.

Object Manager and Lightning App Builder (Additional Content)

1. Standard Objects

Standard objects are pre-built Salesforce objects that support common business processes. While you covered common ones like Account, Contact, and Opportunity, it is also essential to understand objects relevant to different teams.

Case (Support Tickets)

• Definition: The Case object tracks customer support requests, commonly used in Service Cloud.
• Use Case:
  • A customer submits a complaint about a faulty product.
  • A support agent creates a Case record and assigns it to the correct department.
• Key Features:
  • Case Status: Tracks the progress (New, In Progress, Escalated, Closed).
  • Case Escalation Rules: Automatically escalate cases if not resolved within a set timeframe.
• Configuration Path:
  Setup > Object Manager > Case

Campaign (Marketing Initiatives)

• Definition: The Campaign object allows marketing teams to manage and track marketing efforts.
• Use Case:
  • A company launches an email marketing campaign.
  • The Campaign object tracks responses and ROI (Return on Investment).
• Key Features:
  • Campaign Influence: Links marketing efforts to won opportunities.
  • Leads & Contacts Association: Tracks customer interactions.
• Configuration Path:
  Setup > Object Manager > Campaign

Quote (Sales Quotation)

• Definition: The Quote object allows sales teams to generate and send pricing proposals to prospects.
• Use Case:
  • A sales rep creates a Quote linked to an Opportunity.
  • The Quote includes products, discounts, and expiration dates.
• Key Features:
  • Sync with Opportunity: Keeps pricing aligned with deal stages.
  • Quote PDF Generation: Converts quotes into PDF documents.
• Configuration Path:
  Setup > Object Manager > Quote

2. Custom Objects

Custom objects allow businesses to create customized data structures that standard objects cannot accommodate.

External Objects

• Definition: External objects allow Salesforce to access and display data from external systems without storing it inside Salesforce.
• Use Case:
  • A company integrates its ERP system with Salesforce to display real-time inventory levels.
  • Instead of duplicating data, External Objects fetch data dynamically.
• Configuration Path:
  Setup > External Data Sources > New External Data Source
• Example:
  • A manufacturing company connects to an SAP database to retrieve inventory stock data.
• Consideration:
  • External objects require API access, such as OData or Salesforce Connect.

3. Field Management

Fields store specific data points within records. Proper field management ensures accurate and organized data.

Roll-Up Summary Fields

• Definition: Roll-Up Summary Fields automatically calculate values based on related child records.
• Use Case:
  • A company wants to see total revenue from all closed opportunities on the Account record.
• Configuration Path:
  Setup > Object Manager > Select Parent Object > Fields & Relationships > New Field (Roll-Up Summary)
• Example:
  • The Account object contains a Total Revenue field that sums all Opportunity "Amount" values where Stage = Closed Won.
• Limitations:
  • Only available for Master-Detail relationships.
  • Cannot be used for Lookup relationships.

Picklist Fields

• Definition: Picklist fields provide predefined selectable values to maintain data consistency.
• Use Case:
  • A Lead Status field ensures sales reps can only select "New," "Contacted," or "Qualified".
• Configuration Path:
  Setup > Object Manager > Select Object > Fields & Relationships > New Picklist Field
• Example:
  • A Case Priority picklist contains "Low," "Medium," and "High".

4. Page Layouts

Page layouts control the arrangement and visibility of fields, buttons, and related lists on record pages.

Global Actions

• Definition: Global Actions allow users to perform common tasks from anywhere in Salesforce.
• Use Case:
  • A sales rep can create a new Contact without navigating away from the current page.
• Configuration Path:
  Setup > Global Actions > New Action
• Example:
  • A support agent can create a Case from the Salesforce mobile app.

Compact Layouts

• Definition: Compact Layouts control which fields appear at the top of a record page in Lightning and Mobile.
• Use Case:
  • Show only critical fields (e.g., Account Name, Phone, Industry) on mobile.
• Configuration Path:
  Setup > Object Manager > Select Object > Compact Layouts

5. Record Types

Record Types allow different users to see customized page layouts and picklist values.

Page Layout Assignment

• Definition: Different page layouts can be assigned based on Record Type.
• Use Case:
  • A bank uses separate layouts for "Business Accounts" and "Personal Accounts".
• Configuration Path:
  Setup > Object Manager > Select Object > Record Types
• Example:
  • Sales users see different fields than Support users when viewing the Account page.

6. Lightning App Builder

The Lightning App Builder allows users to customize Lightning pages with drag-and-drop components.

App Builder Permissions

• Definition: Only users with specific permissions can modify Lightning Pages.
• Use Case:
  • A company restricts page customization to Salesforce Admins.
• Configuration Path:
  Setup > Profiles / Permission Sets > Lightning Page Access

FlexiPage (Underlying Structure)

• Definition: A FlexiPage stores the metadata configuration of Lightning pages.
• Use Case:
  • Every custom Lightning page is technically a FlexiPage.
• Configuration Path:
  Setup > Lightning Pages > Manage FlexiPages

7. Dynamic Forms

Dynamic Forms allow field visibility to be controlled based on user role, record values, or device type.

Supported Objects

• Definition: Dynamic Forms are currently available for custom objects and some standard objects.
• Use Case:
  • A company wants to display different fields based on user role.
• Supported Objects:
  • Custom Objects
  • Standard Objects: Account, Contact (Opportunity, Lead, Case are not yet supported)
• Configuration Path:
  Lightning App Builder > Select Object > Enable Dynamic Forms

Dynamic Field Control

• Definition: Field visibility can be controlled dynamically based on user conditions.
• Use Case:
  • Hide sensitive fields (e.g., "Salary" field on an Employee record) from non-HR users.
• Example:
  • Show "Approval Status" only when "Discount" is greater than 20%.

Summary

These additional Object Manager and Lightning App Builder elements enhance Salesforce customization and user experience:

Key Enhancements

1. Standard Objects Expansion – Understand Case, Campaign, and Quote.
2. External Objects – Fetch real-time external data into Salesforce.
3. Roll-Up Summary & Picklist Fields – Automate data calculations and selection control.
4. Page Layout Enhancements – Use Global Actions & Compact Layouts to streamline UX.
5. Record Types & Page Layouts – Provide custom experiences for different user groups.
6. Lightning App Builder & FlexiPages – Manage Lightning Pages dynamically.
7. Dynamic Forms – Display fields based on user role or record conditions.