Skip to main content

TagBox How To's

How to's for the TagBox guide.

What Is TagBox?

What Is TagBox?

TagBox is a form component that presents values—either retrieved from a data source or defined manually by the developer—in a list format and allows users to make multiple selections from that list.

Each selected value is displayed as a tag in the interface. Users can remove selected tags individually or clear all selections at once.

What Is It Used For?

TagBox is commonly used in the following scenarios:

  • Selecting multiple categories
  • Assigning multiple roles to a user
  • Tag-based classifications
  • Defining multiple relationships for a single record
  • Filtering and search-based selections

TagBox vs Other Selection Components

ComponentSelection TypeDisplay
ComboBoxSingleList
DropdownSingleDrop-down list
TagBoxMultipleTags
ListBoxSingle / MultipleList

Key Features

  • Supports multiple selection
  • Tag-based visual representation
  • Supports data sources and manual data entry
  • Built-in search and filtering
  • Suitable for dynamic data scenarios

Notes

  • TagBox is preferred over ComboBox when multiple selection is required.
  • For very large data sets, using a Lookup component is recommended.
  • From a user experience perspective, tag-based visualization makes multi-selection clearer and more intuitive.

How to Use TagBox?

How to Use TagBox?

Follow the steps below to add and configure the TagBox component on a form.

Add TagBox to the Form

  1. Open the form designer.
  2. Go to the Toolbox panel.
  3. Find the TagBox component.
  4. Drag and drop it onto the form.

Configure General Properties

When you select the component, the Property Viewer displays the relevant tabs.

General Tab

You can configure the following settings:

  • Text → The title shown to the user
  • Data Source → The data source used for the list
  • Name → The value to be stored/saved
  • Allow Clear → Allows clearing selected values
  • Show Search → Enables searching within the list

Define the Data Source

TagBox can be used in two ways:

Bind to a Data Source

  • Select a data source in the Data Source field
  • Set the Display and Value fields

Define Items Manually

  • Add static items manually
  • Suitable for small and fixed lists

Use Multi-Selection

  • The user can select multiple values from the list
  • Each selected value is displayed as a tag
  • Tags can be removed one by one

Use with Events

From the Events tab, you can:

  • Run actions when the selection changes
  • Update other fields based on selected values
  • Define conditional behaviors using Rule Manager

Use Cases

  • Assigning multiple roles to a user
  • Selecting multiple categories for a record
  • Tagging systems
  • Filtering and reporting scenarios

Notes

  • For very large data sets, Lookup is recommended
  • For better user experience, keep search enabled
  • TagBox is ideal when multi-selection is required to maintain data consistency

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:

  1. 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 StateDescription
TrueThe control is active and ready for user interaction when the form loads.
FalseThe 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.