A text area is a form element used to capture multi-line input from users in a conversational interface. The text area component is typically used for longer inputs such as descriptions, comments, or feedback, providing users with more space to type their responses.
It is an important tool for creating intuitive and effective conversational interfaces that can collect and process large amounts of user input.
These settings added in the Generic tab are available and they apply to all platforms including Web, iOS, and Android:
Process data key creates the binding between form element and process data, so it can be later used in decisions, business rules or integrations
The default value for the element can be configured here, this will autofill the text field when you will run the process.
You can add multiple validators to a text area field. For more details, refer to Validators.
The text area’s behavior can be defined using JavaScript expressions for hiding or disabling the element. The following properties can be configured for expressions:
In the example above, we used a rule to hide a text area element if the value of the switch element above is false.
We will use the key defined on the switch element to create a JavaScript hide condition to hide the text area element:
For example, you can use a disabled condition to disable a text area element based on what values you have on other elements.
When you choose a specific value on the radio element (Contact via SMS), the text area is disabled based on the disabled condition.
It’s important to make sure that disabled fields have the same expression configured under the path expressions → hide.
UI actions can be added to the text area field to define its behavior and interactions.
CHANGE
.For more details on how to configure a UI action, click here.
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:
Overrides can always be imported/pushed from one platform to another:
Adjusting the size of components is crucial for a responsive design. Fit W (width) offers three 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:
Common Properties
Label
Helper
Error
Empty State
Active State
Filled State
Disabled State
Error State
Hover State (only for Web configuration)
You can import or push the overrides from one platform to another without having to configure them multiple times.