# verifyExists

This is a pre-built Action located under the **@Custom Element**. The functionality of this Action in Avo Assure is to verify whether the specified object is present on the web page. The result is stored in the given dynamic variable for further use during test execution.

{% hint style="info" %}
The **verifyExists** action works only when the **VerifyExists** action is executed in a preceding step.
{% endhint %}

## Syntax

**Input Value**: `<ObjectType>;<VisibleText(optional)>;<Index>;<abs(optional)>`&#x20;

| Argument                            | Description                                                                                                                                            |
| ----------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------ |
| <p>\<ObjectType><br>(Required)</p>  | Provide the object type you want to verify for present in the application.                                                                             |
| <p>\<VisibleText><br>(Optional)</p> | Provide the visible text associated with the object.                                                                                                   |
| <p>\<Index><br>(Required)</p>       | <p>Provide the position of the object you want to identify based on its sequence in the application.<br><strong>Note</strong>: Index start from 0.</p> |
| <p>\<abs><br>(Optional)</p>         | Provide the absolute XPath of the object you want to identify for this operation.                                                                      |

{% hint style="info" %}
**Note**:

* If the last argument **abs** is defined, the action executes using absolute identification based on the specified absolute XPath provided in the input.
* To skip an optional input value, use an extra semicolon (;).
  {% endhint %}

**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 1: Verifying Existence of an Object**

In this example, we are explaining how to verify that a specified object exist on the application interface.

* **Action**: verifyExists
* **Input Value**: Button;;0
  * The first argument (Button) specifies the object type to be identified.
  * The second argument is left blank to skip an optional value.
  * The third argument (**0**) specifies the index of the object when multiple matching elements are present.
* **Output Value**: {Status}
  * The result of the verification operation is stored in the **{Status}** dynamic variable with the following possible values:
    * **True**: If the specified object exist on the application interface.
    * **False**: If the specified object does not exists.
* **Logical Explanation**: The **verifyExists** action reads the identification details from the **Input Value** column (**Button;;0**). The action searches for the specified object using the object type and index. If the object is found on the application interface, the verification result is stored as (True) in the **{Status}** variable.

<figure><img src="/files/bmWLXFs7tB8e1if7H0no" alt=""><figcaption></figcaption></figure>

### **Example 2: Verifying Existence of an Object using Optional Parameter**&#x20;

In this example, we are explaining how to verify that a specified object exist on the application interface using optional parameter.

* **Action**: verifyExists
* **Input Value**: Button;Delete;0
  * The first argument (**Button**) specifies the object type to be identified.
  * The second argument (**Delete**) specifies the visible text associated with the object.
  * The third argument (**0**) specifies the index of the object when multiple matching elements are present.
* **Output Value**: {Status}
  * The result of the verification operation is stored in the **{Status}** dynamic variable with the following possible values:
    * **True**: If the specified object exist on the application interface.
    * **False**: If the specified object does not exists.
* **Logical Explanation**: The **verifyExists** action reads the identification details from the **Input Value** column (**Button;Delete;0**). The action searches for the specified object using the object type, visible text, and index. If the object is found on the application interface, the verification result is stored as (True) in the **{Status}** variable.

<figure><img src="/files/6pVAIDH5lticycGWIz9r" alt=""><figcaption></figcaption></figure>


---

# Agent Instructions: 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:

```
GET https://docs.avoautomation.com/avo-assure/actions/web/custom-1/verifyexists.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.