A form is a list of sections (pages or steps for the applicant). Each section holds blocks (groups of related fields), and each block holds fields. Every field has a unique key: the workflow, the pricing rules, the certificate and the integrations all read the answer by that key.
▶ Video walkthrough: watch on Loom

3. Form Builder: the empty canvas

A section and a block, ready for fields

Add Field: pick a field type

Field settings: Basic

Field settings: Validation

Field settings: Expressions

Field settings: JSON
Gotcha · keys are forever
Choose clear keys before you build the workflow and certificate. Renaming a key later silently breaks every rule, price, certificate placeholder or integration that reads the old key: nothing warns you.
Tip · the reference is in the wiki
Every field option is documented in Form configuration · Overview, Custom validation, Custom string expressions and Hint and hint position.
The certificate must print the traveller's full name. What links the certificate to the form?
FullnamesCD10C. Workflows, prices, certificates and integrations read answers by key. Labels are translated and can change; keys cannot.
← A4 · Overview: what citizens read first · A6 · Form Builder II: the code editor and components →