Skip to main content
Actions are what happens after When is true. You can stack several actions on one rule — show a follow-up and require it and jump to a page, all from the same match. This page is the map. Each action has its own Studio tutorial linked below.

​
How to add Then actions in Studio

1

Build When first

Open Logic → Rules, Branch / Add condition on a field, or a Calculated block. Complete at least one When clause (or Always on Calculated blocks).
2

Expand Then

Below When, click Add action (or use the pre-filled Then on Calculated blocks).
3

Pick an action type

Choose from Show / Hide blocks, Require / Make optional, Disable / Enable blocks, Set / Clear value, Jump to page, Calculate, or Hide submit.
4

Configure targets

Select block(s) from the canvas list, pick a destination page, or build a formula — depending on action.
5

Resolve conflicts

Fix Studio conflict hints (Show ↔ Hide on same target) before publish.
6

Preview on Fill

Walk the form — toggle answers and confirm actions apply and revert live.

​
Action catalog

​
Evaluation order

  1. Form Logic Board rules (top → bottom)
  2. Field-anchored rules and Calculated Always→Calculate in evaluation / canvas order
  3. Hidden or disabled fields forced not required (invariant — you cannot require what they cannot edit)
  4. On fill, hidden answers are cleared so stale data never submits
  5. Set value / Clear value write into the live answer bag (and calculated feed) before jumps run
Last matching rule wins for the same target. If two enabled rules both match and both change visibility, required state, or jump destination, the later rule in evaluation order wins.

​
Common action interactions

​
Where to add actions

Keep Rules for cross-form routing. Put field-specific Show/Require pairs on Branch / Add condition so Rules stays readable.

​
Test on fill (action checklist)

1

Trigger When true

Confirm each Then action visible effect (fields shown, required asterisk, jump, missing submit).
2

Trigger When false

Actions should revert unless another rule keeps them active.
3

Submit attempt

Required visible fields block submit; hidden fields never block.
4

Multi-page jump

Skipped pages stay unvisited — answers there remain blank for operators.
5

Calculate targets

Change inputs — computed fields and downstream When rules update live.

​
Common mistakes

  • Stacking Show and Hide on the same target without exclusive When clauses — last rule wins unpredictably.
  • Require without Show on a hidden follow-up — users cannot answer.
  • Hide submit expecting the button to disappear — Fill always keeps Next/Submit; use Require or Jump.
  • Jump to deleted page — Studio warns; fix before publish.
  • Removing Always → Calculate from Calculated blocks — formulas stop updating.

​
Troubleshooting

When false — incomplete clause, blank source field, or fail-closed comparison value.
Another rule still matches, or a later rule won — inspect Logic Board order.
Visible required field empty — not hidden ones. Check current page validation.
Show ↔ Hide fight on same block — reorder rules or narrow When until hint clears.
Last modified on September 7, 2026