Radio Buttons

Radio Buttons are used on a form to retrieve single option input from the form user, where the users input options are limited by the form designer. In appearance it looks more like a checkbox, but its behaviour is pretty much on par with the pulldown menu. The difference is that all of the available options are displayed on the form with a dial next to each which allows the user to easily see the possible options and select their result right on the form.  For two or three option selections the radio button can be more efficient while on larger list values the pulldown menu may work better.

ch7_p35

Labels and Values: Like the checkbox and pulldown menu, there are a few ways to populate the values of a radio button. The designer can simply key the values into the field provided. The values can also be populated via a lookup from a database table.  If no label is entered the system will display the value by default.

Hide and Show: This is discussed in greater detail in the next chapter, but the general idea is that sections of the form can be open and closed based on the value selected in the radio button.

Font Styles: the radio button is unique in that it provides a second set of font properties for actual object. The font, color, size and style of the fields label can be controlled separately from the font, color, size and style of the selectable values.

Alignment: The values in a radio button can be displayed horizontally or vertically.

Next Action: There is currently only a single defined action which is “Next Form” and it serves the purpose of passing an additional form for the user to complete. To set the action, enter the form ids that need to open with the corresponding Radio Button ‘values’ in the order of appearance. Each action shall be separated by a comma and supports its own parameters. Values with no actions are represented by an empty string. If none of the values require any action then the field can be left blank. The Format for defining nextAction is as follows: <formId>[:parameter(s)]],[<formId>[:parameter(s)].

Practical Example:

A radio button has four values, representing the four seasons. ‘Winter’, ‘Spring’, ‘Summer’ and ‘Fall’. As a designer you want to open a different form for sports registrations based on the respective season the user selects.

In the ‘Next Action’ field you would enter the form id’s for each of the respective registration forms, like this:  345,122,487,498

If there was no ‘Spring’ registrations you would just remove the id, but keeping the comma to separate the values, like this: 345,,487,498

By default, the action will pass the entire XML submission between the two forms and re-map any of the existing data. You can define parameters of ‘global’ and ‘none’ which will either map on the global values or none of them at all. Back to the previous example say I wanted to map only global values for winter, my entry would like this: 345[:global],,487,498.

Contact Form Powered By : XYZScripts.com