> 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-cell/simulate-press-action.md).

# Simulate Press Action

This is a pre-built Action located under the captured table cell element. The functionality of this Action in Avo Assure is to perform a simulate press operation on the specified captured table cell. The result is stored in the given 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)`

<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 stores the status as <strong>True</strong> or <strong>False</strong>.</td><td></td></tr></tbody></table>

### **Example: Performing a Simulated Press Action on a Table Cell**

In this example, we explain how to simulate a press action on a specific cell in a table.

* **Action:** Simulate Press Action
* **Input Value:** N/A
  * This action does not require any input value. It directly interacts with the captured table cell and performs a simulated press operation.
* **Output Value:** {Status}
  * The result of the press action is stored in the **{Status}** dynamic variable, with the following possible values:
    * **True**: If the captured cell is pressed successfully.
    * **False**: If the captured cell is not pressed successfully.
* **Logical Explanation**: The **Simulate Press Action** does not require any input value. It identifies the captured table cell and performs a simulate press action. The result of this action (**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%2F0wtSLv0ffhU8zkVK8H2q%2Funknown.png?alt=media&amp;token=3b7aba3f-0286-470f-b188-c9e8b98967b7" 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/table-cell/simulate-press-action.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.