> For the complete documentation index, see [llms.txt](https://help.novacuraflow.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.novacuraflow.com/6.12/development/flow-studio/applications/workflow/user-step/menu-selection-input.md).

# Menu selection input

A menu selection input is used to select a key field value from a machine task or a table. Menu selection inputs take up less space than list selection inputs, but are less practical for large data sources with lots of information in each record.

Menu selection inputs have the following properties:

* **Target Variable**\
  &#x20;The name of the new variable(s) in which to store the selected value. The data that will be stored in the varibale is the value frpm the seleced variable in "Field to select".
* **Table Variable**\
  &#x20;Choose the table that will be the data source in the list.
* **Prompt**\
  &#x20;The label displayed at the top of the list.
* **Row Text**\
  &#x20;Enter text and variables that should be displayd in the list. Use {} to get a list of available variables from the source table.
* **Default Value**\
  &#x20;Enter a default value based on the values of the variable entered in *Field to Select*.
* **Field to Select**\
  &#x20;The target variable will contain the value of this field.
* **Show Empty Option**\
  &#x20;The list will be empty when the user enter the user step.
* **Text of Empty Option**\
  &#x20;Enter a text for the empty option (optional).
* **Allow Empty Option Selection**\
  &#x20;If set to **True**, the operator is allowed to move forward in the workflow without entering anything into the text field.


---

# 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, and the optional `goal` query parameter:

```
GET https://help.novacuraflow.com/6.12/development/flow-studio/applications/workflow/user-step/menu-selection-input.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.
