> 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/sap/common-operations/verify-exists.md).

# Verify Exists

This is a pre-built action available under the **Captured Element** from the **SAP GUI Application**. The functionality of this action in Avo Assure is to verify the element present on the page. It verifies the presence of the captured element.

### **Syntax**

**Input Value:** `N/A`

| Argument | Description    |
| -------- | -------------- |
| N/A      | Not Applicable |

**Output Value**

| Argument                                                    | Description                                                                                |
| ----------------------------------------------------------- | ------------------------------------------------------------------------------------------ |
| \<Dynamic Variable>(Optional);\<Dynamic Variable>(Optional) | This variable holds the result as **True** (if element exists) or **False** (if not found) |

**Example**

**Verifying if a Button Exists on the SAP Screen**

The **Verify Exists** action does not require any value from the Input Value column. It checks whether the captured button or UI element exists on the SAP screen. The result of the action is stored in the **{Btn Status}** variable as **True** (if the element exists) or **False** (if the element does not exist).

{% hint style="warning" %}
***Note:** The particular element is highlighted in red color on the SAP application to indicate its presence.*
{% endhint %}

<figure><img src="/files/6cF5D7EosGq2dumoFjWp" 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/sap/common-operations/verify-exists.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.