When to choose this
Exact behavior
- Sets form-level
hide_submit: truewhile the matching rule’s action value is true (default true). - Studio Rules simulator can still show that the flag matched.
- Fill does not hide or hard-block Next/Submit based on this flag.
- Empty required fields on the current page still fail validation when the respondent clicks Next or Submit.
- Does not clear answers or hide fields by itself.
What changes on fill
Configure in Studio
1
Prefer Require / Show / Jump
For new forms, gate with required answers or route ineligible people with Jump + copy.
2
If you already use Hide submit
Keep explanation blocks so respondents understand eligibility — navigation buttons will still appear.
3
Test on Fill
Confirm Next/Submit always render; only missing required answers block progress.
Worked examples
Unsigned waiver (prefer Require)
When Liability waiver is not signed → Require answer on the waiver (or keep the field required)Canvas copy: “Sign the waiver above to submit.”
Age ineligible (prefer Jump)
When Age less than18→ Jump to pageNot eligiblewith a clear message
Failed quiz threshold
When Score less than50→ Jump to pageRetakewith instructions
Common mistakes
- Expecting Hide submit to remove the button — Fill always keeps Next/Submit.
- Using Hide submit instead of Require for a single missing field.
- Jumping to a non-terminal page and wondering why Next appears instead of Submit — mark ending pages as terminal.
Troubleshooting
Submit still visible when Hide submit matches
Submit still visible when Hide submit matches
Expected. Fill keeps Next/Submit visible; use Require or Jump for real gates.
Cannot continue on a step
Cannot continue on a step
Check required fields on that page (including logic Require answer).
Next instead of Submit on an ending
Next instead of Submit on an ending
Mark the page as terminal in Studio, or ensure the path lands on a terminal page.