If you are creating a Wizard style form as a front-end to a traditional form, you should design the traditional form first.
Wizard style pages are often designed as a "front-end" to a traditional form. In this case, when the user opens the form they see a Wizard page first. As they begin filling the form, they step through a series of simple pages, adding information to each page as they go. Once they have completed all of the Wizard pages, they are then shown the traditional form, which has been populated with the information they entered into the Wizard pages.
If you are creating a Wizard style form as a front-end to a traditional form, you should design the traditional form first. In many cases, the form you want to create already exists on a paper in a traditional format, and it is easy to replicate online. Even if you aren’t replacing an existing paper form, creating the traditional-style form acts as an important guide for the information you need to collect in your wizard pages. For example, each section of the traditional page could correspond to a separate wizard page.
When designing your traditional page, you should:
1. Determine the information you need to collect.
2. Divide the data into logical sections, such as Name, Address, Dependents, Medical Information, and so on.
3. Create the data model (XForms or XML Data Model forms only)
4. Add all of the graphic user interface items, such as fields, lines, labels, and so on.
5. Resize and format your items so they look the way you want and collect the correct type of data.
6. Add help messages to the items that collect user data.
7. If using a data model, bind the items on the page with nodes in the data instance.
Consider a "Request Authorization for Travel" form. It needs to collect the employee’s information, such as name, social security number, and department, as well as the travel dates, and reason for the travel request. Other information that needs to be collected includes mode of transportation, per diem rates, hotel costs, and so on. These logical groupings determine how the page is laid out. For example, name and other employee information will go in the top section of the traditional-style page, travel dates and reason for travel could go in the next section, and so on. Each of these sections will then translate into wizard-style pages, with each section being turned into its own wizard-style page.
The following diagrams demonstrate this format, where three simple wizard pages collect data and pass it to the final page, which duplicates the appearance of a traditional paper form:
Final page (traditional style):
Exceptions to this practice
There are no exceptions to this practice.