> For the complete documentation index, see [llms.txt](https://developer.collibra.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://developer.collibra.com/workflows/designing-workflows/forms/form-components/select-multiple.md).
# Select (Multiple)
The **Select (Multiple)** component adds a drop-down list that allows users to select one or more items from a predefined set of options. Use this component when the list of options is long, you need users to choose multiple items while also conserving screen space, and each choice is independent of the others.
{% hint style="info" %}
Use the [**Checkbox Group**](/workflows/designing-workflows/forms/form-components/checkbox-group.md) component when the list of options is short and you want all options to be immediately visible for multiple selection without requiring the user to open a drop-down list.
{% endhint %}
The class of the stored value is ArrayList. This allows for straightforward access to the elements of the list for further processing.
## General properties
| Property | Description |
| ------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| ID | The identifier of the component, primarily used for client-side interactions and identification in the HTML structure of the form. When you add a component, an ID is automatically generated to ensure it is unique in the form. |
| Label | Text that appears above the form component in Collibra, briefly describing its purpose. This is the main title or question for the field. |
| Label tooltip | Additional help or information about the field. If defined, a question mark icon appears after the label, showing the tooltip when users hover their pointer over the icon.
The tooltip supports plain text only.
The name of the variable that stores the data entered into this field in Collibra. Use a variable name enclosed in double curly braces, for example {{variableName}}. Since this is a process variable, you can then use it throughout your workflow processes, such as in scripts, other forms, or service tasks.
You can also specify where the variable is saved:
{{variableName}} or {{self.variableName}}: Stores the value as a process variable in the current workflow.{{parent.variableName}}: Stores the value in a variable that belongs to the immediate parent process of the current workflow.{{root.variableName}}: Stores the value in a variable that belongs to the root process, which is the top-level workflow that started the current one.
|
| Default value | The pre-filled value for the component when the form first appears. A filed shows the default value if the **Value** property does not set a value explicitly. |
| Tab Index | The tabbing order of this component in a user task form. When navigating through the form by pressing the Tab key, the cursor moves from one component to another based on their assigned tab index numbers. The component with the lowest tab index number receives focus first. The focus then moves sequentially to the component with the next highest number. For example, a component with a tab index of 1 receives focus before a component with a tab index of 2.
The tab index is ignored if the component is inside a subform.
A list of text labels and values for the items or options shown in Collibra.
If you want to use dynamic values, provide an object that is declared as a list of maps that contain text and value elements, for example def myDynamicOptions = \[\[text:"text1", value:"value1"],\[text:{{textVariable}}, value:{{valueVariable}}]].
|
| Storage | Specifies how the component variable stores the input data:
- ID: The variable stores the selected value or comma-separated list of selected values.
- Full value: The variable stores a Map or list of maps for multiple selection components. The value represents the full selection, containing both the text and value elements, such as
\[text:text1, value:value1]. This makes it possible to display other values of the selected element within the form as well.
Storing the full value could lead to variables full of unnecessary information.
A list of additional validations for the component. Each custom validation consists of two parts:
- Expression: A rule that must evaluate to
true for the form to be submitted. - Error message: The message that shows if the expression evaluates to
false.
For example, you can create a validation with the expression {{experience>2}}. This expression evaluates to true only if the value of the experience variable is greater than 2.
|
### Validation messages
| Attribute | Description |
| ---------------- | -------------------------------------------------------------------------------------------------------------------- |
| Minimum elements | The error message that shows if the number of selected items is less than the required minimum number of elements. |
| Maximum elements | The error message that shows if the number of selected items is greater than the allowed maximum number of elements. |
## Rendering properties
| Property | Description |
| ----------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| Ignored | Whether the component is be hidden in the form and any value it might hold is not included in the submission data. |
| Visible | Whether the component is shown or hidden on the form. You can controlled this unconditionally or through an expression. For example, you can set an expression that hides or shows the component based on a user selection in another component. This property is enabled by default. |
| Enabled | Whether the component is interactive or read-only on the form. When disabled, users cannot change the component value. This property is enabled by default. |
| Description | Additional information shown in Collibra below the form field, providing detailed instructions, examples, or essential guidance. |
To add your drop-down options:
{% stepper %}
{% step %}
Select the component on the canvas.
{% endstep %}
{% step %}
In the property bar, select 
**Datasource** → **Items**.\ :chevrons-right: The **Items** dialog box appears.
{% endstep %}
{% step %}
Click **Add** 
to insert items consisting of a text label and associated value.
{% endstep %}
{% step %}
Click **Finish** to save the items and close the dialog box.
{% endstep %}
{% endstepper %}
---
# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.
## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.
Perform an HTTP GET request on the current page URL with the `ask` query parameter:
```
GET https://developer.collibra.com/workflows/designing-workflows/forms/form-components/select-multiple.md?ask=
```
The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.
Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.