Skip to main content

ComboBox How To's

How to's for the ComboBox guide.

How to Use a ComboBox?

How to Use a ComboBox?

Follow the steps below to add and configure a ComboBox in form design:

1. Add the Object to the Form

  • Locate the ComboBox object in the Toolbox panel.
  • Drag and drop it onto the form.

2. Configure Its Properties

When you click the ComboBox object, the Property Viewer panel appears.

General Tab

  • General
  • Label
  • Data Source
  • Behavior
  • Appearance

Events Tab

You can configure the following events:

  • On Value Changed
  • On Load
  • On SelectedItemChanged

3. Save and Test

After saving the form and running the preview, the ComboBox will be ready for use.


What Is a ComboBox?

What Is a ComboBox?

A ComboBox is a form object that presents a list of values—either retrieved from a data source or manually defined by the developer—and allows the user to make a single selection from that list.

This object is frequently used in form design and can work with both static and dynamic data.

Purpose of the ComboBox

  • Allows the user to choose from predefined options
  • Displays values retrieved from a data source
  • Provides a controlled data entry interface within the form
  • Supports both static (manually added) and dynamic (DataSource) option lists

Where Is It Used?

  • Department selection
  • Status selection (Active / Passive)
  • Lists such as country, city, category
  • Data-driven selection scenarios

Accessing Properties

In the development interface, the ComboBox object:

  1. Is added to the form by dragging it from the Toolbox panel
  2. When clicked, the Property Viewer panel displays General , Label ,Data Source, Behavior , Appearance and Events tabs
  3. All configurations can be made from these sections

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.