The form designer builds the entry form riders fill in when they enter your event. Add fields from a palette, prefill what Horsify already knows about the rider and their horse, and add rules that show, hide, require or fill in fields as the rider answers.
The same designer builds your form templates, including your public membership application form and your club fields. Saving forms and whole events to reuse is in Reusing forms and events with templates.
| On this page |
Before you start
- Your organisation's plan must include the form builder: the Club Site, Club Site Premium, Riding School and Premium plans do. See Horsify plans and prices.
- To edit an event's entry form you need to be an admin, staff with Events and entries at Manage, or on that event's Event team at Manage.
- To edit templates you need to be an admin or staff with Events and entries at Manage. Staff with Members and volunteers at Manage can also edit the membership application and member profile templates. See Staff access: who can do what.
Open the form designer
- Open the event's edit page and go to the Entry form section.
- Choose Open in the form designer to edit the template the event uses, or Advanced: manage per-event forms to create or edit that event's own forms.
You can also open the designer from the organiser menu: Settings → Templates → Form Templates. The same designer edits all three kinds of template: event entry, membership application and member profile (club fields).
The designer has the palette of fields on the left, the form on the canvas in the middle, and the selected field's properties on the right. A second tab, Logic, holds the form's rules.
Add and arrange fields
- Click a palette item, or drag it onto the canvas. Dropdown, Checkbox group and Conditions of entry open the full field editor straight away, because they need options or text before they make sense.
- Click a field on the canvas to select it. The canvas shows each field's type, its Fill in from source, and how many rules touch it.
- Make everyday changes in the properties panel: label, required, Fill in from (any data source, including the two numeric horse heights), This asks about health, and help text.
- Choose All settings, or the pencil button (Edit field) on the canvas, to open the full field editor (options, conditions text, waiver, checkbox items).
- Drag the grip, or use the arrows, to reorder fields.
- Choose Duplicate to copy a field. The copy has no data source, since one source fills one field.
- Choose Preview (beside Add Field, once the form has a field) to see the form as riders will see it.
Prefill rider and horse details
The palette has three groups:
| Group | What it adds |
|---|---|
| Basic fields | Short answer, paragraph, number, email, phone, website, date, dropdown, checkbox, checkbox group, file upload, conditions of entry, information |
| Rider details | Fields already wired to the rider's profile: name, email, mobile, date of birth, address, emergency contact, medical information, membership number, inclusive participation |
| Horse details | Fields wired to the nominated horse: name, show name, height in cm, height in hands, height as text, breed, sex, date of birth, colour, microchip, registrations, owner, owner's membership number, sire, dam |
Rider and horse fields arrive with their Fill in from source set. They prefill at checkout and, for rider fields, write back to the rider's profile when the form is submitted. A smart field already on the form shows ticked in the palette.
Membership numbers
A Membership number field prefills with the rider's number for the organising club when there is one, otherwise their most recently expiring body number. Name a body in the label ("EA number", "Pony Club Australia membership") and that body's number is used instead. A rule can name the body explicitly (see Add rules on the Logic tab below), which is more robust than relying on the label.
Horse registrations
The Registrations field (in Horse details) fills with every registration on file for the selected horse, written as Society: number and separated by commas, for example Equestrian Australia: 12345, Australian Stock Horse Society: 67890. It lists all of the horse's societies, not one picked by the event. The rider can check it and edit anything out of date before submitting.
Riders add their horse's society numbers themselves: see Adding your horse.
Field types
| Palette item | What it collects |
|---|---|
| Short answer | A single line of text |
| Paragraph | Several lines of text |
| Number | Whole or decimal numbers |
| An email address, checked for a valid address | |
| Phone | A contact number |
| Website | A web address |
| Date | A date picked from a calendar |
| Dropdown | One choice from a list |
| Checkbox | A single yes/no tick |
| Checkbox group | Any number of ticks from a list (below) |
| File upload | A photo, PDF or certificate |
| Conditions of entry | Text riders must read and accept |
| Information | Nothing: a read-only notice (below) |
Information
The Information field puts a notice, instruction or disclaimer in the form without asking for anything. It shows as a tinted, bordered panel wherever you place it, on event entry forms, membership application forms and member profile forms.
| Note: The Label is the notice. There is no separate body-text box. Whatever you type into Label is what participants read. Write the full sentence there, not a heading. |
- In the palette, click Information (an info circle, "Read-only notice or instructions"), or drag it where you want it.
- With the field selected, type the whole notice into Label, in plain text.
- Drag it into position, or use the up and down arrows, and save the form.
The editor has no help text, no Required tick box and no data source for this field: it can never be required and never collects an answer. The text is shown exactly as you typed it. HTML is not interpreted (it would appear as literal tags), so write plain sentences.
For example, in the Label box: "Prize money will be paid within 7 days by bank transfer. Eligibility requires current club membership." Or: "Entries close at midnight on the Thursday before the event. Late entries are taken on the day at the higher fee."
| Note: An Information field records no acknowledgement. If you need the rider to actively agree to something rather than just read it, use a Conditions of entry field instead (or, on a membership application form, a Waiver (sign) field). |
Checkbox group
A Checkbox group lets people tick any combination of options from a list you write: volunteer shifts, dietary requirements, interests. Unlike a dropdown, zero or more options can be ticked, and all of them are stored together in the answer.
- In the palette, click Checkbox group (a ticked list, "Tick any that apply"), or drag it onto the form. The field editor opens straight away.
- Enter the Field Label, for example "Volunteer Preferences".
- Optionally add a Description. It shows above the checkboxes, for example "Club events require support from our members. Please advise where you would like to assist:".
- Type each option and press Enter, or click Add. Hover an option to remove it.
- Tick Include "Other" option with free-text field if people should be able to write their own answer. Ticking Other: opens a box to type in.
- Tick Required Field if at least one selection is mandatory (a typed "Other" answer counts).
- Move the field into position (drag it, or use the up and down arrows), and save.
| Note: a checkbox group's options are always the list you type. Unlike some other field types, it can't be linked to a data source that fills the options for you. |
The ticked options (plus any "Other" answer) show as a list under Entry Form Responses on the registration, and riders see the same list on their own registration. A checkbox group can drive rules on the Logic tab, such as showing a field when one option is ticked.
Mark a question as health information
Tick This asks about health on a question you wrote yourself, such as "Any allergies?", or a checkbox group whose options cover allergies, medical conditions, medication or a disability. The tick is in the properties panel and in the full field editor.
Only admins and staff who manage the event (Events and entries at Manage) see the answers to these questions; scorers and stewards with View don't. Fields filled in from a health source (a rider's medical information or inclusive participation details) are treated that way already. Without the tick, staff at View can read a question's answers.
Withheld answers are left out of the entry list, its exports and the registration for staff at View, and the registration page tells them they are withheld. Emergency contacts are still shown at View, so stewards and scorers can reach someone on the day. To let a first-aid officer see medical notes for one event, add them to that event's team at Manage. The tick travels with the form when you save it as a template.
Add rules on the Logic tab
Every rule reads When … then ….
- Open the Logic tab.
- Click Add rule.
- Under When, choose what to look at, an operator and a value. Click Add condition for another; with more than one, choose all of these hold or any of these hold.
- Under Then, choose the action and the field it applies to. Click Add action to do more than one thing.
- Save the form.
Quick starts on the Logic tab add ready-made rules: show a field only for certain classes, prefill a membership number for a body, require a field for riders under 18, ask something extra when the horse is a pony (height under 148 cm).
What a rule can look at
| Look at | Compares |
|---|---|
| The answer to… a field on this form | Text, a dropdown choice, a ticked checkbox-group option |
| A rider or horse detail | Any prefill data source, for example horse height in cm, date of birth, membership number |
| The entry | Classes being entered, disciplines, tickets, horses nominated, who the entry is for (Self / Dependant), the registrant's age |
Operators: is, is not, contains, does not contain, starts with, is empty, is not empty, is ticked, is not ticked, is greater than, is less than. Numeric operators read the number out of formatted text, so "14.2 hands" and "148cm" both compare.
What a rule can do
| Action | Effect |
|---|---|
| Show / Hide | A field targeted by a Show rule starts hidden and appears when the rule holds. Hidden fields are not validated and not submitted. |
| Make required / Make optional | Overrides the field's own Required setting while the rule holds. |
| Set the value of | Puts a fixed value in the field. |
| Copy another answer into | Copies the rider's answer from one field to another. |
| Prefill from rider or horse details | Fills from a data source. For membership number you can name the body (EA, PCA…). |
| Clear | Empties the field. |
Value actions fill an empty field, or refresh a value the same rule wrote earlier. Tick Replace what the rider has typed to overwrite.
Rules are evaluated live as the rider fills in the form at checkout. The form receives the rider's nominated horse and the classes, tickets and horses in their cart, so "classes being entered contains Pony" works without the rider doing anything.
Where rules run
Rules run wherever a form built with the designer is filled in, and a rule behaves the same on each. What a rule can read differs, because not every form has an entry or a rider profile behind it:
| Where the form is filled in | Answers on the form | Rider or horse details | The entry |
|---|---|---|---|
| A rider entering an event (checkout) | Yes | Yes | Yes: classes, tickets, horses, Self/Dependant, age |
| An organiser adding a registration by hand (phone or paper entry) | Yes | Only when the email typed matches a rider your club already knows (a member, a client, or an entrant in another of your events) | Yes: the classes, tickets and horse names being keyed in, and the age of a matched rider |
| Your public membership application form | Yes | No | No |
| Club fields on a member (the member panel and Add Member) | Yes | The template's own profile-linked fields | No |
A condition about something a form cannot read is simply never true there (and an "is empty" condition is true). So on a membership application, write rules about the applicant's answers, such as "show Where is your horse kept? when Do you have your own horse? is Yes", rather than about classes or horse details.
Rules are stored with the form and follow its fields: when an event first uses a template, when you clone an event, save a form as a template, or load a template into a new form. If you delete a field a rule uses, that part of the rule is removed, and a rule left with no actions is removed too.
Related guides
- Reusing forms and events with templates
- Adding competition classes
- Exporting an entry list
- Taking membership applications online
- Adding an entry by hand
|
Still need a hand? Open the Help bubble at the bottom of any Horsify page to ask a question or send us a message, or email support@horsify.com.au. More guides on this topic: Entries and entry forms. |