How a rule reads
A rule is a sentence: if a question meets a condition, then something happens to another question. You build it in the Logic tab, and it reads top to bottom in that order.
| Effect | What it does |
|---|---|
| show | The target stays hidden until the rule matches. |
| hide | The target is visible until the rule matches. A matching hide always wins over a show. |
| make required | The target must be answered, but only while the rule matches — and only if it is visible. |
| jump to | Sends the respondent forward to the screen holding the target. |
| change a value | Adds to, subtracts from, multiplies or sets one of the form's values. See the scoring guide. |
The operators
Twelve, grouped so the list stays scannable: text, presence and numbers.
- Text — is, is not, contains, doesn't contain, starts with, ends with.
- Presence — is empty, is not empty. These ask about the answer alone, so they take no value.
- Numbers — is more than, is less than, is at least, is at most.
“is” and “is not” compare exactly, including capitals. Everything else that compares text ignores case. So “Yes” is not the same answer as “yes”, but “contains ye” matches both.
Combining conditions
Add a second condition to a rule and a match control appears, set to all. Choose all to require every condition, or any to require one. The control is hidden while a rule has a single condition, because there would be nothing to combine.
Combining conditions is a Pro feature, as are the nine operators beyond is, is not and contains. On a free plan the whole rule is dropped rather than run with only its first condition — a rule firing on a condition you did not write would be worse than one that does not fire.
Why a jump sometimes does nothing
A jump moves someone to the screen that holds the target question. That means it only does anything on a form that has more than one screen.
- A single-page form is one screen, so there is nowhere to jump to and the rule is inert.
- Split the form into steps, or switch to one question per page, and the same rule starts working untouched.
- In Studio, screens come from your canvas pages — so a canvas with one form page is still a single screen no matter what the layout setting says.
The Logic tab now warns you when a form has jump rules but only one screen, and it will not let you aim a jump at a heading or a calculated field — neither ever gets a screen of its own.