> For the complete documentation index, see [llms.txt](https://docs.wem.io/platform/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.wem.io/platform/wemtipsandtricks/widgets/advanced-input/multi-select-input-button.md).
# Multi select input button
The Multi-Select Input Button Widget allows users to choose multiple options from a set of interactive buttons. With its intuitive design and flexible functionality, it provides an efficient solution for interaction nodes that managing filters with a lot of options.
### Properties
| Property | Type | Description |
| ----------------- | -------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| Data field | datafield, single select concept | The concept that holds the options information. It displays the selected options and all other options allowing the user to make options selected or unselected. |
| Filter | boolean, expression | Can be used to filter the options (concepts). |
| On change | dropdown | When the user clicks on a button to either select or unselect that option, the following actions can be performed: do nothing, refresh screen or execute flowchart. |
| Execute flowchart | flowchart | Execute the provided flowchart when the user clicks on one of the options. Only visible when 'On change ' is set to 'Execute flowchart'. |
| Orientation | dropdown | Display the buttons either horizontal or vertical. |
| Label | text, expression | Changes the button text. By default it displays the concept's name. |
| Badge | number, expression | Display a number immediately after the button label. Example 1 shows a random number after each label. |
| Justified | dropdown, boolean | Make the buttons as wide as possible. Only visible when using a horizontal orientation. |
---
# 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 by asking a question.
Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:
```
GET https://docs.wem.io/platform/wemtipsandtricks/widgets/advanced-input/multi-select-input-button.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.
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.
.gif?alt=media&token=c50673cd-fa58-4dfa-bef4-de906d4271d7)