> For the complete documentation index, see [llms.txt](https://docs.avoautomation.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.avoautomation.com/avo-assure/actions/desktop/dropdown/verify-value-exists.md).

# Verify value exists

This is a pre-built action available under the **Captured Dropdown Element** from the **Desktop Application**. The functionality of this action in Avo Assure is to verify if the input value(s) provided by the user is/are present in the dropdown, and save the result in dynamic variable.

### Syntax

**Input Value:** `<value1>;<value2>;…etc`

| Argument                                          | Description                                                                                                                                                                                                   |
| ------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| <p>\<value1>;\<value2>;..etc</p><p>(Required)</p> | <p>Specify the text values to verify their presence in the dropdown list.</p><p>Additional values can also be provided (optional).</p><p><strong>Note:</strong> Separate each value using a semicolon (;)</p> |

{% hint style="warning" %}
***Note:*** This action will pass only if the input value matches with value present in the dropdown.
{% endhint %}

**Output Value:**

| Argument                                                    | Description                                                                    |
| ----------------------------------------------------------- | ------------------------------------------------------------------------------ |
| \<Dynamic Variable>(Optional);\<Dynamic Variable>(Optional) | This dynamic variable holds the status of the action as **True** or **False.** |

**Example**

**Verifies whether the specified values exist in the dropdown list**

The **Verify Value Exists** action takes the values from the **Input Value** column (e.g.,**All;Last Month;Last 3 Months;Last 6 Months**) and checks whether each of the specified values is present in the dropdown list. The result of the verification is stored in the **{Verify}** variable as **True** (if all the provided values are found in the dropdown) or **False** (if any of the values is missing)

<figure><img src="https://2174257472-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fk8QZzXZMIJSStKAzDSTu%2Fuploads%2FH2YNcNY3L0bKpgpzxXcN%2Fimage.png?alt=media&amp;token=ab3cb44f-5efa-4238-9f1d-406484432667" alt=""><figcaption></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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.avoautomation.com/avo-assure/actions/desktop/dropdown/verify-value-exists.md?ask=<question>&goal=<user_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.