> 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/web/common-web-operations/verifyhidden.md).

# VerifyHidden

This is a pre-built Action located under the captured element. The functionality of this action in Avo Assure is to verify if the captured object is hidden in the application. The result is stored in the given dynamic variable for further use during test execution.

## **Syntax**

**Input Value**: `N/A`

| Argument | Description    |
| -------- | -------------- |
| N/A      | Not Applicable |

**Output Value**: `<Dynamic Variable>(Optional);<Dynamic Variable>(Optional)`

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

### **Example: Checking Whether a UI Element Is Hidden**

In this example, we are explaining how to verify whether a captured UI element is hidden on the screen.

* **Action**: verifyHidden
* **Input Value**: N/A
  * This action does not require any input value. It verifies whether the captured UI element is hidden within the application.
* **Output Value**: {Status}
  * The verification result is stored in the **{Status}** dynamic variable with the following possible values:
    * **True**: If the UI element is hidden.
    * **False**: If the UI element is visible on screen.
* **Logical Explanation**: The **verifyHidden** action does not require any input value. The action checks the visibility state of the captured UI element in the application under test and determines whether it is hidden. The verification result (**True**) is stored in the **{Status}** variable.

<figure><img src="https://2174257472-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fk8QZzXZMIJSStKAzDSTu%2Fuploads%2FC9mEPZKdXbtQH8uzPagj%2Funknown.png?alt=media&amp;token=45878978-4d81-43c6-8a66-499f8218dbcc" 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/web/common-web-operations/verifyhidden.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.