You are here:
Reactive Screen Flow Components
A subset of the screen flow components in Salesforce supports reactivity.
Required Editions
| View supported editions. |
Standard Screen Flow Components That Support Reactivity
You can configure these components to react to changes in other components on the same screen in real time.
| Supported Components | Level of Reactivity |
|---|---|
| Address | Full |
| Checkbox | Full |
| Choice Lookup | Full |
| Currency | Full |
| Data Table | Full |
| Date | Full |
| Date & Time | Full |
| Dependent Picklist | The Dependent Picklist component doesn’t react to changes but can push changes to other components. |
| Display Text | If you reference the output of another component and the output is a record variable of type Currency, the value appears differently in the Display Text component than in other parts of the flow. For example, the flow renders currency values without a currency symbol. To avoid this issue, wrap the reference in a formula. For instance, if a Data Table contains records that include an Amount field of type Currency, you can include a reference to the Amount field by wrapping the reference in a Currency formula. Additionally, if you reference a Choice resource from a previous screen in a Display Text component, the component shows the Choice Label instead of the Choice Value. If you include a reference to another screen component within the text box of the Display Text component, the text is subject to the same character limit as reactive formulas, 3,900 characters. Formatting such as applying bold adds characters that count toward the limit. If the text exceeds the character limit, the Display Text component isn’t reactive. When you debug a flow that includes a Display Text component that reacts to changes on the same screen, Flow Builder doesn’t update the Debug Details pane when the text changes. If you reference a non-Text collection in the Display Text component, you can’t also reference the output of another component on the same screen. For example, if you reference a collection of Date values and the output of a Text component on the same screen, the flow returns an error. |
| Full | |
| Long Text Area | If you reference the output of another component and the output is a record variable of type Currency, the value appears differently in the Display Text component than in other parts of the flow. For example, the flow renders currency values without a currency symbol. To avoid this issue, wrap the reference in a formula. For instance, if a Data Table contains records that include an Amount field of type Currency, you can include a reference to the Amount field by wrapping the reference in a Currency formula. If you include a reference to another screen component within the body of the Long Text Area component, the text is subject to the same character limit as reactive formulas. Formatting such as applying bold adds characters that count toward the limit. If the text exceeds the character limit, the Long Text Area component isn’t reactive. If you reference a non-Text collection in the Long Text Area component, you can’t also reference the output of another component on the same screen. For example, if you reference a collection of Date values and the output of a Text component on the same screen, the flow returns an error. |
| Lookup | Full |
| Multi-Select Picklist | Full |
| Name | The Available Options and salutationOptions input parameter doesn’t support reactivity. |
| Number | Full |
| Password | Full |
| Phone | Validation isn’t triggered when the pattern or value input is changed. |
| Picklist | Full |
| Radio Buttons | Full |
| Repeater | In a Repeater component, child components can reference the output of other child components. However, a child component can’t reference the output of child component in a different Repeater component. Choice components that reference a collection choice set resource in the Choice field aren’t reactive inside Repeater components. References to Repeater components aren’t supported in formulas. |
| Slider | Setting reactivity for sliders can set the values outside the allowable range. |
| Text | Full |
| Toggle | Full |
| URL | Validation isn’t triggered when the pattern or value input is changed. |
| Visual Picker | Full |
Lightning Web Component Reactivity
Reactivity is supported in Lightning web components. However, to configure a Lightning web
component to trigger reactivity in a different component, fire attribute change events
following recommended best practices. To configure a Lightning web component to react to
changes in other components, update the component’s state when the component’s
@api parameter changes.
Flow Components That Don’t Support Reactivity
These components can’t be configured to react to changes in other components on the same screen in real time.
- Display Image
- File Upload
- Aura components
Flow Resources That Don’t Support Reactivity
These flow resources can’t be configured to react to changes in other components on the same screen in real time.
- Variable that you set to the output of a component
- Record choice set
Flow Fields That Don’t Support Reactivity
Record fields (Dynamic Forms for Flow) on screens can’t be configured to react to changes in other components on the same screen in real time.
