Skip to main content

Button How To's

How to's for the Button guide.

How to Use Button?​

How to Use Button?​

The following steps describe how to add a Button to a form and configure its click event.

1. Add the Button to the Form​

  1. Open the form design screen.
  2. Go to the Toolbox panel on the right side.
  3. Locate the Button control.
  4. Drag and drop it onto the form.

2. Configure Button Properties​

When the Button is selected, the Property Viewer panel allows you to configure:

  • Text: The label displayed on the button.
  • Icon: An optional icon that can be added to the button.
  • Visible: Controls whether the button is shown on the form.
  • Enabled: Determines whether the button is clickable.

What Is Button?​

What Is Button?​

A Button is an interactive form element used to start an operation, trigger an event, or execute code.
When the end user clicks the button, the background logic associated with it runs and performs the defined action.

For this reason, the Button is one of the most essential action triggers within a form.

Features​

  • Executes code when clicked
  • Used for starting processes such as validation, saving data, or workflow actions
  • Visually customizable (text, icon, visibility, styling, etc.)
  • Can trigger actions on both the client and server side

Usage Areas​

  • CRUD operations such as Save / Update / Delete
  • Opening another process or form
  • Running calculations, validations, or custom logic
  • Guiding user actions within the web interface

The Button is considered the starting point of an action within the form’s logic.

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.