Screen Flow Action Buttons (beta) in Salesforce Summer 24

NOTE: This is currently only available in Pre-Release env for Summer 24.
How many times have you wanted to be able to add custom BUTTONS to your screen flows?
00:00 Intro
04:13 Action Button Demo
08:30 Flow Builder
21:35 Outro
Below are some applications that can now be achieved within a singular screen:
1. Create a data table or a group of radio options for related records when a parent records assembly, such as accounts or contacts, is selected from any component.
2. Import product data from an external system and integrate the obtained results back into the screen for user selection.
3. Design dynamically dependent picklist fields reliant on record data, such as car brands to car models, or school majors and their associated concentrations.
4. Compile a summary of the record selections made from a data table like the earliest date, total sum, or related record details.
As demonstrated, a prime example of reactivity use involves maintaining users on the same screen while selecting an account and needing to display related records for that account-be it cases, contacts, or opportunities. With the feature of Flow-controlled Action Buttons, you can accomplish that swiftly and without difficulty.
The Action Button demonstrates a sequential retrieval of Opportunities, following which it creates Quotes for those Opportunities.
To set up an Action Button component, pull the Action Button component into your screen editor, assign a label to your button, select an active auto-triggered flow, and then organise the inputs into the auto-triggered flow-much like how you would for a subflow.
🔥 Thank you for watching! If you enjoyed this video and found it helpful, please consider hitting the 'Like' button and sharing it with your friends. Your support helps me create more content for you.
✏️ Feel free to leave a comment below; I appreciate your feedback and would love to hear your thoughts on this video. If you have any questions or suggestions for future videos, let me know!
🫡 Don't forget to subscribe to my channel if you haven't already to stay updated with the latest content.
I appreciate your engagement and support! ⭐

[@Jen-ij1tj]

It's refreshing to hear someone say the truth about learning and the process of getting there. It's encouraging. Thank you for sharing your perspective and the demo.

[@paduarte]

Full transparency video. Thanks so much for your feedback! 🫶

[@zacattack556]

Good video. In case you were wondering, the GUID is the ID related to the flow interview for when an auto-launched (or screen) flow executes. Useful if you want to query the FlowInterviewLog record and find information such as how long it took to run, or if the auto-launched flow is paused perhaps in a delay and you need to stop the flow from continuing, then the flow interview can be deleted.

[@paduarte]

This is SUPER helpful! Really appreciate the info. 💪🏻

[@rahulgawale]

Very Nice Video!

[@paduarte]

Glad you found it helpful! Thank you for your feedback 🙌🏻

[@glenndaly1281]

beautifully explained!

[@paduarte]

Hey 👋🏻
Thanks for taking the time to give your feedback!

[@ThePhilryan29]

thanks for putting this together!

[@paduarte]

Glad you liked it! 👋🏻

[@anchalpaul2662]

Thanks for this, it was really helpful ❤ and I also had kind of same scenario. I didn’t use 2 auto launched flows. Everything worked out in single flow itself based on input and output variables.

[@alancapodanno499]

So, you put get record and create record elements in the same flow, correct?

[@paduarte]

Oh really? That's interesting. I need to try again and see if I can get it all under one flow

[@neilhohmann10]

@@paduarte ​In your case, you would still need two separate autolaunch flows (as you've done). That's because the user must make a decision and select one of (possibly) many opportunities to create a quote. A single autolaunched flow cannot pause to accept user input (like a screen flow). Instead, if you just wanted a table of related opportunities and a table of related quotes, then this could be done with just one autolaunch flow (since it wouldn't require additional user input).

[@oyemomimayowa]

Wow, I'm trying this out ASAP

[@paduarte]

Please do! Let me know how you find it 👍🏻

[@skc446]

Can it be used to create records or add contacts to existing accounts records? Like using existing global actions or existing buttons /actions,create record/new record?

[@paduarte]

Great question. Short answer, yes!
Because the Action Button launches a separate flow, you can do a lot of different things. Using the example in the video, I created Quote records.
The full capabilities on this functionality, however, will be discovered after full release and official documentation becomes available.

[@raquelriemer6563]

Can it print for instance the data from a data table

[@paduarte]

It essentially laucnhes a flow, so it works within the limitations of that.

[@steveanderson2084]

GUID = global unique ID. the flow's ID