> 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/table-operations/verify-text-exists.md).

# Verify Text Exists

This is a pre-built action available under the **Captured Table Element** from **SAP GUI Application**. The functionality of this action in Avo Assure to verify if the text given in the input is present in the table and save the result in dynamic variable.

### **Syntax**

**Input Value:** `<value to be verified>`

| Argument                                     | Description                                              |
| -------------------------------------------- | -------------------------------------------------------- |
| <p>\<value to be verified><br>(Required)</p> | Specify the input value to be verified within the table. |

**Output Value:**

| Argument                                                    | Description                                                                    |
| ----------------------------------------------------------- | ------------------------------------------------------------------------------ |
| \<Dynamic variable>(Optional);\<Dynamic variable>(Optional) | This dynamic variable holds the result of this action as **Ture** or **False** |

**Example**

**Verifies the existence of a specific text on the application page**.

The **Verify Text Exists** action takes the value from the Input Value column **(e.g., Transaction)** and checks whether the specified text is present table. The result of the verification is stored in the **{Verifytext}** variable as **True** (if the text is found) or **False** (if the text is not found).

<figure><img src="/files/jY0K8t0cUjdQzC86vWmS" 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/table-operations/verify-text-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.