# Radio group - RadioGroup

Single-choice value group

<figure><img src="https://2112972046-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F2CssJT0zIo4SJQLbSZ6l%2Fuploads%2FgZEe3wgHQssACFLonHLT%2Fimage.png?alt=media&#x26;token=4b13f033-7c15-4359-81ac-0455bf3dfa03" alt=""><figcaption></figcaption></figure>

## Component properties

| Eximee Designer property                                                                              | Attribute name in Source | Description                                                                                                                                                                                                                                                                      |
| ----------------------------------------------------------------------------------------------------- | ------------------------ | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| <p><strong>Title</strong><br>(section <strong>Basic properties</strong>)</p>                          | title                    | Title of the radio group. The availability of this functionality depends on the license and may not be available in all deployments.                                                                                                                                             |
| <p><strong>Graphical representation of the component</strong><br>(section <strong>Other</strong>)</p> | presentation             | Graphical representation of the component (for value selection **STANDARD** and **SELECT**). The value **STANDARD** defines the standard appearance of the component. The availability of this functionality depends on the license and may not be available in all deployments. |

## Internal components

Inside the component **Radio group** two types of components can be embedded: **Text** (text labels) and **Radio** (single-choice components). The way components are arranged inside **Radio group** can be specified using a layout, similarly to the arrangement of components on a page or in a section.

{% hint style="warning" %}
Note! a dynamic Radio group always has a single-column layout.
{% endhint %}

## Component input parameters

| Parameter | Description                                                                                                                             |
| --------- | --------------------------------------------------------------------------------------------------------------------------------------- |
| **value** | The value selected field takes **Radio**.                                                                                               |
| **text**  | Text label of the field **Radio**. It is possible to refer to variables or fields, e.g.: *${sessionVariableName}* or *${GesTextField1}* |

## Populating from an external data source

The component **Radio group** can be populated with data from an external data source.

* For a source of type **SERVICE** - you can, for example, choose a service that displays formatted text and an image from the TextContent artifact in the radio; to do this, use the service **TextContentService**.
* For a source of type **DICTIONARY** - all rows will be translated into fields **Radio** and arranged according to the layout **GridLayout**, each field **Radio** in the next row.

<figure><img src="https://2112972046-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F2CssJT0zIo4SJQLbSZ6l%2Fuploads%2FQvnfbzlCmEM5xG07InAm%2Fimage.png?alt=media&#x26;token=5a401946-58b5-426e-bc42-586de953fd2f" alt=""><figcaption><p align="center"><em><strong>Illustration 1.</strong> Appearance of the component in the application</em></p></figcaption></figure>

{% hint style="info" %}
Demo application: demoRadioGroup
{% endhint %}

{% hint style="info" %}
♿WCAG: [WCAG best practices for low-code dev](https://docs.eximee.com/documentation/documentation-en/budowanie-aplikacji/proces-biznesowy/tworzenie-procesu-biznesowego-w-bpmn-2.0/dobre-praktyki)
{% endhint %}