Recommendations for Building Reactive Screens

When you build screen flows with reactive components and formulas, keep these recommendations in mind.

Map a component’s input directly to another component’s output. Don’t use merge field references in your input such as 'Hello there, {!Screen_Input_1}!'. Use a formula resource instead.
Don’t use components that actively poll or query data without connecting it to a change event on the screen. If you use reactivity to query data, ensure that you consider user permissions and limit its results to meet performance expectations.
Check and plan for null or empty values in your reactive formulas. Null or empty values that don't meet conditional visibility requirements can't work with reactivity.
Check for self-referencing items as these can cause infinite recursion issues such as in places where a field using a formula that appends text to itself.
Plan for or address any flow scenarios where the formula input that you’re evaluating is blank.
When you add a screen component with a preset default value, manually reset it, or the flow doesn't recognize it at run time. For example, the Slider component has a preset default value of 0. To reset the default value, change the Slider component's default value to 1, and then click into another field like Range Maximum. Change the default value back to 0, and save the flow.

Did this article solve your issue?

Let us know so we can improve!

Product Area