> 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/checkbox/get-object-status.md).

# Get Object Status

This is a pre-built Action located under the **@Captured Checkbox Element**. The functionality of this Action in **Avo Assure** is to verify whether the specified checkbox is selected or not within the application and stores the result in a dynamic variable for further use during test execution.

## Syntax

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

<table><thead><tr><th>Argument</th><th>Description</th><th data-hidden></th></tr></thead><tbody><tr><td>N/A</td><td>Not Applicable</td><td></td></tr></tbody></table>

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

<table><thead><tr><th>Argument</th><th>Description</th><th data-hidden></th></tr></thead><tbody><tr><td>&#x3C;Dynamic Variable>(Required)</td><td>This Dynamic Variable stores the Checkbox status (e.g., Unselected or Selected).</td><td></td></tr><tr><td>&#x3C;Dynamic Variable>(Optional)</td><td>This Dynamic Variable stores the status as <strong>True</strong> or <strong>False</strong>.</td><td></td></tr></tbody></table>

### **Example: Retrieving the Status of a Checkbox Object**

In this example, we explain how to use the **Get Object Status** action to retrieve the current state of a specified checkbox during test execution.

* **Action**: Get Object Status
* **Input Value**: N/A
  * This action does not require any input value. It directly checks the current status of the targeted checkbox object.
* **Output Value**: {Get Status}
  * The retrieved button status (e.g., Selected or Unselected) is stored in this **{Get Status}** dynamic variable.
  * If a second output variable is provided, the action returns the status as True/False:
    * **True**: If the checkbox status is retrieved successfully.
    * **False**: If the checkbox status is not retrieved successfully.
* **Logical Explanation**: The **Get Object Status** action evaluates the status of the specified checkbox object and retrieves its current status as selected or unselected and stores in the **{Get Status}** variable.

<figure><img src="https://2174257472-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fk8QZzXZMIJSStKAzDSTu%2Fuploads%2Fa75ZoSHPVw5xjDSug3sE%2Fimage.png?alt=media&amp;token=55c078be-d3c7-4355-bd39-e9475d3ab0ae" 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/checkbox/get-object-status.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.