Salesforce now sends email only from verified domains.

Help Agent Performance Degradation

Automate Your Business Processes

Table of Contents

No results

Here are some search tips

Check the spelling of your keywords.
Use more general search terms.
Select fewer filters to broaden your search.

Search all of Salesforce Help

Considerations for Reactivity in Screen Flows

You are here:

Considerations for Reactivity in Screen Flows

Review these considerations before you set up reactivity in your screen flows. Reactivity is supported with API version 57.0 or later.

For information on how to set up components for reactivity, refer to Make Your Screen Elements Dynamic with Reactivity

General Considerations

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.
Data types must 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, are not 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