> 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-1/simulate-mouse-click.md).

# Simulate Mouse Click

This is a pre-built Action located under the captured table element. The functionality of this Action in Avo Assure is to perform a mouse click on the specified cell provided in the input value for the table object. The result is stored in the given dynamic variable for further use during test execution.

## Syntax

**Input Value**: `<Row>;<col>`

| Argument                    | Description                                                    |
| --------------------------- | -------------------------------------------------------------- |
| <p>\<Row><br>(Required)</p> | Provide the row number of the table cell you want to click.    |
| <p>\<col><br>(Required)</p> | Provide the column number of the table cell you want to click. |

**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: Simulating a Mouse Click on a Specific Table Cell**

In this example, we explain how to perform a simulated mouse click operation on a particular cell in a table.

* **Action**: Simulate Mouse Click
* **Input Value**: 4;3
  * The first argument (**4**) specifies the row number.
  * The second argument (**3**) specifies the column number.
* **Output Value**: {Status}
  * The outcome of the mouse click action is stored in the **{Status}** dynamic variable, with the following possible values:
    * **True**: If the mouse click operation is preformed successfully.
    * **False**: If the mouse click operation is not preformed successfully.
* **Logical Explanation**: The **Simulate Mouse Click** action reads the value from the **Input Value** column (**4;3**). It identifies the table cell at row 4 and column 3 and performs a simulated mouse click on that cell. The result of this interaction (**True**) is stored in the **{Status}** variable.

<figure><img src="https://2174257472-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fk8QZzXZMIJSStKAzDSTu%2Fuploads%2FINemtfVmSUGZSPHHUqHU%2Fimage.png?alt=media&amp;token=e0b21ee2-050a-441d-9c47-0a0eb1723577" 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.avoautomation.com/avo-assure/actions/web/table-1/simulate-mouse-click.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.