Controlling form elements and pages with conditions

Last updated: 05 August, 2026

Conditions let you make your forms dynamic. The form automatically adapts to what users enter, hiding elements or entire pages that aren't relevant. This improves usability and supports data minimization.

There's a basic distinction between element conditions and page conditions. Both follow the same if/then logic, but they differ in what they control and where in the form you set them up.

Key difference at a glance

Element conditions are added as a separate element in the form tree. They control individual fields (e.g., showing a field or making it required).
Page conditions are turned on directly in the settings of the target page. They control entire pages (e.g., skipping a page).

Overview: element conditions vs. page conditions

	Element conditions	Page conditions
What does it control?	The state of a single form element (e.g., an input field, a selection)	The visibility of an entire form page
Possible effects	Shown/Hidden, Optional/Required, Enabled/Disabled, Editable/Read-only	Skip page, continue input on another page, submit the form
Where do I set it up?	As a separate "Condition" element added via the form tree	Via the "Conditions" toggle in the editing area of the relevant page
Available from which page?	On every form page	Only from page 2 onward (page 1 can't be hidden)

Where do I find element conditions?

Element conditions are set up as their own form element:

In the Build area, click the green add icon.
Go to General → Page elements and click Condition.
The new element appears in the form tree, right below the element you had selected. You can drag and drop it to a different position if needed.
On the right, under Edit condition, configure the trigger (If) and the effect (Then).

Where do I find page conditions?

Page conditions aren't added as a separate element — they're switched on directly on the relevant page:

Open the page you want to show or hide.
In the editing area, switch the Conditions toggle on.
Under If, set the triggering form element, the operator, and the value.
Under Then, define what should happen (e.g., skip page).

What they have in common

Both types of conditions are built on the same if/then structure and follow the same core logic around default states.

Core logic: the automatic default state

Formcentric works on a simple principle: you only define the exception — Formcentric handles the default state automatically.

When you set what should happen for a specific input ("If Yes is selected, show field X"), Formcentric automatically knows what applies in every other case ("Otherwise, field X stays hidden"). You don't need to create a rule for the opposite case.

The light switch principle

Think of an ordinary light switch: you only set up that the light should turn on when you flip the switch. You don't need to separately teach the switch that the light stays off while no one flips it — that's just its default state. Conditions in Formcentric work exactly the same way.