Our users have a million things going on. As admins, we can make their jobs more productive and drive data consistency with a to-do list on the record page, using the Actions & Recommendations component in Lightning Experience. This way, users can track their progress by completing each item on their to-do list.
The Actions & Recommendations component creates a list of actions (flows, Quick Actions, and recommendations from your Next Best Action strategies) for your users. The to-do list can be generated by using an Actions & Recommendations deployment or Salesforce automation tools (Flow Builder or Process Builder). Take a look at the example below to understand the amazing benefits of this component.
Sunshine Cupcakes sells cupcakes on the go. Devohne Mays, Head of Sales Operations, notices that some of his staff is struggling to consistently follow the processes for a cupcake order from creation to completion. His rockstar employees follow the steps consistently, but other employees forget certain steps, leading to inconsistent customer service.
#AwesomeAdmin Addison Dogster wants to remove the need for employees to remember what to do. Thankfully, she recently learned about the Actions & Recommendations component! With this component, she can create a to-do list for the Sunshine Cupcakes staff. All they need to do is go down the list and take the actions shown in the component. Each order can be handled consistently from now on.
Addison decided to build a record-triggered flow using Flow Builder to automate the creation of the actions in the Actions & Recommendations component.
Let’s follow along as Addison builds out the solution using Flow Builder, Quick Actions, and Lightning App Builder.
1. First, Addison creates the Quick Actions, screen flows, or auto-launched flows she wants to show as actions in the Actions & Recommendations component.
2. Next, she creates the record-triggered flow shown above. In Lightning Experience, it can be found under Process Automation | Flows. Click New Flow, then select Record-Triggered Flow.
A. Addison configures the Start element to the following:
B. Next, she adds a Decision Flow element called “New or Status Changed?”, which would determine whether the record is new or the Status field has changed. We need to determine whether the record is new (that is, prior record does not have an id) or whether the status has changed. We’re using the Decision element since, in the Start element, we’re not able to access the prior record.
Best-practice tip: Provide a description so you and other/future admins know what this flow resource is used for.
This is how that flow resource would be configured:
All the Flow elements below fall under the Yes Outcome path.
C. Addison adds a Create Records Flow element called “Create a Log a Call RecordAction”. This will create the Log a Call action in the Actions & Recommendations component.
This is how that flow resource would be configured:
The ActionDefinition is the API name of the Quick Action or flow you want to appear in the component.
Action Type: You can choose between a QuickAction or FlowDefinition (aka Flow).
Order is the display order relative to the other actions.
D. Addison adds a Create Records Flow element called “Create a Process Order Record Action”. This will create the Process Order action in the Actions & Recommendations component.
This is how that flow resource would be configured:
E. She then adds a Create Records Flow element called “Create a Complete Order Record Action”. This will create the Complete Order action in the Actions & Recommendations component.
This is how that flow resource would be configured:
F. Next, Addison adds a Create Records Flow element called “Create a Send a Survey Record Action”. This will create the Send a Survey action in the Actions & Recommendations component.
This is how that flow resource would be configured:
G. She adds a Create Records Flow element called “Create a Send a Email Record Action”. This will create the Send Email action in the Actions & Recommendations component.
This is how that flow resource would be configured:
H. Next, Addison debugs the flow by selecting a record with a status = ‘Submitted’ and specifies to run the flow as if the record is “Created”. Then, she debugs the flow again using a record with a status = ‘Submitted’ but this time specifies to run the flow as if the record is “Updated”.
I. Once you tested the flow using debug and it works as expected, save the flow with these properties. Activate the flow.
3. Next, Addison navigates to the cupcake record Detail page, clicks the wrench icon, and selects Edit Page to open the Lightning Record page in Lightning App Builder.
4. She locates the Actions & Recommendations component and drags it onto the page, then clicks Save.
And we’re done!
Being the #AwesomeAdmin that she is, before Addison deploys the changes to Production, she tests her configuration changes.
We want to learn about the things you’ve built using this feature. Tweet us (@SalesforceAdmns) and share!
New to Flow? Take the Build Flows with Flow Builder trail on Trailhead to learn more.
As an Awesome Admin, it’s probably in your nature to look for any way to optimize a process or situation! As part of that never-ending desire for optimization, I would bet that you’ve spent a lot of time thinking about your permissions setup in Salesforce. Salesforce provides multiple ways to grant permissions to users, each […]
Ready to take the next step in your admin career but unsure where to start? Take a page out of my book and learn development fundamentals to jumpstart your abilities as an advanced admin and extend your Salesforce Platform knowledge. Several years ago, I was at a career tipping point. I felt solid in my […]
Winter ’25 is almost here! Learn more about some of the features coming to Flow and check out Be Release Ready to discover more resources to help you prepare for Winter ’25. General Flow enhancements With Winter ’25, we’re introducing several features that will streamline the flow creation experience and simplify the maintenance of existing […]
