Add fields and functionality to your form.
After completing your new form's general settings, you're presented with a basic form structure in the editor.
This form includes:
This is the minimum structure of a form and the starting point for building your form.
Before you start building your form, there are a few things to consider depending on your situation and preferred build process.
If you're part of a team or have ministry standards, your first section might be used for:
You can save time setting this up by copying from another form, including a template.
You're new form includes a plain text control. Since this is the most common control you'll use for your form, consider copying it first. You can then rapidly paste as many as you need to set up your form. The control will stay in memory until you copy something else. If you're working from a mock-up or PDF, you can quickly develop the layout first, and then go through and configure the fields.
You can also copy controls - including grids and sections - from another form. This can save you even more time if you're able to repurpose something from another form or template, such as form control or common components like:
If you want to copy controls from one or more other forms for your new one, it's generally easiest and fastest to have all the forms open at the same time.
To work with multiple forms simultaneously:
You can now quickly switch between forms to copy and paste from one to another.
The order in which you build your form is completely up to you.
Your primary activities are going to be:
If this is your first form, it's been a while sine your last one, or you have a situation you haven't encountered before, consider reviewing the Cookbook.
The general process of adding a control is:
If you pre-populated your form with copied controls, then you'll just select each and apply steps 3-6.
It's good practice to test your form frequently while you build it. This is referred to as build testing.
While you may not need to do much testing for basic data fields, you'll probably want to do it more frequently when your form includes things like:
Testing as you go will help you identify issues and errors and make troubleshooting logic errors - the "CMS Lite is unavailable" error - much easier.