This article covers the sections that collect information about the person filling in the form, and the Text section for words and images between them:
Contact details
Comments
Custom attributes
Consent / T&Cs
Text
You can use all of them on any type of form.
Contact details
Every form needs a Contact details section. It tells Vega who made the submission. Vega matches the person to an existing contact, or creates a new one.
Choosing the fields
Each field has three settings:
Visible: show the field on the form.
Required: the form can't be submitted without it. Only possible if the field is visible.
Half row: the field takes half the width, so two half-row fields sit side by side (on a phone they always take the full width). First and last name are half a row each by default; Mobile and Phone start at half a row on new forms. The address always takes a full row.
First name and last name are always shown and always required. You can turn the others on or off:
Email
Mobile
Phone
Date of birth
Organisation
Address
Title
Gender
To change the order, drag a field by its ⠿ handle (or select the handle and use the ↑ ↓ keys). The list in the settings is in the order the form shows the fields, and first and last name move as a pair.
A required address needs a street (on either address line) and a postcode, as the old widgets asked. The other address fields are optional.
More than one Contact details section
You can add more than one Contact details section, to ask for details in different places, for example the address on a later page. Vega reads them as one:
The first section asks for the name and holds the personalised-link setting.
Each other field can be on one section only. A field shown on another section is greyed out here, marked on another Contact details section. A new Contact details section starts with every field off.
A field shown on two sections (on a form set up before this) is flagged. Turn it off on one; the form can't be saved until you do.
Organisation
When Organisation is visible, you can tick Provide the option to submit on behalf of their organisation. This gives the person a tick box (worded however you like, e.g. Pay on behalf of this organisation). If they tick it, the organisation's name becomes the account name in Vega.
Address search
When Address is visible, choose how people enter it:
| Option | What happens |
|---|---|
| NZ Post / Australia Post / Google Places | Suggestions from that service as they type |
| Auto – by the donor's country | NZ Post for New Zealand and Australia Post for Australia (where your organisation has them), Google for elsewhere. Only offered if your organisation has NZ Post or Australia Post |
| Manual entry only | They type the address into separate fields |
Until you choose, the form uses your organisation's lookup: NZ Post or Australia Post (Auto, if you have both), otherwise Google Places, otherwise manual entry. Forms moved over from the old widgets work the same way.
With a search, the form shows just the search box, with an Enter address manually link, and a chosen address as one line. Tick Always show the address fields to show the fields all the time, under the search: choosing an address fills them in, and people can check or change each line.
NZ Post and Australia Post are switched on for each organisation in the Vega dashboard. A service your organisation doesn't have is greyed out in the list and marked (not available for your organisation). If a form was set to one that has since been switched off, it stays selected with a note, and the form asks for the address to be typed in until you choose another.
How a looked-up address is filled in
Australian addresses are written as Australia Post writes them: the street, then the suburb, state and postcode. There's no separate city.
Unit numbers are kept, written the usual way, e.g. 2/12 Smith Street.
Your organisation's address mapping: if your organisation has its own mapping in Vega of which parts of an address go into which line (for example, the street on address line 2 and line 1 left for a unit), the lookup follows it, as the old widgets did.
Gender
When Gender is visible, tick the gender options to offer. They come from the Gender attributes in Vega (the shared ones and your own), and the one chosen is saved against the contact. You can't save the form until at least one is ticked, or Gender is hidden.
When someone uses a personalised link
You can send people a link that already knows who they are, for example from an email (see Putting a form on your website). Choose what they see:
| Option | What happens |
|---|---|
| Show a short summary | They see a short card saying who they're filling the form in as, with options to update their details or say Not you?. If a required field is missing from their record, it's shown so they can fill it in |
| Show all the fields, filled in | Every field is shown with their details already filled in. Good for "update your details" forms |
Choosing Not you? clears everything that was filled in, so the next person doesn't see someone else's details.
Comments
A Comments section lets people write a message. What they write is saved as a note on their contact in Vega. You can add as many Comments sections as you like. Each one becomes its own note.
| Setting | What it does |
|---|---|
| Heading | Shown above the fields. Also tells several Comments sections apart in the builder |
| Reason for contact | A dropdown of reasons, e.g. Membership enquiry, Volunteering. See below |
| Subject | A short subject line |
| Message | The main message box |
| Label | Change the wording shown for each field |
| Note type | The type of note created in Vega. General Note if you don't choose one |
| Note subject | The note's subject if the person doesn't give one. If left blank, the heading is used |
Each field can be made visible and required. At least one must be visible.
Reason for contact
This option appears if your organisation has attributes of the Reason for contact type in Vega. Tick the reasons to offer. The reason the person picks is added to their contact. You can also send a different staff notification for each reason, under Form settings → All emails (see Acknowledgements and thank-you pages).
A form can only ask for a reason once. If one Comments section asks, the others won't offer it.
Custom attributes
Custom attributes let you ask your own questions and save the answers against the contact in Vega, for example Interests, T-shirt size or How did you hear about us? On an event form, a question can also be put to the attendees (see Questions for attendees below).
You can add several Custom attributes sections, each with its own heading, to group questions together.
Adding a question
Click + Add custom field, then fill in:
| Setting | What it does |
|---|---|
| Label | The question as people see it |
| Field type | Text box, Text area, Dropdown, Radio, Checklist, Date, or Yes/No |
| Applies to | Only on event forms whose Tickets section collects attendee details: Primary contact, Each attendee – asked in each card or All attendees – asked once. See Questions for attendees below |
| Attribute type / attribute | Where in Vega the answer is saved |
| Width on the form | Full row, half a row or a third of a row, so short questions can sit side by side |
| Label display | Above the field, or beside it (taking a quarter, a third or half of the row) |
| Hidden – always added | The question isn't shown, and its attribute is added to every submission. Greyed out until you've chosen the one attribute it records. Not offered on questions for attendees. See below |
| Required | The question must be answered |
| Show comment box | Adds a box for an extra comment |
| Payment attribute | Record the answer on the payment rather than the contact |
| Payment & contact attribute | Record the answer on both the payment and the contact |
| Active | Untick to hide the question without deleting it |
Use ↑ ↓ to reorder questions and the remove button to remove one.
Adding an attribute to every submission
To record the same attribute against everyone who submits the form, for example Source: Spring appeal, add a field, choose that attribute, and tick Hidden – always added. The tick box is greyed out, with a note, until the attribute is chosen. This replaces the old widgets' "attribute for all submissions" setting.
The question isn't shown on the form, and Required and the comment box are switched off.
Optionally type a Value it records, saved with the attribute.
It also works with Payment attribute to record it on the payment.
You can add several, one hidden field each. The section's summary shows how many are hidden.
The attribute comes from the form's own settings, so nothing a person sends can change it.
Questions for attendees
On an event form whose Tickets section collects attendee details, each question has an Applies to setting, just under Field type:
| Applies to | Where it's asked | Where the answer is saved |
|---|---|---|
| Primary contact (the starting choice) | Once, in the Custom attributes section | Against the person filling in the form, whether or not they're attending |
| Each attendee – asked in each card | In every attendee's card on the Tickets section, the booker's card too when they're attending | Each attendee's own answer, against them. If it's required, every attendee must answer it |
| All attendees – asked once | Once, in the Custom attributes section | The one answer, against every attendee. If it's required, it's answered once. If the booking has no attendees to save it against, it's saved against the person filling in the form instead |
When someone ticks I'm booking on behalf of others, the person booking isn't an attendee, so the two attendee choices are saved only against the people attending. For anything that should go on the person booking, use Primary contact.
The Tickets section's Attendees settings list the questions put to attendees, under Also asked of each attendee, or say how to add one. Questions for attendees can't be Hidden – always added.
If the Tickets section stops collecting attendee details, Applies to is only shown on questions still set to an attendee choice, so you can set them back. A question set to Each attendee isn't asked at all then, and the checklist says so.
Dropdowns, radio buttons and checklists
For these field types, choose what the question is asking:
| Choice | Example | What's saved |
|---|---|---|
| Pick from a list | Interests: Education / Health / Environment | The item(s) they pick are added as attributes to their contact |
| Answer one question | T-shirt size: Small / Medium / Large | Their answer is saved as the value on one attribute |
| Answer the same question for several things | Coordinator: Active / Inactive, Volunteer: Active / Inactive | One answer per attribute |
Then choose the attribute type. Its attributes fill in the list automatically. You can remove any you don't want or change the wording people see. Changing the wording doesn't change the attribute in Vega. Refill from… puts the list back to match Vega.
For "answer one question" and "answer the same question…", choose where the answers come from:
Type my own: you write the answers. They're saved exactly as written.
Copy options from attribute type: the answers are the names of another attribute type's attributes.
A checklist with one item shows as a single tick box.
The builder sums up each question in plain words, for example Form shows: "Interests" as tick boxes, with 3 items… Saved as: each item they tick is added to their record. If anything is missing, it says Still to do and explains what. Vega won't save the form until it's sorted.
Dates
For a Date field, choose whether the date is saved as the attribute's value, its start date or its end date.
Each attribute only once
An attribute can only appear once on a form. Attributes already used elsewhere are marked (already on the form).
Consent / T&Cs
The Consent section holds tick boxes such as I agree to the terms and conditions or I'm happy to receive updates. You can have as many as you need.
For each tick box:
| Setting | What it does |
|---|---|
| Label | The wording. Put words in [square brackets] to make them a link, e.g. I agree to the [terms and conditions] |
| Required | The form can't be submitted until it's ticked. An RSVP decline (Sorry, I can't attend) doesn't need it |
| Record against the contact | Choose an attribute to add to the contact when it's ticked, e.g. a marketing opt-in |
| Link | No link, a web page or file, or a Vega document. Opens in a new tab |
Use + Add checkbox to add one, ↑ ↓ to reorder, and the remove button to remove one.
New forms start with one required tick box: I agree to the terms and conditions.
Text
A Text section adds words and pictures to the form: an introduction at the top, a heading above a group of questions, a note before payment. Nothing in it is submitted. You can add as many as you like, anywhere on the form.
A new Text section starts empty. Add blocks with the buttons at the bottom of its settings, and reorder them with ↑ ↓:
| Block | Options |
|---|---|
| Heading | Large, medium or small; left or centred. Shown in your brand colour |
| Paragraph | Left or centred |
| Divider | A line across the section |
| Image | The image's web address (starting https://), a description for people using screen readers, and small, medium or full width |
| Notice | A tinted box for something that should stand out: Information, Good news or Important |
| Space | A small, medium or large gap |
Paragraphs and notices take simple formatting: **bold**, *italic*, [words](https://link) for a link, a line starting with - for a bullet, and a blank line between paragraphs.
Show in a card (on by default) puts the text in a card like the other sections. Untick it to put it on the page itself, between the cards, which suits a heading for the sections below.
Comments
0 comments
Please sign in to leave a comment.