Which OmniScripts elements allow users to select from a set of options? What are the differences between them?

Which OmniScripts elements allow users to select from a set of options? What are the differences between them?

• A. Radio: one selection as buttons; Select: one selection from dropdown list; Multiselect: one or more selections as a checklist.
• B. Radio: multiple selections; Select: no selection allowed; Multiselect: unlimited text input.
• C. Radio: text input only; Select: image choices; Multiselect: numeric choices.
• D. Radio: selects from a dropdown; Select: uses checkboxes; Multiselect: uses date picker.

Answer: (A)

The essential idea is that OmniScript provides different controls for letting users pick from predefined options, and each one handles single versus multiple selections differently. A radio element lets the user choose exactly one option and typically shows them as a row of buttons. It’s ideal when you want to present all choices up front and require a single answer. The selected value is stored as a single value. A select element also enforces a single choice, but the options appear in a dropdown. This is useful when you have many options or want to save screen space; the user still picks only one value and that value is stored as a single value. A multiselect element allows multiple options to be chosen, shown as a checklist. The result is a list of the selected values, not just one. This is the right choice when the user may want more than one option at once, and you bind the result to a collection. These elements can pull options from static lists or from a data source, and the chosen value or values are stored in corresponding variables in the OmniScript flow. The other descriptions don’t reflect how these controls actually behave: radio sets do not support multiple selections, a select control does not inherently prevent a selection, and multiselect does not require text input or a date picker by default.

The essential idea is that OmniScript provides different controls for letting users pick from predefined options, and each one handles single versus multiple selections differently.

A radio element lets the user choose exactly one option and typically shows them as a row of buttons. It’s ideal when you want to present all choices up front and require a single answer. The selected value is stored as a single value.

A select element also enforces a single choice, but the options appear in a dropdown. This is useful when you have many options or want to save screen space; the user still picks only one value and that value is stored as a single value.

A multiselect element allows multiple options to be chosen, shown as a checklist. The result is a list of the selected values, not just one. This is the right choice when the user may want more than one option at once, and you bind the result to a collection.

These elements can pull options from static lists or from a data source, and the chosen value or values are stored in corresponding variables in the OmniScript flow. The other descriptions don’t reflect how these controls actually behave: radio sets do not support multiple selections, a select control does not inherently prevent a selection, and multiselect does not require text input or a date picker by default.