> 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/button-operations/verify-button-name.md).

# Verify Button Name

This is a pre-built action available under the **Captured Button Element** from the **SAP GUI Application.** The functionality of this action in Avo Assure is to verify whether the button name provided in the input matches the actual button name in the SAP application.

### Syntax

**Input Value:** `<Button Name>`

| Argument       | Description                                     |
| -------------- | ----------------------------------------------- |
| \<Button Name> | Provide the expected button name to be verified |

**Output Value**

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

**Example**

**Verifying if the Button Name is "Execute F8" on the application**

The **Verify Button Name** action takes the value from the Input Value column **(e.g., Execute F8)** and checks whether the captured button’s name matches the expected name. The result of the action is stored in the **{VerifyBtnName}** variable as **True** (if the name matches) or **False** (if the name does not match).

<figure><img src="/files/gHxfjYzZiYc1iwIHXQzA" 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/button-operations/verify-button-name.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.