> 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/working-with-the-avo-assure-platform/create-and-execute-tests-with-design-studio/working-with-element-repository-section/custom-property.md).

# Custom Property

### Overview 

Avo Assure supports automation for web applications by using built-in properties to identify on-screen elements. In addition to the eight default properties (e.g., Id, Attribute Name, Class Attribute), two extra fields- Custom 1 and Custom 2 are available for added flexibility.  

These fields are useful when the application uses unique attributes (e.g., data-testid, maxlength) that are not part of the standard set, enabling more reliable element identification even when default properties vary. 

{% hint style="warning" %}
***Note:** Custom 1 and Custom 2 only work for **web applications.*** 
{% endhint %}

### Custom 1 – Standard Unique Identifier Property 

**Custom 1** allows users to define a **unique element property** that is consistently used across the application. This is particularly useful when developers implement a unique attribute (e.g., data-testid, custom-id, etc.) throughout the application to help with element identification. 

* This custom property acts as a replacement or extension of the default properties. 
* It ensures that the automation scripts remain robust and maintainable by relying on a developer-defined, consistent element identifier. 

### Custom 2 – Manual Unique Identifier 

**Custom 2** gives users the **flexibility to manually assign** a unique or alternate identifier for an element.

* This can be helpful in scenarios where the standard properties and *Custom 1* do not provide sufficient identification.
* Users can input any attribute or identifier that reliably distinguishes the element in the current context.

**Manual Attribute Update Syntax**

When updating a custom attribute manually in the **Custom Property** settings page, please use the following syntax format:

`tagname[attributename="attributevalue"]`


---

# 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/working-with-the-avo-assure-platform/create-and-execute-tests-with-design-studio/working-with-element-repository-section/custom-property.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.