> For the complete documentation index, see [llms.txt](https://docs.novacura.com/flow-connect/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.novacura.com/flow-connect/reference/how-to-guides/create-user-step-controls/menu-selection-input.md).

# Menu selection input

## Prerequisite data

No connectors will be used in this example, but data from table steps will be utilized. Please download the file below; it will be used to import into the required table steps

{% file src="/files/4deMzQ91meLeuOaLdMGC" %}

## Add a menu selection input

1. Open an existing [application ](https://docs.novacura.com/flow-connect/working-with-connect/create-and-design/applications/create#create-application)or create a new one in an [application package](https://docs.novacura.com/flow-connect/working-with-connect/create-and-design/application-packages) and open it in the Designer.
   1. Add a User step. 
   2. Add a Table step.
   3. Open the Table step and select **Import File**.
   4. Choose the semicolon separator and click **OK**.
   5. Select the "List selection.csv" file downloaded in the prerequisite section above.
   6. Set the table variable name to "Articles" and click **OK**.
   7. Change the step name to "Articles". It's good practice to name steps after their content.
   8. Right-click on the "Articles" step, select **Add data arrow**, and connect it to the User step created in step 1.

<figure><img src="/files/7YoEtYwSemXrNWwN8cp0" alt=""><figcaption></figcaption></figure>

2. Open the User step.
   1. Add a Menu Selection input.&#x20;
   2. In the Target Variable, write "article".
   3. Under Data Source, in Table Variable, choose the table "Articles".
   4. Under Appearance, in Prompt, write "Choose an article".
   5. In Large Row Text, write "{Name}".
   6. Under behaviour, set the Field to Select to "{Name}".
3. Click the **Play** button in the top right-hand corner to run the application in diagnostic mode.

<figure><img src="/files/AtipqDHll0Adxuj2HvvX" alt=""><figcaption><p>The Large Row Text shows the articles names. The table is displayed in a drop down menu.</p></figcaption></figure>

<figure><img src="/files/PUnDx0T540Dh7Q9e7qnK" alt=""><figcaption><p>All articles displayed.</p></figcaption></figure>

## Add configuration

The Menu selection input enforces a selection by not giving an empty option. If you wish to leave the variable empty, you need to add an Empty Option.

2. Go back to the Designer.

   1. Under the Empty Option section, check the "Show Empty Option" checkbox.
   2. Set the Text of Empty Option to "Not applicable".
   3. Check the "Allow Empty Option Selection" checkbox.&#x20;
   4. Run the application in diagnostic mode again.

   <figure><img src="/files/QLt3BNZyfuofSLYLD14H" alt=""><figcaption><p>There is now a Not applicable option, allowing the user to not choose one of the articles to move forward.</p></figcaption></figure>

3. You can also set a default value to display the value you wish to highlight.
   1. Under Behaviour, in Default Value, write "{"Small box"}".
   2. Click the **Play** button in the top right-hand corner to run the application in diagnostic mode.

<figure><img src="/files/NXFmNEXhI9MRjh49ggro" alt=""><figcaption><p>The small box is now shown as chosen value. </p></figcaption></figure>

3. Condition to hide&#x20;
   1. In the Condition To Hide, write “{userId = “*your user id”*} *(the user Id you log in to Connect with)*
   2. Run the application in diagnostic mode again.

<figure><img src="/files/mppUkxzWDnuGCzC7vKo8" alt=""><figcaption><p>The list is now hidden since the condition is fulfilled.</p></figcaption></figure>


---

# 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://docs.novacura.com/flow-connect/reference/how-to-guides/create-user-step-controls/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.