An input field control, similar to an HTML input.
Below is a screenshot of the control. This is from a create step where an admin has added Clarke and Kent in two input controls. Email and Mobile number has no value yet.
Scenarions when the control can be used:
Like above when an admin creates a new object and needs to add data about the object. You can add data controllers to an inout control to verify correct syntax, an @ for email adress, no characters for an mobile number.
You like to display data about an object. You search an LDAP directory and display a user with data about the user. The input control can be in edit or read-only mode.
Properties for Input control
type
Control implementation
N/A
id
Unique ID within the flow
N/A
data
Value to display from session or flow. {{{flow.attribute}}} {{{session.attribute}}}
N/A
config.required
Must have a value when leaving the step. true/false
false
config.readonly
Open to edit by enduser. true/false
false
config.type
Type of input value. Valid JSON types are: string, number, integer, boolean.
"string"
schema.format
Validation of input data. Valid checks: strict, email, phone, postal. See below for more info.
N/A
This is an example from a create step where values are to be added. Mail and mobile have checks for correct syntax.
This is an example from a create step where values are to be added from a session. In this scenario a user has logged in using Swedish BankID.
This is an example from a step where values are to be added from a previous step or from a pipe in a previous step.
The 'config.type' determines how the control is displayed in the view.
For the type 'string' the field can be validated before it is sent to the pipe or next step. The 'strict' validation is recommended as it blocks several common special characters not suitable for Pipe/Valve data handling. Postal is post address.