Skip to main content
Radio field in the UI Designer

Configuring the radio field element

Radio generic settings

These allow you to customize the generic settings for the Radio element:

Process data key

Process data key establishes the binding between the radio element and process data, enabling its later use in decisions, business rules or integrations.

Properties

  • Label: The visible label for the radio element.
  • Helpertext: Additional information about the radio element, which can be optionally hidden within an infopoint.

Datasource configuration

  • Default value: Autoselect an option from the radio element based on this value. You need to specify the value from the value/label pairs defined in the Datasource tab.
  • Source Type: The source can be Static, Enumeration, or Process Data.
  • Value key and Label key (Process Data only): the paths read inside each item of the array, for items that don’t use value and label. Use dots for nested fields, for example city.code and city.name. Leave a key empty to read value or label. The field stores the value it reads at the value key. An item whose value at that key is missing, an object, or a list is left out of the options.
  • Options → Add new (+): Define label and value pairs here.

Validators

The following validators can be added to a radio: required, customExpression and custom. For more information, see the validators documentation.

Hide/disable expressions

The radio’s element behavior can be defined using JavaScript expressions for hiding or disabling the element. The following properties can be configured for expressions:
  • Hide condition: A JavaScript expression that hides the Radio element when it returns a truthy value.
  • Disable condition: A JavaScript expression that disables the Radio element when it returns a truthy value.
It’s important to make sure that disabled fields have the same expression configured under the path expressions → hide.
Radio field hide and disable expressions

Event handlers

Event handlers can be added to the radio element to define its behavior and interactions.
  • Trigger: On change (CHANGE).
  • Action Type: Select the type of the action to be performed.
For more information, see the Event Handlers documentation.

Radio settings overrides

There are instances where you may need to tailor settings configured in the Generic settings tab. This proves especially beneficial when you wish to adjust these settings to appear differently across various platforms such as Web, Android, or iOS. Available override settings:
  • Properties:
    • Label: Override the radio label.
    • Helper: Override helper text/info point.
  • Expressions:
    • Hide: Override the hide expression.
Overrides can always be imported/pushed from one platform to another:

Radio styling

  • Type: Set the type of the radio. Possible values:
    • bordered
    • clear

Radio style overrides options

Theme overrides refer to the ability to modify or customize the appearance and behavior of UI components by overriding default theme settings. This can be applied at various levels, such as specific elements or entire sections, and can be platform-specific (Web, iOS, Android).
Radio Theme overrides section in the Styles tab with every override category added
Style options:
  • Border radius [NUMBER]
  • Font [FONT]
  • Default state
    • Text [COLOR]
  • Disabled state
    • Text [COLOR]
  • Font [FONT]
  • Text [COLOR]
  • Font [FONT]
  • Helper tooltip
    • Font [FONT]
    • Text [COLOR]
    • Background [COLOR]
    • Icon [COLOR]
  • Text [COLOR]
  • Font [FONT]
  • Background [COLOR]
  • Text [COLOR]
  • Icon [COLOR]
  • Background [COLOR]
  • Text [COLOR]
  • Icon [COLOR]
  • Background [COLOR]
  • Text [COLOR]
  • Icon [COLOR]
  • Background [COLOR]
  • Text [COLOR]
  • Icon [COLOR]
  • Background [COLOR]
  • Text [COLOR]
  • Icon [COLOR]
  • Background [COLOR]
  • Text [COLOR]
  • Icon [COLOR]
Border color and border width are not in the Theme overrides menu. Set them in the Border section of the Styles tab.
You can import or push the overrides from one platform to another without having to configure them multiple times.
Last modified on November 9, 2026