Overview

A text area is a user interface element used for inputting large amounts of text. Unlike a single-line text input field, a text area supports multi-line input, making it ideal for longer entries like comments, messages, or descriptions. 

​

Key Characteristics

1. Multi-line Input: 

   • A text area allows users to type and view multiple lines of text at once. 

   • The size of the text area can typically be adjusted by developers or users (e.g., via drag-resizing). 

2. Customizable Dimensions: 

   • Scrollbars appear automatically when the content exceeds the visible area. 

3. Placeholder Text: 

   • Optional placeholder text can provide guidance on what kind of content to input. 

4. Dynamic Behaviour: 

   • Can support advanced features like character limits.

​

Common Use Case

• Writing comments or feedback on websites. 

• Filling out descriptions in forms. 

• Creating or editing documents or long text entries. 

• Composing emails or messages in web applications. 

​

Various Fields in Text Area Input

• API Name: The API Name is a unique identifier used to reference a particular object, field, or component in an application programmatically. It is typically used in backend code, integrations, or API calls. API Names are often system-generated and follow a specific naming convention, such as using underscores instead of spaces (e.g., Customer_Status__c). 

• Label: The Label is the user-friendly name for an object, field, or component that is displayed in the user interface (UI). It is designed to be easily understood by end-users and often includes spaces or capitalization for readability (e.g., "Customer Status"). 

• Add Help Text is the text that will be displayed to the end user to help them understand the label’s meaning. 

• Placeholder: It specifies the name of the field displayed in the system.  

• Default Value: The default value for the component is a pre-populated entry displayed when the form or input field is initially loaded. This value can be either a static text entry or dynamically sourced from a variable.

• Initial Rows: Defines the height of the text area screen component by specifying the number of visible text rows. The specified number in the Initial Rows field applies to the Runner text area as well. If left unspecified, the system defaults to 3 rows.

• Enable Auto Size: When enabled, this option allows the text area to automatically expand in height based on the amount of text entered by the user.

• Mark Field as Mandatory: to mark the field mandate, if the field is not field it will not allow the user to move to the next step. 

• Restricted Keyword Lists: It is a multi-select configuration field. It enables you to assign one or more predefined keyword lists. If your input contains any terms from the selected restricted keyword lists, an error message will be triggered. This message is configurable once you enable Configure Error Messages toggle. This feature helps you maintain better input quality control and enforce compliance or content guidelines dynamically within your workflow.

• Minimum Character Limit: You can set the minimum character limit in the text box, if you are setting it to 10 then the end user has to fill in at least 10 characters to move ahead with the next step 

• Maximum Character Limit: Allow the end user to enter the maximum characters in the text field. 

• Enable Reporting: This allows to specify whether the auto-drafted values in the screen component should be included in reporting. When enabled, this ensures that auto-saved data is captured and made available for analytics, addressing gaps in reporting accuracy caused by un-submitted workflows. 

• Visibility Conditions: is a rule or set of rules that determine whether a specific element, field, or component is visible to users in an application or interface. These conditions are typically based on factors such as field values, or contextual data. Visibility conditions ensure that users only see relevant information, improving usability and security. 

  • Example  

    • Condition: Display a "Priority Escalation" section if the "Ticket Priority" is set to "High."

    • Implementation: Visibility Condition: Ticket_Priority == 'High'

    • Result: The "Priority Escalation" section appears only for high-priority tickets. 

      ​

      ​

• Disability Condition: It refers to a rule or set of criteria that determines whether a specific element, such as a field, button, or component, should be disabled (i.e., grayed out and non-interactive) in a user interface. It restricts user interaction based on certain conditions, ensuring that actions are contextually valid or preventing errors. 

  • Example: 

    • Based on Field Value: 

      • Condition: Disable the "Submit" button if the "Terms and Conditions" checkbox is unchecked. 

      • Result: The user cannot submit the form until they accept the terms.

    • Based on User Role: 

      • Condition: Disable the "Delete Record" button for users without "Admin" permissions. 

      • Result: Only admins can delete records, while other users see the button but cannot interact with it. 

    • Based on Data Completeness: 

      • Condition: Disable the "Next" button until all required fields are filled. 

      • Result: Users are prevented from moving forward until they complete the required steps. 

• Configure Error Message:

  • If the field value is left empty.

  • If the text entered has fewer characters than the minimum character limit.

  • If the text entered has more characters than the maximum character limit.

  • If text entered has restricted keywords.

​