Screen flow

Salesforce makes automation more straightforward and powerful with increased Flow capabilities. We talked earlier about the Spring ’25 release. One of the significant additions to it is Reactive Screen Actions. This feature lets you to auto-launch flows from the screen. And that too without a button click. Today, we will see Reactive Screen Actions in Salesforce Flow. We will give you practical examples to help you understand the new feature.What Are Reactive Screen Actions?Reactive Screen Actions is a new feature added to the Screen Flow element. It is different from the Action Button component. Reactive Screen Actions execute auto-launched flows whenever users’ input changes. It makes Flows more intuitive, eliminates the need for users to perform redundant manual actions, and enhances user experience.Building a Flow with Reactive Screen ActionsToday, let’s create a Screen Flow. Why not dynamically fetch Opportunity records based on a selected Account? Keep reading for step-by-step instructions.Build an Auto Launched FlowBuild an auto-launched flow that retrieves Opportunity records related to a selected Account.Input Variable: AccountID (Text) – The flow will receive this Account ID as input.Output Variable: OpportunityRecords (Record Collection) – The flow will return a collection of related Opportunity records.This auto-launched flow will be the core logic of our reactive screen.Set Up Your Screen FlowCreate a new Screen Flow. Add the Screen element and a screen with a Lookup for a user to get an Account record. Just name the Look up “Account Lookup.”Configure the Action of your ScreenWithin the Screen element, go inside Screen Properties. Insert a Screen action and select one of the screen flows as “auto launched.” Map the AccountID variable from the Lookup component to the flow input. The Screen Action will auto-launch when a user selects or changes an Account in the Lookup.Display ResultsAdd a Data Table component to the same screen to display the Opportunity records that the auto-launched flow returned. Bind the Data Table to the OpportunityRecords variable. With each selection of an Account, the corresponding Opportunity records will appear.Expanding the Functionality with Multiple Screen ActionsThe true power of Reactive Screen Actions lies in their flexibility. You can attach many actions to a single screen, thus building more complex workflows. Here, we provide some examples so you can understand the feature.Example 1: Summarize OpportunityAdd another Screen Action that summarizes the selected Opportunity records. For example, you can display the total revenue or count the records. You could dynamically update a text or number field on the screen.Example 2: Make HTTP CalloutsReactive Screen Actions can also trigger flows that make external API calls. For example, when a user types a question into a text field, the Screen Action can trigger an auto-launched flow that calls ChatGPT and returns the answer.Example 3: Enhance File UploadsThe default File Upload component does not confirm uploads. With Reactive Screen Actions:Start a flow that retrieves uploaded files when the user uploads them.Show the uploaded files in a Data Table to verify.Why Reactive Screen Actions?Reactive Screen Actions make advanced automation possible:Update dynamic, related data without human

Last Updated on April 4, 2022 by Big Idea or Enduring Question:How do you validate user input for Screen Flow Components? Input Validation in Salesforce Flow allows a system administrator to define custom logic and error messages to ensure data integrity. A Validation can contain a formula or expression that evaluates the data in one or more fields and returns a value of True or False. Validation also includes an error message that displays when the rule returns a value of True – indicating that inaccurate data is being entered. In the past, I have written a few articles on Validation Rules and Salesforce Flow. Why not check them out while you are at it?! Getting Started with Salesforce Flow – Part 21 (Validation Rule using a before-save Flow? Yes!)Objectives:After reading this article, you will be able to:Add validation to check what a user enters in a flow screen component and display an error message to guide the userDisplay colorful error message and much more Business Use CaseSteven Greene, a Lead System Administrator at Universal Containers (UC), received a requirement to create a Screen Flow with the following fields:City – Only alphabet characters (A-Z or a-z) are allowed Phone – Minimum 10 and Maximum 15Automation Champion Approach (I-do):To solve the above business use case, will use Screen Flow.Before discussing the solution, let me show you a diagram of a Process Flow at a high level. Please spend a few minutes to go through the following Flow diagram and understand it.Let’s begin building this automation process.Guided Practice (We-do):There are 4 steps to solve Steven’s business requirement using Screen Flow. We must:Salesforce Flow Steps: Define flow properties Add a screen to capture the user’s inputAdd a Text component to store the city Add input validation to validate user input Add a Phone component to store the Mobile Number Add input validation to validate user input Step 1: Salesforce Flow – Define Flow Properties Click Setup.In the Quick Find box, type Flows.Select Flows then click on the New Flow.Select the Screen Flow option and click on Next and configure the flow as follows: How do you want to start building: FreeformIt will open the flow designer for you.Step 2: Salesforce Flow – Add a Screen Element Under Toolbox, select Elements. Drag and drop Screen onto the canvas. Input the following information: Enter Label the API Name will auto-populate.Click Done. Step 3: Salesforce Flow

