> 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/element/double-click-on-object.md).

# Double Click on Object

This is a pre-built Action located under the captured element. The functionality of this Action in Avo Assure is to perform a double-click operation on the specified captured element within the application. The result is stored in a dynamic variable for further use during test execution.

## Syntax

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

| Argument | Description    |
| -------- | -------------- |
| N/A      | Not Applicable |

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

| Argument                                                      | Description                                                       |
| ------------------------------------------------------------- | ----------------------------------------------------------------- |
| \<Dynamic Variable> (Optional);\<Dynamic Variable> (Optional) | Both dynamic variable stores the status as **True** or **False**. |

### **Example: Performing a Double-Click on a UI Element**

In this example, we explain how to simulate a double-click on a specified object using the Double Click action.

* **Action**: Double Click on Object
* **Input Value**: N/A
  * This action does not require any input value. It identifies the target object and performs a double click operation.
* **Output Value**: {Status}
  * The result of the double click operation is stored in this **{Status}** dynamic variable with the following possible values:
    * **True**: If the double click action is performed successfully.
    * **False**: If the double click action is not performed successfully.
* **Logical Explanation**: The **Double Click on Object** action does not require any input value. It identifies the specified UI element and performs a double click on it. The outcome of this operation (**True**) is stores in the **{Status}** variable.

<figure><img src="https://2174257472-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fk8QZzXZMIJSStKAzDSTu%2Fuploads%2FqXYF3RqOPYCmeOFKjS7f%2Fimage.png?alt=media&amp;token=08a93304-dee1-4d63-b103-8ee4e92a819e" 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/element/double-click-on-object.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.