> 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/table-operations/get-cell-status.md).
# Get Cell Status
This is a pre-built action available under the **Captured Table Element** from **SAP GUI Application**. This functionality of this action in Avo Assure to fetch the status of the radio button/checkbox in the table cell and save the status in dynamic variable.
### **Syntax**
**Input Value:** ``
{% hint style="warning" %}
***Note:** The index value starts from **1.***
{% endhint %}
| Argument | Description |
| --------------------------------- | -------------------------------------------------------------------------- |
|
\ (Required)
| Specify the row index of the cell containing the checkbox/radio button. |
|
\
(Required)
| Specify the column index of the cell containing the checkbox/radio button. |
#### Output Value
| Argument | Description |
| ----------------------------------------------------------- | -------------------------------------------------------------------------------------- |
| \(Optional);\(Optional) | This dynamic variable holds the checkbox/radio button status as **True** or **False**. |
**Example**
**Retrieves the status information of a specific cell from a table based on the parameter**
The **Get Cell Status** action takes the value from the Input Value column **(e.g., 3;4)** and identifies the status **(e.g., selected)** of the given cell. The result of the cell status is stored in the **{CellStatus}** variable.
---
# 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/table-operations/get-cell-status.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.
