Target audience: Site Administrators, Site Managers, Site Editors
Webforms in the Web Management System (WMS) support functionality such as the Advanced Grid. This feature allows for all types of webform components to be inserted into a grid to create compact, well-formatted text-based forms as well as complex order forms in a single table format.
In this article:
Grids are usually thought of as tables used for conducting surveys or multiple choice questionnaires. A popular example of a grid is a simple form asking customers for feedback:
Using key-value pairs (e.g., machine_readable_text|Human readable text), Site Managers can specify:
Users can then provide feedback by clicking on the radio button that corresponds to their choice.
However, grids can also be used for more complex applications by allowing all types of webform components (not just radio select options) to be inserted.
In this context, a text-based form is a form that mainly uses textfields and textareas.
Traditionally, Site Managers have placed labels above fields so that they align, making forms longer.
If labels are displayed inline, textfields and textareas will generally bump up right beside the label and will align poorly.
Grids can be used to contain form components so that labels and fields are displayed in separate cells.
The example below is an order form that enables users to customize their very own My Little Pony.
Because a grid can now contain other components, various fields can be included within one table. Furthermore, these fields would respond to conditionals and form validation.
Refer to the example above to see options for:
The instructions below show how to recreate parts of the My Little Pony form in the previous example.
Note that Body and Eyes were excluded from the Questions.
Each of the above needs to have a separate select options component because:
Saving the form at this point will display the select components for Body and Eyes lined up with the grid options for Mane and Tail.
The Eyes select component only displays radio buttons for the Light blue, Fuchsia, and Purple, but not for White or Yellow.
After specifying colors for the Mane, Tail, Body, and Eyes, users will be asked if they would like to make their Pony a Unicorn. If Yes, please. is selected…
A new row for selecting the Horn color will display.
If No, thank you. is the choice, the new row would remain hidden. This is done by using conditionals.
After specifying whether they want horns and in which color, users are then asked what kind of markings they would like. If any choice besides -None- is made, another row for selecting the Marking color will appear.
Since Marking color and Body have the same options, users should be prevented from specifying the same color, otherwise the markings will not be visible. This is done through Form validation.
Should the user decide to choose the same Body color and Marking color, error messages notifying them that they did not make a unique choice will be displayed.
Review the form and see that it’s possible to add any sort of component to a grid to create complex but compact forms.