TECH **Salesforce Administrator: Global Actions, Quick Actions & Publisher Layouts – Zero-Fluff Study Guide**

Salesforce Administrator: Global Actions, Quick Actions & Publisher Layouts – Zero-Fluff Study Guide

1. What This Is & Why It Matters

What it is:
Global Actions, Quick Actions, and Publisher Layouts are Salesforce’s way of letting users do things fast—without leaving the page they’re on. Think of them like shortcuts in a video game: instead of navigating through menus, you press a button and boom—you’ve logged a call, created a case, or updated a record.

• Global Actions = Buttons that work anywhere in Salesforce (e.g., "New Task" from the global header).
• Quick Actions = Buttons tied to specific objects (e.g., "Log a Call" on an Account record).
• Publisher Layouts = The container that holds these actions (like a toolbar where you arrange buttons).

Why it matters in production:
- User adoption plummets if people have to click 10 times to do a simple task.
- Mobile users suffer—if your actions aren’t optimized, they’ll hate the app.
- Process compliance fails—if users can’t easily log activities, your sales/CS teams won’t follow up properly.
- Customization debt piles up—if you don’t set this up early, you’ll waste hours fixing it later.

Real-world scenario:
You’re the Salesforce Admin for a sales team. Reps complain that logging calls takes too long. They’re skipping it, so managers have no visibility into customer interactions. Solution: Add a "Log a Call" Quick Action to the Account page layout, pre-populate fields (like Subject and Related To), and train reps to use it. Result: Call logs increase by 40%, and managers finally have data to coach reps.

2. Core Concepts & Components

3. Step-by-Step Hands-On: Adding a "Log a Call" Quick Action to Accounts

Prerequisites

✅ You’re a Salesforce Admin (or have "Customize Application" permissions).
✅ You’re in Lightning Experience (Classic steps differ slightly).
✅ You have at least one Account record to test with.

Step 1: Create the Quick Action

1. Go to Setup → Object Manager → Account → Buttons, Links, and Actions.
2. Click New Action.
3. Configure:
4. Action Type: Log a Call (this is a special action for call logging).
5. Label: Log a Call
6. Name: Log_a_Call (auto-filled, but you can edit).
7. Description: Log a call with this Account (optional but helpful).
8. Success Message: Call logged! (what users see after saving).
9. Click Save.

Step 2: Customize the Action Layout

1. Still in Object Manager → Account → Buttons, Links, and Actions, find your new Log a Call action.
2. Click the down arrow → Edit Layout.
3. Remove unnecessary fields (e.g., "Priority," "Status" if they’re not relevant).
4. Add useful fields (e.g., "Subject," "Comments," "Call Type").
5. Set predefined values (e.g., "Subject" = Call with {!Account.Name}).
6. Click the wrench icon next to "Subject" → Predefined Field Value → Insert Field → {!Account.Name}.
7. Click Save.

Step 3: Add the Action to the Publisher Layout

1. Go to Setup → Object Manager → Account → Page Layouts.
2. Click Account Layout (or the layout your users see).
3. In the layout editor, find the Mobile & Lightning Actions section (top of the page).
4. Drag your Log a Call action into the Salesforce Mobile and Lightning Experience Actions palette.
5. Remove any actions you don’t want (e.g., "New Task" if you only want "Log a Call").
6. Click Save.

Step 4: Test It!

1. Open an Account record (e.g., "GenePoint").
2. Look for the Chatter feed (or the highlights panel if you added it there).
3. Click the down arrow (▼) → You should see Log a Call.
4. Click it → The form should appear with:
5. "Subject" pre-filled as Call with GenePoint.
6. Only the fields you added (no clutter).
7. Fill in the call details → Click Save.
8. Verify: Go to the Activity Timeline on the Account—your call should appear.

Expected Output

✅ A "Log a Call" button appears on every Account record.
✅ When clicked, it pre-fills the Account name in the Subject.
✅ Only the fields you selected appear in the form.
✅ The call logs to the Account’s Activity Timeline.

4. ? Production-Ready Best Practices

User Experience (UX)

