RadioList How To's
How to's for the RadioList guide.
How to Use RadioList?
How to Use RadioList?
RadioList is a component that allows multiple options to be listed under a single group.
By following the steps below, you can add a RadioList to your form and define its options.
Adding the RadioList Component to the Form
- Open the form design screen
- Go to the
Toolboxpanel - Locate the
RadioListcomponent - Drag and drop it onto the form
Adding Options (Items)
- Click on the RadioList component
- In the
Property Viewer, find theItemssection - Click the “+” button to add a new option
- Fill in the
TextandValuefields for each optionText→ The label displayed to the userValue→ The value used in processing
Setting a Default Selected Value
- Use the
Selectedproperty to determine which option will be preselected when the form loads.
What Is RadioList?
RadioList – What Is It?
A RadioList is a form component used to group multiple Radio options under a single unified structure.
Normally, you can add multiple Radio controls to a form and manually group them, but RadioList makes this process much more organized, easier to manage, and controllable from a single point.
What Is Its Purpose?
- Combines all related radio options
under one component - Ensures the user can select
only one option - Allows adding, editing, and ordering Radio items from a single panel
- Simplifies the form design and makes it more readable
Usage Scenarios
- Gender selection (Male / Female)
- Payment type selection (Cash / Card / Transfer)
- Delivery method selection
- Product variant selection
- Yes / No preference options
Advantages
| Feature | Description |
|---|---|
Single group management | Manages multiple radio items using one RadioList instead of separate controls |
Easy editing | Options can be quickly added or removed from the panel |
Clean form design | Provides a cleaner and more maintainable form structure |
Guaranteed single selection | Ensures the user can choose only one option |
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:
-
Select the “Signature” fieldin the form editor. -
In the
Propertiespanel, find theClient Enabledfield. -
Set the value to
False— the field will now be disabled by default when the form loads. -
Open the
Rule Manager. -
Add a new rule:
Condition:
Action:
- 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 State | Description |
|---|---|
True | The control is active and ready for user interaction when the form loads. |
False | The control is disabled at load time and can be enabled dynamically via rules or code. |
Notes & Best Practices
- Use the
Client Enabledproperty to manageclient-side interactivitywithout requiring server actions. - Combine it with
Rule Managerto define when and how controls become active. - Remember: if
server enablementis disabled, the client cannot enable the control even ifClient Enabledis set toTrue. - 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.