- Form Build Order
- Questions to ask before each build
- Forms Vocabulary
Form Build Order
Map out Form before build: i.e. diagram, whiteboard, etc
- Existing Fields
- New Fields
- Roles (if needed)
- Custom Design
- Admin Test
- User Test
Questions to ask before each build
- Who am I building this for? (Audience)
- How do they enter the form?
- Is there a total limit to the number of registrations? A per person limit?
- Will tickets be sold?
- Are there limits to the number of tickets sold?
- Will ticket purchases be driving registration?
- Will a guest list be displayed?
- Are there additional commerce fields needed that do not drive registration?
- Do you need a quantity field to drive registration?
- Will tickets have individual or group limits on sale?
- Are Admin only fields needed?
- Donation Opportunity offered?
- How do constituents exit the form?
- Will a confirmation email be used and what will it say?
- Will Identity Checkpoint be used?
Use the answers to these questions to create a road map for your form prior to building.
Steps: Page display in the form. You can create additional steps to break up information collection flow.
Categories: The containers the hold and sort your data fields. Categories can be used as filters in reporting and can collapse fields from view in a form.
Fields: The tool used to collect the data for storage in your database
Existing Fields: Fields that have been created in your database or mapped over from your back end database (example: profile member fields)
New Fields: A new field that is created because it does not exist in your database. DO NOT create new fields when an existing field is present. (example: phone number field is existing because it is a member field used often, whereas a field requesting someone’s favorite color would be unique and specific to the form it lives in. This would be a new field.)
Suggested Naming conventions
Building Fields - nameoftheform_nameofthefield
Building Roles - nameoftheform_nameofthefield_nameofthevalue
For your reference: Vocabulary and Suggested Naming Convention documents.