Design and Customise Application Forms
In this article
In this article group
Access the Forms Section
On the lefthand-side menu, scroll down to Forms.
View Existing Forms
You can see the current forms available. To edit a form, click the edit button on the right.
Update Fields
Click the edit icon on any field to update it.
Add New Fields
Add new fields by dragging and dropping elements from the righthand-side menu.
Save and Publish
Once done, click Save, then Publish to proceed.
Note: The video above provides a visual walkthrough, guiding you through each step with real-time examples.
How a form is structured
A form is a series of pages the applicant steps through. Within a page you can group related questions into a section, which is a titled block that can be shown or hidden as one. Questions sit either directly on the page or inside a section.
The rule that catches people out is the one at the bottom of that picture. A question can be shown or hidden based on any earlier answer. A page can only be hidden based on answers from an earlier page: a condition pointing at a question on the same page, or a later one, is ignored, because otherwise the page could never be shown and its own question could never be answered.
See Sections and Conditional Questions for the operators available, and for what happens to an answer that gets hidden.
Translating a form
You can add text for your form in other languages, so applicants can fill it in in the language they prefer. English is the default. The other languages are German, Spanish, French, Hebrew, Indonesian, Japanese, Portuguese, and Chinese (Traditional and Simplified).
Open any field and find the Translations section at the bottom. It has one box per language under the English text, and a count showing how many pieces of text are still missing a translation, or "All translated" when nothing is missing. You can translate the label, help message, placeholder, option names, section names and page titles, and the form's own title and description.
Anything you leave out shows in English. A missing translation never leaves a blank. The applicant sees the English text for that piece instead.
Applicants choose their language. When a form has translations, a Form language picker appears at the top of the form. The review step and error messages follow the language they pick.
Answers stay the same. Translating an option does not change the answer that is saved, so reports, exports and your team's view all stay in English.
Questions for your team only (assessor only) are never shown to applicants, so they are not translated for them.
Copying a form keeps its translations. Translations come with the form when it is copied.
Preview shows layout, not behaviour
Preview opens the real applicant form in read-only mode. Every field is disabled, so nothing can be typed into it.
That one fact explains what preview cannot do: with no answers, no condition is ever met, so conditional questions, sections and pages stay exactly as they start. The review and submit steps do not appear either.
To test conditional logic, submit a test application through the real form. There is no shortcut.