> 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/unselect-checkbox.md).

# Unselect Checkbox

This is a pre-built Action located under the captured checkbox element. The functionality of this Action in Avo Assure is to uncheck or clear the selection of a specified checkbox within the application and stores the result in a dynamic variable for further use during test execution.

{% hint style="info" %}
**Note**: Make sure that the checkbox should already selected.
{% endhint %}

## 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>(Optional);<Dynamic Variable>(Optional)`

<table><thead><tr><th>Argument</th><th>Description</th><th data-hidden></th></tr></thead><tbody><tr><td>&#x3C;Dynamic Variable>(Optional);&#x3C;Dynamic Variable>(Optional)</td><td>Both Dynamic Variable holds the status as <strong>True</strong> or <strong>False</strong>.</td><td></td></tr></tbody></table>

### **Example: Unselecting a Checkbox Element**

In this example, we explain how to use the **Unselect Checkbox** action to unselect a specific checkbox element within the application.

* **Action**: Unselect Checkbox
* **Input Value**: N/A
  * This action does not require any input value. It directly interacts with the targeted checkbox element to perform the unselecting operation.
* **Output Value**: {Status}
  * The result of the unselecting operation is stored in this **{Status}** dynamic variable with the following possible values:
    * **True**: If the checkbox is unselected successfully.
    * **False**: If the checkbox is not unselected successfully.
* **Logical Explanation**: The **Unselect Checkbox** action identifies the targeted checkbox object and performs the uncheck operation during execution, ensuring that the checkbox is unchecked before proceeding to the next step. The result is store in the **{Status}** variable as true.

<figure><img src="https://2174257472-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fk8QZzXZMIJSStKAzDSTu%2Fuploads%2FecRvBgnjdwDGumufCmNE%2Fimage.png?alt=media&amp;token=d6f1a8c6-d67f-4c0f-bb9e-02f052d6b578" 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/unselect-checkbox.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.