TextArea How To's

How to's for the TextArea guide.

How to Use TextArea?

How to Use TextArea?

TextArea is used to add a multi-line text input area to a form.
The steps below explain how to place the component on a form and configure its properties.

1. How to Add a TextArea Component?

1. Open the form design screen.
2. Go to the Toolbox panel on the left side.
3. Find the TextArea component.
4. Drag and drop it onto the form.

2. Configuring Properties

When the TextArea is selected, the General and Events tabs appear in the right-side panel.

You can configure the following settings:

Property	Description
Text	Field label
Placeholder	Helper text that guides the user
Required	Marks the field as mandatory
ReadOnly / Disabled	Controls editability
Rows	Number of lines initially displayed
Max Length	Maximum number of characters allowed

3. Common Use Cases

• Description / comment fields
• Problem or request explanations
• Address information
• Long-text input fields
• Forms where detailed user input is required

4. Tips

• Use Placeholder to help explain the purpose of the field.
• If very long text is expected, configure a Max Length value.
• Adjust Height / Rows to optimize layout and readability.

---

What Is TextArea?

What Is TextArea?

TextArea is a form component that allows users to enter long and multi-line text.
It serves a similar purpose to a TextBox; however, TextArea is preferred when the text content is longer and needs to be displayed across multiple lines, making it ideal for broader text entry scenarios.

What Is It Used For?

• Description fields
• Notes or comments
• Address information
• Any text input requiring multiple lines
• Any form scenario that requires a large text entry area

Usage in the Development Interface

When the form design screen is active:

1. The TextArea component is listed in the Toolbox panel.
2. Drag and drop the component onto the form.
3. When selected, the Property Viewer panel displays the General and Events tabs.
4. All component properties can be configured through this panel.

2. Editable Core Properties

Property	Description
Text	The label text displayed to the user.
Visible	Determines whether the component is visible on the form.
Width / Height	Defines the width and height of the TextArea field.
Horizontal Align	Aligns the label text to the left, right, or center.
Enable Multilanguage Text	Enables multi-language text input. When activated, a multi-language button appears, allowing users to enter values in multiple languages.
Rows	Specifies the initial height of the TextArea in rows. For example, if the value is set to 5, the component loads with a height that displays 5 rows. This size can also be adjusted manually using the resize handle on the corner of the component.

Advantages

• Provides a user-friendly way to enter long text inputs.
• Multi-line support makes large text entries easier to read.
• Automatic text wrapping keeps the content visually organized.

---

How to Use Client Enabled?

What is Client Enabled?

Client Enabled is a property that defines whether a form control is active (enabled) on the client side when the form is first loaded.
If it is set to True, the control is immediately usable by the user.
If it is set to False, the control is disabled and cannot be interacted with until a specific condition or rule activates it.

This property is especially useful for controlling the user’s interaction flow and applying dynamic behaviors using the Rule Manager.

What Does It Do?

The property allows developers to:

• Control when a form control becomes interactive.
• Prevent users from entering or changing data until prerequisites are met.
• Dynamically enable or disable controls based on user input or logic.

Example Scenario — Conditional Activation

Scenario:
A form contains a checkbox called “I Accept Terms” and a text field called “Signature.”
The goal is to make the “Signature” field inactive until the user checks “I Accept Terms.”

Steps to Implement:

1. Select the “Signature” field in the form editor.

2. In the Properties panel, find the Client Enabled field.

3. Set the value to False — the field will now be disabled by default when the form loads.

4. Open the Rule Manager.

5. Add a new rule:

   Condition:

Action:

6. Save and publish the form.

Result:

• When the form loads, the “Signature” field is disabled.
• Once the user checks “I Accept Terms,” the field automatically becomes active and editable.

Behavior Summary

Property State	Description
True	The control is active and ready for user interaction when the form loads.
False	The control is disabled at load time and can be enabled dynamically via rules or code.

Notes & Best Practices

• Use the Client Enabled property to manage client-side interactivity without requiring server actions.
• Combine it with Rule Manager to define when and how controls become active.
• Remember: if server enablement is disabled, the client cannot enable the control even if Client Enabled is set to True.
• By default, this property is set to True (active).

Summary

Client Enabled improves form usability by letting developers control when and how users interact with form controls.
It is essential for creating responsive, condition-based form experiences where user actions dynamically change the form’s state.