- use Branch (choice answers → show follow-ups / go to page), or
- use Add condition (or Edit as When → Then) for the full When → Then editor under the same field
When to use Branch vs Rules
Prefer Branch for ~90% of “if they pick X, show Y / jump” cases.
Non-choice fields (Show if)
Branch is for choice / select / radio answers. On text, number, email, and other non-choice fields, use Show this field if… on the target field:- Select the field that should appear conditionally.
- In the field chrome, click the workflow icon (Show if…).
- Pick the source field, operator, and value.
- Studio compiles a Show blocks rule (inverted attachment — logic lives as a Rules entry that reveals this field).
When Company is not empty → Show blocks Invoice addressSame engine as Branch — only the Studio chrome differs.
When Budget greater than or equal1000→ Show + Require Phone
Branch on a choice field
1
Select the choice field
Click the Multiple choice / Select / Radio that should own the branches.
2
Open Branch
Hover the field, then click the chrome workflow icon (Branch). Selecting the field alone does not open Branch.
3
Configure each answer
For each option: Show follow-up (pick fields) and/or Go to page.
4
Set Otherwise
Otherwise is the default path when no answer branch matches — continue to the next page, or jump elsewhere.
5
Test
Preview or use Logic → Simulator. Confirm follow-ups show/hide and jumps land correctly.
Advanced: When → Then under the field
1
Select the parent field
Click the field that should own the rule.
2
Open When → Then under the field
On a Branch field: chrome workflow icon (tooltip Edit as When → Then while Branch is open), or the Edit as When → Then link under Branch. On Show-if fields: the same icon toggles Show if… ↔ When → Then. On other fields: tooltip Open Rules opens Workflow → Rules.
3
Build When
Source field + operator + value; All / Any groups as needed.
4
Build Then
Common stacks: Show + Require on a follow-up; Hide when not needed; Make optional when a required field should relax.
5
Reorder and test
Multiple rules can live on one field. They run in evaluation order with all other Rules. Preview: pick Other → follow-up shows; pick a normal option → follow-up hides and clears.
Compared to Rules and Calculated
Operator & action tips
- Open the field-type → operator matrix when an operator is missing.
- Blank parent answers do not trigger equals or not equals — use Is empty.
- Hide blocks clears answers.
- Conflict chips appear when rules fight — fix before publish.
- Deleting a follow-up field scrubs Branch / Rules references automatically.
Worked recipes
Other → specify (classic)
- Multiple choice includes option
Other. - Short text “Please specify”.
- On the choice: Branch → Other → Show follow-up “Please specify”.
- Optional: in Rules, Require that field when Other is selected.
Checkbox unlocks phone
When “Call me back” equalsYes→ Show + Require Phone
(Add condition or Rules — same engine)
Empty company hides invoice block
When Company is empty → Hide Invoice address
Common mistakes
Follow-up never appears
Follow-up never appears
Check Branch row for the right option, When value spelling, whether the parent is answered, and whether a later Hide overrides Show.
Follow-up appears but Submit still fails
Follow-up appears but Submit still fails
Did you also Require it? Is another visible required field on the visited path empty?
Old answer resurfaces after hide
Old answer resurfaces after hide
Hide clears answers. If you see old data, inspect Submissions after a clean fill.
I put this only in Rules by mistake
I put this only in Rules by mistake
Fine for testing, but move local follow-ups to Branch so Rules stays readable for routing.