> 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/desktop/iris/checkbox-radio-button/get-status-of-iris.md).

# Get Status of IRIS

This is a pre-built action which comes for the **Captured Checkbox/Radio button Element** from the **Desktop Application** using the **IRIS method**. The functionality of this action in Avo Assure is to fetch the current state of the object and store it in the dynamic variable as **True** or **False** during debugging or execution.

### **Syntax**

**Input Value:** `<status when object scraped – 0/1>`

| Argument                                    | Description                                                                                                   |
| ------------------------------------------- | ------------------------------------------------------------------------------------------------------------- |
| \<status when object scraped – 0>(Required) | Provide scraped status as 0, which indicates that the IRIS object was **selected** at the time it was scraped |
| \<status when object scraped – 1>(Required) | Provide scraped status as 1, which indicates that the IRIS object was **unselected**                          |

**Output Value**

| Argument                                                    | Description                                                                                                                                                       |
| ----------------------------------------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| \<Dynamic Variable>(Optional);\<Dynamic Variable>(Optional) | This variable holds the current status of the object as **True** (If checkbox/radio button is selected) or **False** (If checkbox/radio button is not unselected) |

**Example 1**

**Retrieves the current state of a captured checkbox element using the IRIS method**

The **Get Status of IRIS** action takes the value from the Input Value column **(e.g., 0)**, where 0 represents the expected status of the object when it was initially scraped or captured. It retrieves the current status of the element during execution and compares it with the expected status.

<figure><img src="https://2174257472-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fk8QZzXZMIJSStKAzDSTu%2Fuploads%2FwRxAWG5KOIbPdJEzq9g0%2Fimage.png?alt=media&amp;token=56e6ce54-b4ac-4321-b24c-862922f9efa2" alt=""><figcaption></figcaption></figure>

**Example 2**

**Retrieves the current state of a captured UI element using the IRIS method**

The **Get Status of IRIS** action takes the value from the Input Value column **(e.g., 1)**, where 1 represents the expected status of the object when it was initially scraped or captured. It retrieves the current status of the element during execution as **True.**

<figure><img src="https://2174257472-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fk8QZzXZMIJSStKAzDSTu%2Fuploads%2Fd1fdOHUePy6MgEuxMVxy%2Fimage.png?alt=media&amp;token=b8e411d7-cdd4-497e-a7c6-b1e8073b2f25" 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/desktop/iris/checkbox-radio-button/get-status-of-iris.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.