Improve consistency and speed form development by creating form templates.
Form templates are pre-designed forms you can duplicate to quickly create new forms. They often contain key elements and layouts common across a set of forms, such as for a program or division. They also help promote consistency in design and data for your forms.
You can build as many templates as useful to you.
You could build:
A good time to build one is when you are planning to convert all the forms for a program. Often, these forms share certain elements. If you review and compare them before you start, you may find a lot of material that repeats across them. You could set up a template - including things like form and email settings - first, then use that as the basis for converting all the forms more quickly and consistently.
Consider including components like:
You don't have to limit yourself to just one version of each section or set of controls, either.
For example, you might have 3 program areas, each with its own collection statement. You can include all three in the template design, and simply delete the irrelevant copies when creating a new form. Or, you could set up a template for each of the program areas as mentioned above.
It's a good practice to establish a pattern for template naming. Consider things like:
These are just suggestions; use an approach that fits with the type of access and 'architecture' you're using.
To use a template:
A copy of the form will appear as the first form in the Form Summary screen.
After you've duplicated the template:
A template is just another form, and you can revise it as and when necessary. Note that if you're using forms control in the template, any values you enter will be duplicated over to the new form.
You'll either want to:
You may also want to establish a practice for what to do when a template is updated such as:
Practices like these can be established at the appropriate level for your organization; whether you have a centralized form team or work is distributed to divisions or lower.