Conditional field logic changes which questions apply to a visitor's answers. For example, show Company name when Contact type is Business. Core supports field Show/Hide rules; conditional confirmations and notifications are separate Pro features.
Configure a rule group
- Select the target field on the builder canvas.
- Open Conditional logic below its ordinary option groups.
- Enable the group and choose Show or Hide.
- Choose whether All or Any rules must match.
- Select a source field, comparison and value for each rule.
- Select Done, then Save form.
Done, Close and Escape retain local edits; Save form persists them. Builder cards remain visible so you can edit them. Use Preview or an embedded page to check the visitor behavior.
Choose appropriate comparisons
| Source | How to use it |
|---|---|
| Text answers | Equality, inequality, contains, starts/ends with, and emptiness operations where offered. Text comparisons fold case. |
| Choices | Compare the saved choice identity selected by the editor, rather than assuming a changed label is a new value. |
| Multiple selections | Is means the selected set contains that choice. Is not means it does not contain that choice. |
| Number | Use numeric comparisons such as greater than or less than. Zero is a real value; blank is not zero. |
| Name / Address | Use an enabled named component for text or country comparisons. The whole compound field supports emptiness checks. |
| Date / Time | Use the typed comparisons offered for canonical dates and times; their display formatting does not change the saved comparison value. |
Understand Show and Hide
Show makes the target applicable when the group matches. Hide excludes it when the group matches. All requires every rule; Any needs at least one. A missing, deleted, disabled or otherwise unavailable source does not match, including negative or empty comparisons.
When a question becomes conditionally inactive, the browser clears and disables its controls. Showing it again does not restore old selections or reapply defaults. The server independently evaluates applicability and excludes inactive answers from the accepted entry and downstream message values.
Sections, dependencies and unavailable rules
A child field needs both its Section and its own rules to be applicable. A rule cannot depend on itself or form a cycle through other fields, sections or pages. The source picker disables choices that would create a cycle, and Save checks the configuration again.
After deleting a source field or choice, repair retained unavailable references. Internal fields are not public condition sources or targets. Static Hidden visibility is different: a statically hidden value can still supply a rule while applicable.
Test complete paths
Change each controlling answer, including clearing it, and test required fields inside each branch. Final submission validates all applicable questions again. Without JavaScript, conditional questions can initially render while the server still enforces applicability on requests.
The submit button has its own conditional group, edited by selecting it in the canvas. A failing submit condition is also enforced on the server. Page and Next-button rules belong to the multi-page workflow.
