Skip to main content

Radio How To's

How to's for the Radio guide.

How to Use Radio?​

Radio – How to Use It?​

Radio is a form control that allows the user to select only one option among multiple choices.
It is especially preferred in single-selection scenarios such as yes/no, male/female, payment type, shipping method, etc.

How to Add a Radio Control to a Form?​

  1. Open the form design screen and go to the Toolbox panel.
  2. Locate the Radio control among the available objects.
  3. Drag and drop it onto the form.
  4. When selected, the Property Viewer panel appears on the right, displaying the General , Label, Behavior, Appearance and Events tabs.

How to Define Options for a Radio Control?​

  1. Select the Radio control.
  2. Go to the Items / Options section.
  3. For each option, add the Value and Text fields:
    • Value: The value saved into the form data model
    • Text: The label displayed to the user

Example:

  • Value: 1, Text: Male
  • Value: 2, Text: Female

Handling Radio Selection Changes (Events)​

Actions that should run when the Radio value changes can be added from the Events tab.

Most common event:

  • On Value Changed → Triggered when the user changes the selected option.

Example usage:
Show/hide another field, update form calculations, make an API call, etc.

Usage Scenarios​

✔ Survey questions
✔ Payment type selection
✔ Gender selection
✔ Branch / delivery type settings
✔ Single-option approval steps

Notes​

  • The Radio control is not suitable for multiple selections; use CheckBox or ListBox for that purpose.
  • Radio buttons can be grouped to create multiple independent single-choice sets.
  • It enhances both usability and accessibility in form design.

What Is RadioButton?​

What Is a RadioButton?​

A RadioButton is used in web interfaces to present multiple options to the user, ensuring that only one option can be selected at a time.

This component is commonly used in scenarios such as:

  • “Yes / No”
  • “Female / Male”
  • “Credit Card / Bank Transfer / Cash on Delivery”
  • “Day / Month / Year”

where mutually exclusive choices are required.

Usage in the Development Environment​

When designing a form:

  1. Drag and drop the RadioButton control from the Toolbox onto the form.

  2. Once selected, the Property Viewer displays:

    • General
    • Events

    where the component’s properties can be configured.

What Does It Do?​

A RadioButton:

  • Forces the user to make only one selection
  • Makes decision points in forms more clear and understandable
  • Is easy to use in business logic (workflow, rule manager)
  • Allows triggering different processes depending on the selected option

Where Is It Used?​

  • Product selection screens
  • Payment method selection
  • User confirmation steps
  • System settings
  • Survey questions

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.