> 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/create-and-execute-tests-with-design-studio/working-with-element-repository-section/features-in-element-repository/element-identifier-order/understanding-element-identifier-and-attributes.md).

# Understanding Element Identifier and Attributes

Every User Interface element has one or more attributes, such as ID, Name, or XPath, that help identify it. In Avo Assure, these attributes are stored as element identifiers and used to locate the element during test execution. You can configure the Element Identifier Order to define the [priority](/avo-assure/create-and-execute-tests-with-design-studio/working-with-element-repository-section/features-in-element-repository/element-identifier-order/reorder-element-and-element-properties-in-repository.md) in which these identifiers are used, improving element recognition and execution reliability.

## Element Identifiers for Web Application

For web application automation, Avo Assure supports the following element identifiers to locate and interact with UI elements during test execution.

* **CSS Selector**: Identifies an element using CSS selector syntax based on its attributes or hierarchy.
* **ID Attribute**: Identifies an element using its unique ID attribute.
* **Absolute X-Path**: Locates an element using its complete path from the root of the Document Object Model.
* **Relative X-Path**: Locates an element using a flexible path relative to other elements in the Document Object Model.
* **Name Attribute**: Identifies an element using its name attribute.
* **Classname Attribute**: Identifies an element using its class attribute.
* **Href Attribute**: Identifies a hyperlink using its href (destination URL) attribute.
* **Label**: Identifies an element using its associated label or displayed text.
* **Custom 1** and **Custom 2**: Identifies an element using user-defined custom attributes for specific application requirements.

## Element Identifiers for Desktop Application

For desktop application automation, Avo Assure identifies elements using a combination of properties to ensure reliable element recognition. The desktop-specific properties map to the element identifiers as follows:

* **Class Name → Absolute XPath**: Identifies an element based on its underlying control class in the desktop application.
* **Control Type → Relative XPath**: Identifies an element by its control type, such as Button, Text Box, or Check Box.
* **Automation ID → ID Attribute**: Identifies an element using its unique automation identifier assigned by the application.
* **Control Name → Name Attribute**: Identifies an element using its displayed or assigned control name.

{% hint style="info" %}
**Note:** **Control Type** typically remains constant. For reliable element identification, Avo Assure requires at least two additional properties that are unique and stable, such as **Automation ID**, **Control Name**, or **Class Name**. This combination helps accurately locate elements during test execution.
{% endhint %}

## Element Identifiers for SAP Application

For SAP application automation, Avo Assure uses the following SAP-specific attributes to identify and locate elements during test execution. These attributes capture the element's hierarchy and position within the SAP user interface, enabling accurate element recognition.

* **Absolute X-path**: Identifies an SAP element using its complete path within the SAP UI hierarchy.
* **Top**: Specifies the vertical position of the element relative to the top of its parent window or container.
* **Left**: Specifies the horizontal position of the element relative to the left side of its parent window or container.
* **Width**: Specifies the width of the element in pixels.
* **Height**: Specifies the height of the element in pixels.

{% hint style="info" %}
**Note**: **Mainframe** and **APIs** applications do not use element identifiers. Therefore, the Element Identifier Order feature is not applicable to these application types.
{% endhint %}


---

# 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/create-and-execute-tests-with-design-studio/working-with-element-repository-section/features-in-element-repository/element-identifier-order/understanding-element-identifier-and-attributes.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.