Form Builder

A form's fields are edited on its Schema tab. The builder is the same one used for profiles, events, and application templates, and a form's fields work like any other custom fields: sections, field types, option sets, and rules. This page covers what is specific to forms.

Sections and Fields

Fields are grouped in sections, shown in order on the form. Each section has a label and an optional description, and can be shown or hidden by a rule like a field. Sections can be dragged to reorder them, and fields to change their order or move them to another section.

Every form starts with a section called Info holding three system fields: First name, Last name, and Email address. They are always required, they are mapped to the profile, and they cannot be deleted, because the email is how a submission finds its profile (see Submissions).

Field Types

The Add field picker offers these types on a form:

Group Type Collects
Standard fields Short answer A single line of text, with an optional maximum length.
Standard fields Long answer A paragraph, with an optional maximum length in characters or words.
Standard fields Number A number.
Standard fields Drop down One choice (or several) from a list of options or an option set.
Standard fields Checkbox Any number of choices from a list.
Fancy fields Programme A programme choice. Only offered when the programme choice field is enabled for forms.
Fancy fields Address A multi-part address.
Fancy fields File upload One or several files, optionally limited to certain extensions.
Fancy fields Email An email address, validated.
Fancy fields Phone A phone number.
Fancy fields Date A date, optionally limited to a range.
Fancy fields Date & time A date and time, optionally limited to a range. Not offered when forms run on version 5.
Fancy fields Country A country, from the built-in list.
Fancy fields Cascading drop down Linked parent and child choices.

See Custom Fields for each type's options.

Field Settings

Click a field to open its settings panel. The Field tab holds:

  • Field type (chosen when the field is created, not changeable afterwards)
  • The label and the instructions shown under it on the form
  • Always required, which makes the field mandatory on every submission
  • The type's own settings: options, maximum length, accepted file extensions, multiple files, date range
  • Logic, the conditional rules described below
  • Translations of the label and instructions for each of the institution's languages

The panel also has a Mapping tab (below) and, on premium editions, a Permissions tab with Can edit: the roles that can change the answer. See Schema Permissions.

A field cannot be deleted while a rule on another field uses it. The panel says which fields to change first.

Conditional Logic

Add logic opens the rules for a field or a section:

Block Effect
Field is shown when / Section is shown when The field or section only appears when a condition is met. Without conditions it is always shown.
Field is required when The field is only mandatory when a condition is met.

Conditions in a block are joined by OR: one met condition is enough. Each condition reads another field on the same form, and the operators depend on that field's type:

Field read Operators
Text fields Is, Is not, Contains, Does not contain, Is empty, Is not empty
Drop down, Checkbox, Country, Programme Is, Is not, Is empty, Is not empty
Number Is, Is not, Is greater than (or equal to), Is less than (or equal to), Is empty, Is not empty
Date Is, Is not, Is before, Is after, Is empty, Is not empty

Conditions are checked as the visitor fills in the form. A field hidden by its rules is not validated, so a hidden required field never blocks a submission.

Note: Always required and a Field is required when rule exclude each other. Remove the rule to use the switch, or turn the switch off to add a rule.

Mapping to the Profile

A field's Mapping tab links it to a profile field with Map to a profile field. On submission, the answer is written to that profile field.

Setting Effect
Profile field The profile field the answer is written to. Address parts can be mapped one by one.
Overwrite existing value On: answers replace whatever the profile holds. Off: answers are only written when the profile field is empty. New mappings start with it on.

An empty answer is never written, so it never clears a profile field. Fields without a mapping are kept on the submission only.

Note: The profile's system email is never overwritten, and a mapping to a system field cannot be changed once saved.

When a signed-in person opens the landing page, mapped fields are filled in from their profile.

Changing Fields After Launch

Answers are validated against the form's fields when they are submitted. Earlier submissions are not checked again when the fields change, and they keep the answers they were sent with.