Forms
Ask a set of questions and email or store the answers. One block, with the questions inside it as fields.
What it is
A form asks a set of questions and does something with the answers — emails them, stores them, or both. It is one block: the questions live inside it as fields, and a field exists nowhere else, so there is no separate block to add for a text box or a dropdown.
One page can hold several forms, and a form can be reused across pages so the answers pool in one place.
How to add it
Add a Form block, give it a title, then add fields to it from the bottom of the form. Each field asks one question. Set the submit button's wording, and enter the address answers should go to.
Configure it
Submissions decides what happens to an answer. Email it to one or more recipients — you can set the reply-to address and the subject line — store it as a CSV you can download, or both. You can send the person an acknowledgement, attach the answers as XML for another system to read, and require a captcha before the form will send.
Fields are the questions. Every field has a label — the question itself — optional help text under it, and whether an answer is required. Most also take a placeholder and a default answer, and the whole form can offer a reset button beside submit if you want one.
The type decides what someone is given. For words: Text for a line, Long text for a paragraph, and Static text to say something in the middle of a form without asking anything. For facts: Number, Email address, and Date — a calendar picker, three boxes for a date someone already knows like a birthday, or both together so it can be typed or picked. For choices: Dropdown, Radio buttons, Checkboxes — which can be shown as tick boxes, as a dropdown, or as tags — a Single checkbox for one agreement, and Yes / no. For everything else: File upload, which can limit the file types it offers, and Hidden value, which carries something you need but never asks for it.
A question that offers choices can take them from a list the site already keeps, rather than typing them out. Set Options from and the options are the list's entries — and they stay right as that list changes, which a typed copy does not: the departments move on and the form goes on offering last year's. Leave it empty and you write the options yourself, which is the better answer when they belong to that question alone, like how someone heard about you.
Answer rules check what someone typed before the form is accepted — a minimum or maximum length, a number range, an earliest and latest date, or a pattern the answer has to match. The message you write is what they see when it does not.
Conditions make one question depend on another answer. Say which field it depends on, the comparison, and the value — and then what should happen when it holds.
A question can wait until it applies, and appear only then. It can stay in place but closed, so someone can see what will be asked without answering it yet. Or it can be answered already and not theirs to change — still sent with the form, just not retypable. Someone answering “no” is never asked the three questions that follow from “yes”.
Reuse a form from another page points this block at a form that already exists. The same questions are asked here and the answers pool with that page's, so one definition can be collected from several places. Only the title and description stay local, so it can be introduced differently wherever it appears.
Tips
Ask for the least you need. Every extra question costs completions, and anything you collect you then have to look after.
Use a dropdown when there are more than a handful of options, and radio buttons for a few mutually exclusive ones. Order long lists in a way that helps — alphabetically, or most-common first.
Use three separate day, month and year boxes for a memorable date like a date of birth, and the calendar picker when someone is choosing from a range, like an appointment. Ask for a four-digit year.
Write help text as the hint you would say out loud — the expected format, or what a good answer looks like — rather than repeating the label.
Related pages
A search block's filters are built from the same field types, and answers can be listed with a listing.
Example
Whole forms
One answer, three consequences. Say you have contacted us before and the reference number appears, the case officer is filled in but not yours to change, and the reply choice opens up. Say you have not and the reply choice stays closed where you can see it.
An error is what a submission produces, so this example asks the form to render as though it had been submitted with nothing filled in.