--- schema_version: "1" id: a22d10c1cb6cd3d5c95f32273f9b69b93284f7135b73b85b81241bd8cbdba5dc title: Make Your Screen Elements Dynamic with Reactivity collection: admin version: current locale: en-us portal_url: https://docs.salesforce.com/admin/current/en-us/platform/264-0-0/flow_build_make_reactive.md canonical_url: https://help.salesforce.com/s/articleView?id=platform.flow_build_make_reactive.htm&release=264.0.0&type=5 source_site: help.salesforce.com content_type: documentation content_hash: 92f1025eb6b11125e21cc39ed2981ad3bcad61870ee438989ae4f7f0b4dc0363 description: Use supported flow screen components, formulas, and screen actions to update screen components in real time without leaving the screen. With this reactivity, you can build screens that feel like single-page applications and reduce the number of screens that users have to navigate to complete tasks. This reactivity is supported with API version 59.0 and later. products: - Flow Builder - Salesforce Platform release: "264" --- # Make Your Screen Elements Dynamic with Reactivity Use supported flow screen components, formulas, and screen actions to update screen components in real time without leaving the screen. With this reactivity, you can build screens that feel like single-page applications and reduce the number of screens that users have to navigate to complete tasks. This reactivity is supported with API version 59.0 and later. ### Required Editions
View supported editions.
Before you create a reactive interaction on a screen, decide which screen component is the source of the interaction and which component reacts to changes in the source. For example, consider a screen with three components: - Two Slider components that enable users to select values - A Number component that displays the sum of the values that the user selects in the Slider components ![Two slider components and a number component](https://sf-zdocs-cdn-prod.zoominsoftware.com/tdta-platform-platform_automation-264-0-0-production-enus/60568438-ec7e-4665-acd1-7c80dcbe60d5/platform_automation/images/flow/flow_build_make_reactive_screens.png) In this scenario, the Slider components are the sources of the reactive interaction and the Number component reacts to changes in the sources. Note that all three components in the reactive interaction produce values of the type number. For reactive interactions to work, the source and reactive values are required to be of the same type. To build a reactive screen, it’s easiest to use a standard component. If you use custom flow components, ensure that you review the reactivity examples in the Lightning Web Components Developer Guide. 1. Create a screen flow, and add a Screen element to it. 2. In the Screen element, add and configure the component that is the source for the reactive interaction. For example, add and configure a Data Table component that displays a list of names for the user to choose from. 3. Add and configure the component that reacts to changes in the source component. For example, add a Name component and set the First Name field to **DataTableAPIName.firstSelectedRow.FirstName**. The Name component displays the First Name value of the first row that the user selects in the Data Table. 4. Save and run the flow. While adding reactivity to your screens, consider these behaviors: - Manual outputs of components don’t support reactivity. If you manually set a component output, that variable doesn’t change on the same screen when referenced in other components. - Help text and labels don't react to changes in other components. This consideration doesn’t apply to labels in custom Lightning Web Component that are configured to respond to events in other components. - Data types are required to match when you’re mapping an output to another component’s input to support reactivity. - If validation rules exist for custom components, reactive changes don't trigger validation. - The global variable $Flow is reactive. All other global variables such as Custom Labels, Custom Settings, $Organization, $Profile, aren’t reactive. - When mapping a `DateTime` field to `Time`, the value is converted to GMT and stays converted when navigating between screens. If mapped to a `DateTime` field, the locale is preserved. For example, if the time value is 8:00 AM in your locale, the converted GMT time could be several hours off your time locale (such as 4:00 PM). Refer to A Note About Date/Time and Time Zones for information about Converting Between Date/Time and Text and Date/Time in time zones: [Using Date, Date/Time, and Time Values in Formulas](https://help.salesforce.com/s/articleView?id=platform.formula_using_date_datetime.htm&type=5&language=en_US) - **[Get or Process Data Within a Screen Element with Screen Actions](https://help.salesforce.com/s/articleView?id=platform.flow_ref_elements_screen_flow_screen_actions.htm&release=264.0.0&type=5)** Screen actions make your screen elements dynamic by using an autolaunched flow to retrieve or process data. Screen actions reduce the need for you to add elements between screens and reduce the need for users to switch between screens to observe data updates. Because users click though fewer screens, they can finish a screen flow faster. Also, users benefit from screens that react to their interactions, increasing their engagement. - **[Reactive Screen Flow Components](https://help.salesforce.com/s/articleView?id=platform.flow_build_reactive_screen_flow_components.htm&release=264.0.0&type=5)** Not all screen flow components support reactivity. Review which components do and any limitations that apply. - **[Reactive Screen Flow Formula Operators](https://help.salesforce.com/s/articleView?id=platform.flow_build_reactive_screen_flow_formula_operators.htm&release=264.0.0&type=5)** A subset of the formula operators supported in screen flows support reactivity. - **[Recommendations for Building Reactive Screens](https://help.salesforce.com/s/articleView?id=platform.flow_build_recommendations_for_building_reactive_screens.htm&release=264.0.0&type=5)** When you build screen flows with reactive components and formulas, keep these recommendations in mind. - **[Calculate and Display a Discount on One Screen Example](https://help.salesforce.com/s/articleView?id=platform.flow_builder_flow_example_calculate_a_discount_in_real_time.htm&release=264.0.0&type=5)** This example creates a single screen flow that uses reactive screen components to let sales reps instantly calculate and view product discounts. - **[Retrieve Opportunities for a Selected Account Example](https://help.salesforce.com/s/articleView?id=platform.flow_build_example_retrieve_opportunities_for_an_account_that_a_user_selects.htm&release=264.0.0&type=5)** This example creates a screen flow that lets users select an account, trigger a flow to retrieve related opportunities, and instantly display the results in a table—all within a single screen.