> 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/sap/tree-control-operations/verify-tree-path.md).

# Verify Tree Path

This is a pre-built action available under the **Captured Tree Element** from the **SAP GUI Application**. The functionality of this action in Avo Assure is to verify if the specified node path exists within the hierarchical tree structure.

### Syntax

**Input Value:** `<Path1>;<Path2>;…;<PathN>;<>;<Column Data>(optional)>`

| Argument                                | Description                                                                                                    |
| --------------------------------------- | -------------------------------------------------------------------------------------------------------------- |
| \<Path1>;\<Path2>;…;\<PathN> (Required) | Provide the hierarchical path of the tree node, with each level separated by a semicolon.                      |
| <> (Optional)                           | <p>Leave this as blank.<br><em><strong>Note:</strong> This is used when optional values are provided.</em></p> |
| \<ColumnData> (Optional)                | Enter the column data value.                                                                                   |

**Output Value**

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

**Example 1**

**Verifies whether a specified path exists in the tree structure**

The **VerifyTreePath** action takes the value from the Input Value column **(e.g., Workbench Demos;Controls;Tree Controls;SAP Column Tree)** and checks if the specified path exists in the tree. The verification result is stored in the **{Verify Path}** variable **True** (if the path exists) or **False** (if the path does not exist).

<figure><img src="/files/Sg00MtegOZPVkStzHgxk" alt=""><figcaption></figcaption></figure>

**Example 2**\
**Verifies whether a specific tree path exists in the SAP GUI tree structure**

The **VerifyTreePath** action takes the node path from the Input Value column **(e.g., Workbench Demos;Controls;Tree Controls;SAP Column Tree;<>;SAP Column Tree Column Tree)** and checks if the specified path exists in the tree. The result of the verification is stored in the **{Verify Path}** variable as **True** (if the path exists) or **False** (if the path does not exist).

<figure><img src="/files/cyptCwHeIKsNz9ZUC6QH" 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/sap/tree-control-operations/verify-tree-path.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.