• Mobile-first: Test all actions on the Salesforce mobile app—if it’s clunky there, reps won’t use it.
• Pre-fill everything: Use {!Object.Field} to auto-populate fields (e.g., {!Account.Phone} in a "Call" action).
• Hide irrelevant actions: If users don’t need "New Campaign" on a Case, remove it from the Publisher Layout.
• Group similar actions: Put "Log a Call" and "Send Email" next to each other in the layout.

Governance & Maintenance

• Naming conventions: Prefix custom actions with CUST_ (e.g., CUST_Log_Call) to distinguish them from standard actions.
• Document changes: If you modify an action, log it in a change log (e.g., "Updated Log a Call action to pre-fill Subject on 2024-05-20").
• Test in Sandbox first: Always deploy to Sandbox → test → deploy to Production.

Security

• Field-level security (FLS): If a user can’t see a field (e.g., "Account Rating"), they won’t see it in the Quick Action even if it’s in the layout.
• Record types: If you have multiple record types (e.g., "Customer Account" vs. "Partner Account"), create separate actions for each.
• Sharing rules: Quick Actions respect sharing settings—if a user can’t edit an Account, they can’t use an "Update Account" action.

Performance

• Limit fields in layouts: The more fields in a Quick Action, the slower it loads. Only show what’s necessary.
• Avoid complex formulas: If a predefined field value uses a complex formula, it can slow down the action.

5. ⚠️ Common Mistakes & Traps

6. ? Exam/Certification Focus (Salesforce Admin)

Typical Question Patterns

1. "Which action type should you use to log a call?"
2. ❌ "Create a Record" (Task)

3. ✅ "Log a Call" (special action with call-specific features).

4. "How do you make a Quick Action appear on an Account record?"

5. ❌ "Add it to the Account page layout."

6. ✅ "Add it to the Publisher Layout under Mobile & Lightning Actions."

7. "How do you pre-fill the Subject field in a Quick Action?"

8. ❌ "Use a workflow rule."

9. ✅ "Set a predefined field value with {!Account.Name}."

10. "Where do Global Actions appear?"

11. ❌ "Only on record pages."
12. ✅ "In the global header (available everywhere)."

Key ⚠️ Trap Distinctions

Common Scenario-Based Question

"A sales rep wants to quickly log a call from an Account record without navigating away. What’s the fastest way to set this up?"
- ✅ Create a "Log a Call" Quick Action on the Account object, add it to the Publisher Layout, and set predefined values for Subject.
- ❌ "Create a custom button on the Account page layout." (Too slow, not mobile-friendly.) - ❌ "Use a Global Action." (Not context-aware—won’t auto-relate to the Account.)

7. ? Hands-On Challenge (With Solution)

Challenge

A support team wants a "Escalate Case" Quick Action on Case records that: 1. Pre-fills the Subject as "Escalated: {!Case.Subject}".
2. Sets the Priority to "High".
3. Only shows the Subject, Priority, and Description fields.

Your task: Set this up in 5 minutes or less.

Solution

1. Setup → Object Manager → Case → Buttons, Links, and Actions → New Action.
2. Action Type: Update a Record
3. Label: Escalate Case
4. Name: Escalate_Case
5. Edit Layout → Remove all fields except Subject, Priority, Description.
6. Set predefined values:
7. Subject: Escalated: {!Case.Subject}
8. Priority: High (select from dropdown).
9. Save → Add to Publisher Layout (under Mobile & Lightning Actions).
10. Test: Open a Case → Click "Escalate Case" → Verify fields are pre-filled.

Why it works:
- Update a Record is the right action type (we’re modifying an existing Case).
- Predefined values reduce clicks.
- Limiting fields keeps the form clean.

8. ? Rapid-Reference Crib Sheet

9. ? Where to Go Next

1. Salesforce Help: Quick Actions – Official docs with deep dives.
2. Trailhead: Lightning Actions – Hands-on module.
3. Salesforce Admins Blog: Quick Actions Best Practices – Real-world tips.
4. YouTube: Salesforce Quick Actions Tutorial – Visual walkthrough (search for "Salesforce Quick Actions 2024").