Show a registration field only when an earlier answer matches
You can now show a registration field only when an earlier answer matches, on a page built on a Livestorm, Zoom or Teams event as much as on an in-person one, and a field that is not shown is neither required, nor validated, nor sent to your platform.
One Visibility setting, three states
In the Form step, each field’s row now carries a Visibility setting with three states. Always shows the field to every visitor. Never hides it from the page while a link can still fill it in, which is the hidden field as before. When… is the new one: the field shows only when a rule on earlier answers matches.
The rule reads as a sentence, Show when, then a field asked before this one, an operator and a value: “Attending as is Press”, “Company is not empty”, “Guests is more than 2”. Up to five conditions, joined with one word, and or or. The operators follow the type of the field being read, so a dropdown offers is and is any of, a date is before and is after, a checkbox is ticked. A value picked from a long list, a country say, is searched rather than scrolled.
The preview shows what visitors will not
The live preview shows a field a rule hides as a dashed row in its place, with what would reveal it, so you see where it sits without answering its question first. Type a matching answer in the preview and the field appears. Visitors never see the dashed row: on the page, the field is simply skipped, and a step whose every field is skipped is skipped too.
A rule that cannot run yet is paused rather than applied halfway: a condition still being written, a field dragged above the one it reads, a source removed by a re-pull. The field then shows for everyone and the row says why. Nothing silently disappears from a live form.
Skipped on the page, skipped on the server
A field the rule hides is not shown, not required and not validated, and its value is neither stored nor forwarded to your event platform. The same rule runs again when the registration is saved, so what the page skipped the server skips too.
The email always shows, since it identifies each registrant. On a page built on a connected event, a field the platform requires always shows as well, because skipping it would make the platform refuse the registration: make it optional there, then re-pull. On an in-person page a field can be both required and conditional, required only when shown. Rules survive a re-pull of the fields, like types and placeholders.