‘Yes’ side of the flow path to delete the records contained in the selectedRows collection of the data table. And that is it! The flow now looks like this: When we debug the flow with a Contact that is currently subscribed to one Email List, the first screen looks like this:On the next screen, we make some selections: When we push the “Update Selections” button, the flow makes the changes and ends. In cases when used on an actual record page or Salesforce Experience Site page, the flow would automatically start over and show us the first screen again with our changes made: ConclusionThis Flow was a lot of fun to build, and we hope you learned something! This is just one example of the great things that can be done with Salesforce Flows. Follow us on social or subscribe to our monthly newsletter to stay up-to-date on all things Salesforce and automation. Other blogs to explore:• Salesforce Flow Basics: Data, Elements, Decision and Assignment• Using Slack Workflows to Manage Customer Support Requests• Salesforce Flow Basics: Loop, Collection Sort, and Collection Filters• Salesforce Flow Basics: Screen, Pause, Action, and Subflow• Salesforce Flow Basics: Variables, Collections, and Formulas About the Author Jonathan Davis

– Add a Text Component to Store the CityUnder Input section on Screen Element. Drag and drop the Text component onto the screen. Input the following information: Enter a name in the Label field; the API Name will auto-populate.Select Require checkbox.Click DoneStep 3.1: Salesforce Flow – Add Input Validation to Validate User Input – CityIt’s time to add a validation check to verify that city only contains alphabet characters (A-Z or a-z). Under the Text Component, expand the Validate input section. Now we will define the values allowed for the component by entering a Boolean formula. Input the following information:Error Message: Please input alphabet characters onlyUse Rich-Text editor to format error message Formula: REGEX( City, “[a-zA-Z ]*$”)Click Done.Step 4: Salesforce Flow – Add a Phone Component to Store the Mobile Number Under Input section on Screen Element. Drag and drop the Phone component onto the screen. Input the following information: Enter API Name.Field API Name: MobileNumber Label: Mobile Number Required: {!$GlobalConstant.True}Advanced > Revisted Screen Values: Use values from when the user last visited this screen Click DoneStep 4.1: Salesforce Flow – Add Input Validation to Validate User Input – Mobile Number It’s time to add a validation check to verify the length of the mobile number. For this, we will use the regex in the Phone component. Under the Phone Component, expand the Field Properties section. Now we will use the regex to validate the lengthPattern: ^[\d]{10,15}Click Done.In the end, Steven’s Flow will look like the following screenshot (I turned on Auto-Layout) for this flow: Once everything looks good, perform the steps below: Click Save.Enter Flow Label the API Name will auto-populate.Click Show Advanced.Type: Screen FlowAPI Version for Running the Flow: 51Interview Label: User Input Validation {!$Flow.CurrentDateTime}Click Save. Things to Remember:The formula expression must return a Boolean value (true or false).If the flow formula expression evaluates to true, the input is valid.If the flow formula expression evaluates to false, the error message is displayed to the user.If the user leaves the field blank and the field is not required, the flow doesn’t validate.If the user leaves the field blank and the field is required, the flow shows the default error message and not the custom error message.Proof of ConceptNow flow will display an error message if the user doesn’t enter the data correctly.Formative Assessment:I want to hear from you! What did you learn from this post, is it relevant to