> 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/web/dropdown/verifyvaluesexists.md).

# VerifyValuesExists

This is a pre-built Action located under the captured dropdown element. The functionality of this action in Avo Assure is to verify whether the input value exists in the dropdown. The result is stored in the given dynamic variable for further use during test execution

### **Syntax**

**Input Value:** `<Text1>;<Text2>;..etc.`

| Argument                                      | Description                                                                                                                                               |
| --------------------------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------- |
| <p>\<Text1>;\<Text2>;..,etc<br>(Required)</p> | <p>Provide the first value you want to verify for its presence.</p><p><strong>Note</strong>: Each text value must be separated using a semicolon (;).</p> |

**Output Value**: `<Dynamic Variable>(Optional);<Dynamic Variable>(Optional)`

| Argument                                                    | Description                                                       |
| ----------------------------------------------------------- | ----------------------------------------------------------------- |
| \<Dynamic Variable>(Optional);\<Dynamic Variable>(Optional) | Both dynamic variable stores the status as **True** or **False**. |

#### **Example: Verifying that Specified Values Exist in a Dropdown**

In this example, we explain how to verify whether all specified values exist within the captured dropdown element.

* **Action**: Verify Value Exists
* **Input Value**: All;Last Month;Last 3 Months;Last 6 Months
  * The first argument (**All**) specifies the first expected value to be checked in the dropdown.
  * The second argument (**Last Month**) specifies the next value that must be present in the dropdown options.
  * The third argument (**Last 3 Months**) specifies another value that must be available in the dropdown.
  * The fourth argument (**Last 6 Months**) specifies the final value that must also be present in the dropdown.
* **Output Value**: {Status}
  * The verification result is stored in the **{Status}** dynamic variable with the following possible values:
    * **True**: If all specified values exist in the dropdown.
    * **False**: If all specified values is not exist in the dropdown.
* **Logical Explanation**: The **verifyValueExists** action takes the values from the **Input Value** column (**All; Last Month; Last 3 Months; Last 6 Months**). The action checks the captured dropdown element and verifies whether each expected value is present among the available options. It validates every value individually to ensure accuracy and completeness. The result of the verification (**True**) is stored in the **{Status}** variable.

<figure><img src="/files/UnKiVoKwjtC1mAxYIxwe" 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 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.avoautomation.com/avo-assure/actions/web/dropdown/verifyvaluesexists.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.