Input

​

Configuring the Input element

​

Input generic settings

These settings added in the Generic tab are available and they apply to all platforms including Web, iOS, and Android:

• Process data key
• Properties
• Datasource
• Validators
• Expressions
• UI actions
• Input styling

​

Process data key

Process data key establishes the binding between the input element and process data, enabling its later use in decisions, business rules or integrations.

​

Properties

• Label: The visible label for the input field.
• Placeholder: Text that appears within the input field when it is empty.
• Type: Defines the type of data the input field can accept, such as text, number, email, or password.
• Prefix: Label appearing at the start of the input field.
• Suffix: Label appearing at the end of the input field.
• Has Clear: Option to include a content clear mechanism.
• Helpertext: Additional information about the input field, which can be optionally hidden within an infopoint.
• Update on Blur: Update behavior triggered when the input field loses focus.

​

Datasource configuration

The default value for the element can be configured here, this will autofill the input field when you will run the process.

​

Computed datasource value

To add a computed value, you have to explicitly check “Computed value” option (represented by the f(x) icon), which will transform the desired field into a JavaScript editor.

Check the following example:

​

Validators

Incorporating validators into your inputs adds an extra layer of assurance to your data. (For further insights, refer to this link).

Witness the essential role of validators in action with this required validator example:

​

Hide/disable expressions

Define the input field’s behavior using JavaScript expressions to control its visibility or disablement. Configure the following properties for expressions:

• Hide condition: A JavaScript expression that hides the input field when it evaluates to the specified result.
• Disabled condition: A JavaScript expression that disables the input field when it returns a truthy value.

​

Hide expression example

We will use the key defined on the “Income” input field to create the JavaScript hide condition to hide the “Mortgage” input field:

• Rule used:

${application.input.income} === null || ${application.input.income} === ""

• Result:

​

Disable example

For example, you can use a disabled condition to disable an input element based on what values you have on a second input.

When you type ‘TEST’ in the first input (Name) the second input (Test) will be disabled:

• Rule used:

${application.input.name} == 'TEST'

​

UI actions

UI actions can be added to the Input Field to define its behavior and interactions.

• Event: Possible value -CHANGE.
• Action Type: Select the type of the action to be performed.

​

Input settings overrides

There are instances where you may need to tailor settings configured in the Generic settings tab. This proves especially beneficial when you wish to adjust these settings to appear differently across various platforms such as Web, Android, or iOS.

Available override settings:

• Properties:
  • Label: Override the input label.
  • Helper: Override helper text/info point.
  • Placeholder: Override the placeholder.
  • Prefix: Override the prefix.
  • Suffix: Override the suffix.
• Expressions:
  • Hide: Override the hide expression.

​

Input styling

​

Input style overrides options

Theme overrides refer to the ability to modify or customize the appearance and behavior of UI components by overriding default theme settings. This can be applied at various levels, such as specific elements or entire sections, and can be platform-specific (Web, iOS, Android).

Style options: