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

# Verify Element Text

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 whether the visible text of the selected element matches the expected value provided in the input value and save the result in the dynamic variable.

### Syntax

**Input Value:** `<Input Text>`

| Argument                 | Description                                                            |
| ------------------------ | ---------------------------------------------------------------------- |
| \<Input Text> (Required) | The expected text value to be matched against the actual element text. |

**Output Value**

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

**Example**

**Verifies** **the Text 'ABAP Editor: Initial Screen' on the SAP Application**

The **Verify Element Text** action takes the value from the Input Value column **(e.g., ABAP Editor: Initial Screen)** and checks whether the visible text of the captured element matches the provided input. The result of the verification is stored in the **{Verify Text}** variable as **True** (if the text matches) or **False** (if the text does not match).

<figure><img src="/files/8bpUEaGH7GSAmjjYrjpC" 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/element-operations/verify-element-text.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.