> 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/custom/page-2.md).

# Page 2

This pre-built Action is located under the @Custom Element. The functionality of this action in Avo Assure is to fetch the column count of the table based on the given input value and stores the result in the output variable. 

**Syntax**

**Input Value:** \<ObjectType>;\<VisibleText(optional)>;\<Index>;\<abs(optional)>

**Note:**

* Ensure that the specified table exists and is accessible before executing the Action.
* The table must be visible and loaded completely for successful execution.

**Input Arguments**

| **Argument**               | **Description**                                                                                                           |
| -------------------------- | ------------------------------------------------------------------------------------------------------------------------- |
| \<ObjectType> **Required** | Specify the type of custom element (table) from which the column count is to be fetched.                                  |
| \<VisibleText> *Optional*  | Specify the visible text of the element, used to identify the target table when multiple elements of the same type exist. |
| \<Index> **Required**      | Specify the index of the element to identify the target table when multiple matching elements exist.                      |
| \<abs> *Optional*          | Specify whether the index should be treated as an absolute position of the element.                                       |

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

| **Argument**                     | **Description**                                       |
| -------------------------------- | ----------------------------------------------------- |
| \<Dynamic Variable> *(Optional)* | Stores the retrieved total column count of the table. |
| \<Dynamic Variable> (Optional)   | Stores the status as True or False.                   |

**Example: Getting the Total Column Count**

**Action:** Get total column Count  \
**Input Value:** table;;0

* table specifies the object type of the custom element.
* 0 specifies the index of the element.

**Output Value:** {Column Count}

If the Action executes successfully:

* {Column Count} stores the actual value of the specified table.
* **True:** The column count is successfully retrieved from the specified table.
* **False:** The Action fails due to an invalid object type, unmatched visible text, incorrect index, non-existent attribute, or the element being inaccessible.

**Logical Explanation**

The Get total column Count Action reads the object type, visible text (if provided), index, and abs flag (if provided) from the Input Value field. During execution, Avo Assure identifies the specified table and fetches the total number of columns present in it. The Action then stores the retrieved count in the specified dynamic variable. \
&#x20;


---

# 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/custom/page-2.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.