> 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/get-input-help.md).

# Get Input Help

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 fetch the input help (such as suggestions or list options) for a textbox or input and save the result in the dynamic variable.

### **Syntax**

**Input Value:** `<(optional)Row;Column>`

{% hint style="warning" %}
***Note:** If no row and column are specified in the Input Value, the action will retrieve the default or first input help entry available for the element.*
{% endhint %}

| Argument               | Description                                                                                                |
| ---------------------- | ---------------------------------------------------------------------------------------------------------- |
| <(optional)Row;Column> | Enter the row and column number of the input help entry to be retrieved (if specific position is required) |

**Output Value**

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

**Example** 1

**Fetches input help suggestions for a textbox Without optional input value**

The **Get Input Help** action does not require any value from the Input Value column. It retrieves the input help suggestion (such as a dropdown or suggestion list) for the specified textbox.

<figure><img src="https://2174257472-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fk8QZzXZMIJSStKAzDSTu%2Fuploads%2F0uF6m0y0ddAbEueiq1B8%2Fimage.png?alt=media&amp;token=f598e683-00f4-4816-9e8f-8778f6072066" alt=""><figcaption></figcaption></figure>

**Example** **2**

**Fetches input help suggestions for a textbox using optional input value**

The **Get Input Help** action takes the value from the Input Value column **(e.g., 1;2)**. It retrieves the input help suggestion (such as a dropdown or suggestion list) for the specified textbox.

<figure><img src="https://2174257472-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fk8QZzXZMIJSStKAzDSTu%2Fuploads%2Fw5pO8bFUmMDvlakc3IIM%2Fimage.png?alt=media&amp;token=c1818808-45ec-4d79-a786-4380b12d1e8e" 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/get-input-help.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.