Skip to main content

Switch How To's

How to's for the Switch guide.

How to Use Switch?​

How to Use Switch?​

The following steps should be followed to add and configure the Switch object on a form.

Add the Switch Object to the Form​

  1. Open the form design screen
  2. Go to the Toolbox panel
  3. Locate the Switch object
  4. Add the object to the form using drag / drop

Configure General Properties​

  1. Click the Switch object
  2. The Property Viewer panel opens on the right
  3. In the General tab, configure the following settings:
    • Caption (Title)
    • Default value (On / Off)
    • Visibility (Visible)
    • Enabled state (Enabled)

Define the Default State​

  • If you want the switch to start as on → True
  • If you want it to start as off → False

This setting determines the initial state of the switch when the form is first opened.

Usage with Rules and Events​

The Switch value can be:

  • Controlled via Rule Manager
  • Read within Events
  • Used to affect the visibility or mandatory state of other form objects

Example Scenario​

If the switch is on, show an additional field; if it is off, hide it.

Data Saving Behavior​

  • The Switch value is saved as a boolean in the form data
  • It is processed as true / false
  • It can be used directly in backend logic or process steps

Tips​

  • For on/off logic, using Switch instead of Checkbox is recommended from a UX perspective
  • Do not use Switch for scenarios with many options
  • The label (Caption) should be short and clear

Summary​

With the Switch object:

  • A clear decision is collected from the user
  • The form becomes simpler and more modern
  • Boolean-based business rules can be applied easily

What Is Switch?​

What Is Switch?​

Switch is a form object used to allow the user to select only one of two options.
It typically represents boolean (true/false) values and offers a more modern and intuitive appearance compared to a Checkbox in terms of user interaction.

The Switch object visually and clearly indicates whether a state is on / off.

What Is It Used For?​

  • Yes / No selections
  • Active / Passive state control
  • True / False decision fields
  • Feature enable / disable scenarios
  • System settings and configurations

Key Features​

  • Single selection (two states)
  • Works with boolean data structure
  • Easily controlled with form rules and events
  • Simple and clear from a user experience (UX) perspective

Usage Scenarios​

  • “Are Notifications Active?”
  • “Is Approval Required?”
  • “Is the User Passive?”
  • “Should Mobile Signature Be Used?”

Notes​

  • Switch is not suitable for multiple selection.
  • If more than two options are required, Radio, Dropdown, or ComboBox should be preferred.

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.