Appearance
Paritor Forms
The extra questions you ask, written once and attached wherever you need them — dietary requirements on a tour, a medical note on a hire, why somebody wants a place.
Where to find it: Settings > Organisation > Paritor Forms
A form is a list of questions. You build it here, and then attach it to the thing that should ask them: a resource group, an event, a group, a service type's application. The applicant fills it in as part of applying, and the answers come back with them.
A form has a type, and the type is permanent
Paritor Form Type decides where the form can be attached:
| Tuition Application, Group Application, Event Application, Audition Application, Exam Application, Hire Application | Asked while somebody applies for that kind of thing |
| Record Card | Questions held against a record rather than an application |
| Note of Interest | Asked when an interest is logged |
The type can only be set while the form is new
It is offered when you add a form and then disappears — once the form is saved, its type is fixed. If you pick the wrong one you cannot convert it; build the form again under the right type.
So decide where the form will be used before you start writing questions, not after.
Allow Teacher To View lets teachers read the answers rather than only managers. Worth thinking about per form: a teacher taking a group on a tour needs the dietary answers, and probably should not be reading a question about family circumstances.
Writing the questions
Each item is one question. Add puts a new one in the list and Delete removes the selected one.
| Label | The question as the person filling it in reads it |
| Sub Label | The smaller print under it — an example, or what you want included |
| Column Name | The name the answer is stored and reported under |
Then pick the type of answer:
| Label | Not a question at all — a heading or a paragraph of explanation |
| Single-line Text, Multi-line Text | Words, short or long |
| Numeric | A number, with a lowest and highest accepted |
| Date, Email | Checked as you would expect |
| Checkbox | Yes or no |
| Checkbox + Text | A tick and a box to say more — "any allergies?" and then which |
| Dropdown | A list you define |
Making a question required is not obvious
There is no "required" tick. For a text question, set Min Char to anything above 0 and the question becomes required — one character is enough if you only want to force an answer rather than a long one.
Max Char of 0 means no limit, and Max Value of 0 means no upper bound, so leaving them alone is the same as leaving them open.
Where the simple limits cannot express your rule, Valid Formula takes one the answer has to satisfy.
Column Name is the one field to get right first time
It is what the answer is stored and reported under, so changing it after people have answered leaves the old answers under the old name — a report asking for the new one will not find them.
Set it before the form goes out, keep it stable afterwards, and make it something you will recognise in a query a year from now.
Where the answers turn up
An applicant's answers travel with the application and are read wherever it is looked at — on an event's delegates as Additional Info, beside a hire request, and on the activity's own evidence and information. A form attached to a resource group is asked when somebody requests a hire; one on a service type is asked while they apply.
See also
- Paritor Forms fields — every field on a form and its items, one by one
- What the application asks — the standard questions an application asks, as against your own
- Events and Exam Sessions — two of the places a form gets attached
