You are here:
Reactive Screen Flow Components
Not all screen flow components support reactivity. Review which components do and any limitations that apply.
Required Editions
| View supported editions. |
Standard Screen Flow Components That Support Reactivity
You can configure these components to react in real time to changes in other components on the same screen.
| 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 in other components but can propagate its own changes to other components. |
| Display Text | If you reference a Currency-type record variable from another component, the value may appear without a currency symbol. To avoid this issue, wrap the reference in a Currency formula—for example, when referencing an Amount field from a Data Table. 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, it is subject to the same 3,900-character limit as reactive formulas. Rich text formatting (such as bold) counts toward this limit and can prevent reactivity if the limit is exceeded. 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 simultaneously reference both a non-Text collection and 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 Long Text Area 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 Currency formula—for example, when referencing an Amount field from a Data Table. 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. Rich text formatting (such as bold) counts toward this limit and can prevent reactivity if the limit is exceeded.. If you reference a non-Text collection in the Long Text Area component, you can't simultaneously reference both a non-Text collection and 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 doesn't trigger when the pattern or value input changes. |
| 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 a child component in a different Repeater component. Choice components that reference a collection choice set resource in the Choice field don't support reactivity within a Repeater. References to Repeater components aren’t supported in formulas. The Collection for Prepopulated Items field in a Repeater isn’t reactive. As a result, outputs from a screen action don't populate Repeater data at runtime. |
| Slider | Reactivity can cause slider values to fall outside the configured range. |
| Text | Full |
| Toggle | Full |
| URL | Validation doesn't trigger when the pattern or value input changes. |
| 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 its state when its @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.
- A variable that you set to the output of a component
- Record choice set
Flow Fields That Don’t Support Reactivity
Record fields on screens can't be configured to react to changes in other components on the same screen in real time. This includes fields added using Dynamic Forms for Flow.
