> 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/create-element-repository/capturing-elements-in-avo-assure/capturing-desktop-elements.md).
# Capturing Desktop Elements
Capturing desktop elements allows you to identify and store UI elements from desktop applications in the Element Repository. These elements are used while designing and executing automated test scenarios in Avo Assure. This topic describes how to capture the desktop elements using the Avo Assure Client.
## Prerequisites
* Ensure that the target desktop application is installed on your system.
* Ensure that the Avo Assure Client is connected.
## Capturing Elements from Desktop Applications
To capture desktop elements, perform the following actions:
1. On the **Home** page, under **Projects**, select the required Project.
2. Select **Design Studio**.
3. On the **Element Repository** page, select the **Create Folder** (**+**) icon.
4. Select **Create main folder** to create a new element repository folder. A new folder appears.
5. In the **New Folder** text box, enter the element repository folder name.
6. In the newly created folder, select the Ellipsis (**...**) icon next to the folder name, and then select **Create Repository** > **Desktop**. The desktop element repository is created.
7. Select **Capture Elements**. The **Avo Assure Client – Capture** window opens.
8. In **Step 1: Enter Window Name/Process ID** box, enter the window name or process ID of the desktop application.
9. Select **Launch**. The specified desktop application is launched.
10. In **Step 2: Capture Element**, select an element capture method.\
The following capture methods are available:
| Capture Method | Description |
| -------------- | ----------------------------------------------------------------------- |
| Visible | Captures visible elements in the AUT. |
|
| |
| All | |
|
| Captures all elements in the AUT, including hidden elements. |
| Manual | |
|
| Allows you to manually navigate to AUT and capture elements. |
| IRIS | Captures elements based on screen coordinates and positions in the AUT. |
Configuring Capture Settings
* **Capture Type**: Select the specific element types to capture.
* **Method**:
* **UI/UIA**: Use for modern applications that support Microsoft UI Automation. This method identifies elements with standard UI structures.\
**Note**: Use the UI method by default. If it does not work, use UIA.
* **Win32**: Use for legacy applications that do not fully support UI Automation. This method uses Windows API-based identification.
* **Option**: Select the type of capture option.
11. Select **Capture** to start the element capturing process.
12. Select **Add**. The selected elements are added to the element repository.
{% hint style="info" %}
**Note**:
* Select **Locate** to highlight the corresponding elements in the application UI.
* Select **Delete** to remove the selected elements from the capture list.
{% 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/create-element-repository/capturing-elements-in-avo-assure/capturing-desktop-elements.md?ask=&goal=
```
`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.