> 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/operations/get-pop-up-text.md). # Get Pop Up Text This is a pre-built Action located under the **@Sap Element**. The functionality of this action in Avo Assure is to retrieve the text displayed in a pop-up window of the SAP GUI application and save the result in a dynamic variable. ### Syntax **Input Value:** `(Optional)` | Argument | Description | | --------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | |

(Optional)

Enter the index number of the pop-up to check when multiple pop-ups appear.
Note: The value starts from 0th index (zero).

| **Output Value** | Argument | Description | | ------------------------------------------- | ---------------------------------------------------------- | |

(Required)

| This variable holds the retrieved **pop-up message text.** | |

(Optional)

| This variable stores the status as **True** or **False**. | **Example:** **Retrieving 'Information' Text from a Pop-Up Using the Get Pop-up Text Action** The **Get Pop Up Text** action takes the value from the Input Value column **(e.g., 0)** to specify the index of the pop-up when multiple pop-ups are present. If no index is provided, the default pop-up text is considered. The retrieved text **(e.g., Information)** is stored in the **{PopupText}** variable. **With index value:**

**Without Index Value:**

--- # 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/operations/get-pop-up-text.md?ask=&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.