Salesforce Winter '27 Flow supports reactive visibility
Screen conditional visibility rules can now reference reactive formulas, including formulas that use components on the same screen. A component can show or hide as the user types, based on the formula’s result. Previously, conditional visibility could not reference same-screen formulas.
**Suggested check:** Test visibility transitions in both directions, including a return to an earlier input value. For each input, compare the expected component visibility with the observed result.
Route records with Decision splits
The Decision element gains **Split by Date** and **Split by Field Value**. These types route records using a chosen field or the current date, so common branches no longer need handwritten formulas or expressions.
In Flow Builder, add a **Decision** element, select either split type, and define paths and values with the inline pickers.
**Suggested checks:**
- Exercise representative field values for each configured path.
- For date boundaries, test cases before, on, and after the relevant boundary.
- Before replacing existing logic, compare its routing results with the proposed split. Check both against the intended business rule.