"Choice" Task

Input (Choices)	An Array or a specially formatted text. Input will be ignored if "Choices (Static)" is specified.
Output (Selection Out)	Single value or an Array depending on "Single Selection" property

The task prompts the user to make choice by showing a list of choices and allowing single or multiple selection. Choices can be either an array, specially formatted text or manually defined values as "Choices (Static)".. If >Choices (Static)" is specified - input will be ignored.

To define choices in a text the following simple format should be used: each choice should occupy one line and choice's name and value should be delimited by = sign. For example, "Yes | No | Cancel" choices can be defined as:

Yes = 1
No = 2
Cancel = 0

The best way to specify choices as text is to introduce an "Enter Text" task as a part of "Installation Workflow", which would store textual choices in an action, family or system variable.

The following are "Choice" task properties:

Choices (Static): list of static choices - use a decimated editor to maintain it.

Selection In: initial selection

Style: specifies layout for each choice. Possible values are:

- Basic: shows title only.
- Sub Title: shows title and subtitle on bottom
- Right Title: shows title and subtitle on the right
- Auto: automatic layout depending on actual choice type

Presentation: defines behavior of the list. Possible values are:

- List: the user should make selection and press the OK button to continue.
- Buttons: the user should just tap on a choice to continue.

Choice Name: optional macro expression that defines title for a choice. Use a self variable to denote a single choice and then specify property(s) to form a title. For example, $(self.address) defines title as location's address if task shows a list of locations. It is also possible to define sub-title similar way - use pipe | as a delimiter e.g. $(self.address)|$(self.latitude), $(self.longitude).

Single Selection: specifies that only single choice can be made.

Track Usage: tracks selection and stores it in the persistent store. This allows to present choices sorted by recent use. To make it work: the "Selection Out" must be an action variable and a dynamic choices list must be properly sorted by usage using a "Sort Array" task.

Add/Update SWITCH to Handle Selection: specifies whether a related SWITCH task should be automatically added or updated to handle selection. Note, this option is applicable to handle static Choices only.