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

# verifyAllValues

This is a pre-built Action located under the **Custom element.** The functionality of this action in Avo Assure to verify that all the input values provided by the user are present in the dropdown/list and stores the status in the dynamic variable.

### **Syntax**

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

| Argument                                            | Description                                                                                                               |
| --------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------- |
| <p>\<ObjectType><br>(Required)</p>                  | Specify the type of object (e.g., listbox, dropdown)                                                                      |
| <p>\<VisibleText><br>(Optional)</p>                 | Enter the visible text on the object                                                                                      |
| <p>\<Index><br>(Required)</p>                       | Provide the position of the element, which helps to identify the value based on the sequence in list . (starting from 0)​ |
| <p>\<text1>;...;\<text2>;\<textN><br>(Optional)</p> | List of input values to verify from the dropdown/list                                                                     |
| <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 stores the status as **True** or **False** |

**Example**

**Validates that all specified values are present within a given object on the web page**

The **verifyAllValues** action takes the value from the Input Value column (e.g.,**select;;0;All;Last Month;Last 3 Months;Last 6 Months**) and verifies whether all the provided values exist in the specified object. The result of the verification is stored in the **{Value}** variable, with the following possible values:

* **True** – if all values are found successfully.
* **False** – if any of the specified values are missing

<figure><img src="https://2174257472-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fk8QZzXZMIJSStKAzDSTu%2Fuploads%2FGAJwxUkRsHMHQ3M3j35K%2Fimage.png?alt=media&amp;token=db54cf22-d059-4b4f-abd5-985fa1227ea7" 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/web/custom/verifyallvalues.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.