> 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.11/development/flow-portal-2/getting-started/settings/list-of-value-management.md).
# List of values management
Users can specify a drop-down list of pre-defined values for both Table and Filter portlets. This pre-defined list is called a list of values. When used, the list of values will limit what a user can enter in a specific field.
To add a new list of values, go to *Settings* then *Lists of Values*. Click the *Manage* button.
Click the + icon to add a new list of values, then select the data source:
* Database: add name, connector and select statement.
* Workflow: create a workflow with output and connect it to the list of values using the drop-down list. The workflow can also be created and connected directly from the list of values by clicking New - Add a name - Create.
Click *execute,* add the text and value columns, then save.
* Text column: the value which will be shown in the drop down when using the list of values.
* Value column: the value which will be sent as the filter value
To edit an existing list of values, just click on the list of values in question and edit.
---
# 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://help.novacuraflow.com/6.11/development/flow-portal-2/getting-started/settings/list-of-value-management.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.
