> 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/textbox-operations/verify-textbox-length.md).

# Verify Textbox Length

This is a pre-built action available under the **Captured Textbox Element** from the **SAP GUI Application**. The functionality of this action in Avo Assure is to verify whether the length (number of characters) of the text present in the textbox matches the length specified in the Input Value.

### **Syntax**

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

| Argument                                        | Description                                                                                                            |
| ----------------------------------------------- | ---------------------------------------------------------------------------------------------------------------------- |
| <p>\<value to be verified></p><p>(Required)</p> | Provide the length (numeric value) of the text that must match the actual length of the textbox text. For example, 12. |

**Output Value**

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

**Example**

**Verifying the Textbox Length on the SAP Screen**

The **Verify Textbox Length** action takes the value from the Input Value column as **12** and checks whether the length of the text present in the captured textbox matches the number specified in the Input Value. The result of the action is stored in the **{VerifyLength}** variable as **True** (if the length matches) or **False** (if the length does not match).

<figure><img src="https://2174257472-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fk8QZzXZMIJSStKAzDSTu%2Fuploads%2Fd81I8aI7gjjgMaqKwjb4%2Fimage.png?alt=media&amp;token=92bd65dc-74a4-4cb8-b33e-7b3ace10be13" 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.avoautomation.com/avo-assure/actions/sap/textbox-operations/verify-textbox-length.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.