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

# verifyValuesExists

This is a pre-built action in Avo Assure and is available for the **@Custom Element.** The functionality of this action in Avo Assure to verify if the input values provided by the user are present in the dropdown or list specified in the input and save the result in the dynamic variable.

### Syntax

**Input Value:**`<ObjectType>;<VisibleText (optional)>;<Index>;<text1>;<text2>…etc;<abs (optional)>`

| Argument                            | Description                                                                                                    |
| ----------------------------------- | -------------------------------------------------------------------------------------------------------------- |
| <p>\<ObjectType><br>(Required)</p>  | Provide the object type to be verified (e.g., select, label, textbox)                                          |
| <p>\<VisibleText><br>(Optional)</p> | Enter the visible text on the object                                                                           |
| <p>\<Index><br>(Required)</p>       | Provide the Index of the object (e.g., 0, 1)                                                                   |
| <p>\<text1><br>(Required)</p>       | Specify the text to be verified in the object                                                                  |
| <p>\<text2><br>(Required)</p>       | Specify the text to be verified in the object                                                                  |
| <p>abs<br>(Optional)</p>            | If the **abs** is provided, the action is performed with absolute identification using the **absolute X path** |

{% hint style="warning" %}
**Note:** *To skip an optional input value, use an extra semicolon (;).*
{% endhint %}

**Output Value:**

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

**Example**&#x20;

**Verifies the presence of specified values within an object on the application**

The **verifyValuesExists** action takes the value from the Input Value column (e.g., **dropdown;;0;All;Last Month;Last 3 Months**) and checks whether the given values exist within the targeted object. The result of the verification is stored in the **{Verify Exists}** variable, with the following possible values:

* **True** – if all specified values are found within the object.
* **False** – if one or more values are missing or an error occurs.

<figure><img src="/files/7etG0ZPap6UIvwedyBb2" 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/custom/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.