Input components
Here is a list of all Input components.
All components are of element type Dictionnary.
| Input components |
|---|
| Text input |
| SecureText input |
| List input |
| Checkbox input |
These components let you ask for end user input. You choose a variable name in the variable key. This variable will be used as a key to let you find the value entered by the end user.
All input values will be available in a single JSON or Plist file. You can choose the format and the path of this file in the Input configuration. Octory will override the content of the file or create one only if the end user has entered at least one input (or if an input component has a default value).
Since Octory 3.1.0, the values entered in SecureText inputs are excluded from that file. Set SavesSensitiveInputs to true if a workflow of yours reads them back.
An input will be saved when one of the following actions is executed:
- when the end user goes to the previous or next slide
- when you have configured a Button component with a SaveInputs action and the end user clicks the button
- when the App terminates
After the end user entered an input, you can use it like a variable in Octory. The name of the variable will be the value of the Variable key, or a composition with the input field(s) when necessary. Refer to the input component to know when a composition happens.
Validation
You can add validation to an input component. It’s a Dictionary in which includes multiple keys to validate the user input. When adding a Validation key, the input component will be considered as Mandatory by Octory. The slide will be unvalid (the user will not be able to go the next slide or to quit the app) until all Mandatory fields are filled correctly.
Alignment
All four input components accept an Alignment key, added in Octory 3.1.0, with the values Left, Center and Right. It moves the label and the control together, as a single cluster, to the chosen edge of the row.
The key has no default: while it is absent, an input keeps the historical placement driven by Distribution and PercentWidth, so existing configurations are unchanged. Alignment and Distribution are independent: Distribution decides how wide the label and the control are, Alignment decides where that cluster sits.