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

# Get Object Status

This is a pre-built Action located under the Table captured from the AUT Element, instructs the Avo Assure to retrieve the status of the objects like radio button or checkbox which is present in the cell of the table and save it in the dynamic variable.

{% hint style="warning" %}
For the object, it may retrieve the following statuses:

* **Checked:** if the radio button or checkboxes are already checked
* **Unchecked:** if the radio button or checkboxes are already unchecked
  {% endhint %}

### Syntax

**Input Value:** `<Row>;<Column>;<ObjectType>;<Index>`

| Argument                           | Description                                                            |
| ---------------------------------- | ---------------------------------------------------------------------- |
| <p>\<Row><br>(Required)</p>        | Specify the row number of the table cell to be checked                 |
| <p>\<Column><br>(Required)</p>     | Specify the column number of the table cell                            |
| <p>\<ObjectType><br>(Required)</p> | Type of object inside the cell. Must be either radiobutton or checkbox |
| <p>\<Index><br>(Required)</p>      | Index of the object inside the cell (starting from 0)                  |

**Output Value**

| Argument                                 | Description                                                              |
| ---------------------------------------- | ------------------------------------------------------------------------ |
| <p>\<Dynamic Variable><br>(Required)</p> | This dynamic variable holds the retrieved status as Checked or Unchecked |
| <p>\<Dynamic Variable><br>(Optional)</p> | This variable save the result in the **True** or **False**               |

**Example**

**Retrieves the status of a radio button or checkbox from a specific cell in the table.**

The **Get Object Status** action takes the value from the Input Value column (e.g., **2;5;radiobutton;1**) and checks the current status of the specified object (radio button or checkbox) in the given row and column of the table. The result is stored in the **{StatusResult}** variable and the execution status is saved in the **{Status}** variable with the following possible values:

* **True** - if the objects status retrieved successfully
* **False** - if the object status not retrieved

<figure><img src="https://2174257472-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fk8QZzXZMIJSStKAzDSTu%2Fuploads%2FrsGiZ8DzE6lTmgYtYXiz%2Fimage.png?alt=media&amp;token=e9c8c6e1-6e7f-4581-b0aa-85eb7a4b1a62" 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/table/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.