Build conditional and multi-step forms

Plan the decision path first

Conditional logic and multi-step forms are included in Drecha Forms Free. Before adding rules, write down the shortest path each visitor should follow.

Example: an enquiry form asks “Are you contacting us as a business?” When the answer is Yes, it shows Company name and makes VAT number required. A later page containing business details is skipped for individual visitors.

Keep one source field near the beginning of the form. Avoid long chains in which one hidden answer controls another hidden answer; they are harder to test and explain.

Show or hide a field

1. Add the source field, such as a Radio buttons field with yes and no stored values.
2. Add the field that should respond, such as Company name.
3. Select the responding field and expand Conditional logic.
4. Under Visibility, choose Show when conditions match or Hide when conditions match.
5. Select Add condition.
6. Choose the source Field, Operator, and Value.
7. When there is more than one rule, choose All conditions or Any condition.
8. Save and test every answer path on the published form.

Available operators are Equals, Does not equal, Contains, Does not contain, Is greater than, Is less than, Is empty, and Is not empty. Greater-than and less-than comparisons require numeric values.

A hidden field is disabled in the browser and omitted from the accepted payload. The server independently evaluates the same visibility rule, so changing browser markup cannot force a hidden answer into the stored entry.

Make a field conditionally required

Use Conditional requirement when a field is optional for most visitors but mandatory in one situation.

1. Select the target field.
2. Leave Required field disabled if it should not always be required.
3. Expand Conditional logic > Conditional requirement.
4. Add one or more rules.
5. Choose All conditions or Any condition when needed.
6. Enter a Custom error message under Validation that explains the required answer.

The requirement applies only when the target field is visible and the rule matches. A field with Required field enabled remains required whenever it is visible, regardless of its conditional-required rules.

Split a form into pages

A Page break starts a new page. Add it immediately before the first field of the next step.

1. Add the first page's fields.
2. Add Page break from the Structure group.
3. Change its Label to a short step title, such as Project details.
4. Add the fields for that page after the page break.
5. Repeat for each additional page.
6. Save and use the public form's Continue and Previous buttons to test navigation.

The browser validates the current page before Continue moves forward. If the server finds an error after submission, the form returns to the page containing the first invalid field and focuses it.

Create a conditional page transition

The Visibility rule on a Page break controls the page that begins after it. This lets the form skip a whole step.

1. Select the Page break that starts the conditional page.
2. Add a Visibility rule using an answer from an earlier page.
3. Choose Show when conditions match for the clearest setup.
4. Ensure the next non-conditional page starts with another Page break.
5. Test both a matching and non-matching answer.

Fields on a skipped page are disabled and not treated as required. The server repeats the page-visibility decision before accepting the response.

Choose a progress indicator

Open Form settings > Multi-step progress and choose:

• Progress bar for a visual completion indicator plus an accessible step label.
• Step count for text such as “Step 2 of 4”.
• No indicator when the form is very short.

Skipped pages are removed from the available-page count, so the current step and progress bar reflect the visitor's actual path.

Free and Pro differences

Conditional visibility, conditional required fields, All/Any matching, conditional page transitions, multi-step navigation, and every progress option in this guide are Free. Pro is not required for these form behaviors.

Pro adds conditional routing for notifications and integrations after a valid entry is stored. It does not replace the Free field and page logic.

Troubleshoot conditional paths

A rule never matches a choice field

Use the option's Stored value, not only its visible Label. Open the choice field and compare the exact stored value with the condition.

Saving reports a circular dependency

One field or calculation eventually depends on itself. Remove one link in the chain so information flows in a single direction from earlier answers to later fields.

A skipped page is still visible

Apply the condition to the Page break that starts that page, not the page break after it. Save, clear any page cache, and retest from the first step.

Continue does not move forward

Correct the first invalid field on the current page. Check its always-required and conditional-required settings and read the displayed validation message.