What are Quick Actions and Global Actions and how to make the most of them?
One valuable feature across a lot of Salesforce’s products is the ability to hand some of the responsibility and repetitive work functions over from the users to the system itself. Salesforce has developed a number of tools to achieve this with Salesforce - Process Builder, Flows, and Workflow Rules are tools that Admins have at their disposal to configure the system to allow users to be more hands-off while ensuring things are still done properly. One feature that’s often overlooked among all the new and flashy tools is Quick Actions.
When people think of Quick Actions, they’ll essentially think of the ‘Lightning Button’, which is partially true. Buttons in Classic were upgraded to Actions in Lightning, but that’s not all an Action is - in fact, they’re quite useful to customise your User Interface!
From creating records, to sending emails, to calling custom Lightning Web Components, Actions are quite versatile.
There are two kinds of Actions - Quick Actions (which are Object Specific) and Global Actions. The main difference between these two is that Global Actions are available for use across Salesforce and are not restricted to a single Object or page. They sit within the Global Publisher Layout.
Object Specific Quick Actions are created against a specific object. Some examples of Object Specific Quick Actions are that you may need a Quick Action that your Users can use to quickly create a new Contact against an Account, or a method of quickly updating some key fields on an Opportunity, or making a Screen Flow quickly available to your users on the Lead Page.
Object Specific Quick Actions have multiple Action Types:
Global Actions have different Action Types to Object Specific Actions:
Let’s create an Update Quick Action on the Contact record that allows a User to quickly update the Email, Phone, and Mobile on a Contact record.
To get started, head to the Object Manager in Setup and find the Contact Object. Open the Buttons, Links, and Actions menu.
Click the New Action button. Set the following values on your new Action:
Action Type: Update a Record
Label: Update Contact Details
Click Save. You’ll be brought to the Update Action’s layout editor. Remove all fields except Email, Phone, and Mobile. You’ll be shown the following error message, which isn’t relevant in our situation - Click Yes.
Fantastic! Your Update Record Action is complete. The next step is exposing it to your Users.
Remember the previous article where you read about Dynamic Forms, and how they were limited to Custom Objects? What if you wanted to highlight some key fields separate to the rest of your Page Layout on a Standard Object like Contacts? Luckily, you can achieve a similar result using Update Actions.
To do this, navigate to a Contact record within your org, click the cog icon at the top and click Edit Page.
Drag the Related Record Component onto the screen, wherever you’d like the Contact Details to show up. Ensure the Update Action is set to the Update Contact Details Action you created earlier, and Lookup Field is set to Use This Contact.
Make sure to Save and Activate your Lightning Page. Now when you head back to the Contact record, you’ll see the three fields from your Update Action available in a separate panel on the Lightning Page.
In this article, you’ve learnt about the difference between Object Specific Actions and Global Actions, and what Action Types are available to each. You’ve gone through the steps to create an Update Action and how to apply it to the Lightning Page to make it behave in a similar way to a Dynamic Form on a Standard Object.
Jump into a Sandbox or Developer org and have a play with some of the other Action types!
How Sysco's team of 40+ developers and admins support a complex Salesforce release flow with Blue Canvas.
Our latest feature offers proactive suggestions so you can avoid dependency errors and better understand relationships between your Salesforce objects.
From your sandbox to a git repository in less than a minute
Why Salesforce DevOps is more than just hooking up a git repo to a Salesforce org
Diving into what it takes to smoothly merge work across Salesforce orgs