Action Buttons In Screen Flow (Generally Available)

With the Action Button component, the running user can trigger a screen action with the click of a button on a screen. The screen action runs an active autolaunched flow, and the results of the autolaunched flow can be shown on the same screen as the button. This component means fewer screens so users can complete screen flows more quickly and with fewer mistakes. This feature is genrally available now. Couple of enhancements happened -

• • Your screen flow users can see a new indicator in the action button to let them know that the screen action is running.
  • If you update the input and output variables of the action’s autolaunched flow, you can refresh your action’s inputs and outputs without refreshing the browser and the flow.
  • With the new In Progress screen action output, you can reference the in progress status of the screen action launched by the action button somewhere else in the flow. For example, you can disable another screen component on the same screen if the screen action is in progress. To use the In Progress output in an API version earlier than 62, open the screen that contains the action button component and resave the flow.
  • You can disable the action button based on criteria that you set using a resource with a Boolean value.

Enhanced Flow Repeater Component

You can now use the Repeater component to update existing record collections so it’s easier for end users to change a collection of records in a screen flow. Previously, the Repeater component in the Screen element supported only creating records. Watch the video below where I have explained this feature with a use case.

Create or Update Records Efficiently with the Create Records Element

In Flow Builder, you can now use the Create Records element to create or update records based on whether a specified field value exists in the database. The Create Records element makes the process of saving records easier and faster, as you no longer check separately for existing records. By merging create and update into one element, you configure and maintain the flow more easily while reducing potential errors from separate operations.

Enable/Disable Screen Components At Run Time

Now you can disable fields on the Action Button, Dependent Picklist, Lookup, Phone, and Slider screen components by using the component’s Disabled attribute. When the Disabled attribute is set to true, screen flow users can’t focus on or modify any fields in the component. A gray background appears on the component’s input fields to give users a visual cue.

Enhanced Choice Lookup Component

You can now configure the Choice Lookup component to accept either a single selection or multiple selections (up to 25), making it more flexible for your business processes. Previously, only the Lookup component supported selecting multiple options through a lookup field.

Deselect Data Table Rows

Running users can deselect a row in a Data Table component that’s set to single-row selection mode, because we now use checkboxes instead of radio buttons to select or deselect rows. To return to the previous functionality and use radio buttons, in the row configuration section, select Require user to make a selection.

Flow Errors and Warning Pane

Troubleshooting flow errors is easier than ever before. The new Errors and Warnings pane lists issues that prevent you from saving and activating your flow as you work in an easy to scan format. The pane includes links to the Flow Builder canvas that help you identify the source of issues. You can show or hide the new pane with the Show Error button, which includes a notification badge that displays the total number of issues to address.

Identify Inefficient Flow Designs

New tips in Flow Builder help you identify designs that can slow down your flows and increase the risk of reaching Apex governor limits. These tips appear in the Flow Builder canvas and provide guidance on how to improve your flow. By addressing these suggestions, you can ensure that your flows are running efficiently and avoid potential performance issues.

Using CC & BCC Options In Send Email Action

The maximum total number of recipient email addresses is increased from 5 to 150. You can now add CC and BCC recipients to emails by using the Send Email Action in Flow Builder. Any address entered in the CC field receives a copy of the email, and those in the BCC field also receive a copy, but their email addresses are hidden from all recipients.

Final Thoughts

That's all for today. I hope with this blog post and youtube video, you will be able to figure out all the cool flow enhancements that are coming with Winter 25 release. In next couple of days, I will bring more Winter 25 features in this blog as well as my youtube channel. So it is highly recommended that you please subscribe to my channel and blog to come to know about all the nice features. Thank you!!

Disclaimer

This article is not endorsed by Salesforce, Google, or any other company in any way. I shared my knowledge on this topic in this blog post. Please always refer to Official Documentation for the latest information.

0 Comments