> 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/desktop/iris/textbox/set-text-iris.md).

# Set Text IRIS

This is a pre-built action which comes for the element captured from the Desktop AUT using IRIS method. It instructs the Avo Assure Client to set the input text to the captured IRIS textbox.

### Syntax

**Input:** `<input value>`

**Output:** `<Dynamic Variable>(Optional);<Dynamic Variable>(Optional)`

<figure><img src="https://2174257472-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fk8QZzXZMIJSStKAzDSTu%2Fuploads%2FWYPMppUKarI9CUNpKYrj%2Fimage.png?alt=media&amp;token=dd5a4a5a-b9af-47c7-a391-100a8c0ab1e7" alt=""><figcaption></figcaption></figure>

### **Usecase/Example**

<figure><img src="https://2174257472-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fk8QZzXZMIJSStKAzDSTu%2Fuploads%2FX8NmcUjnId6QRu9j5o48%2Fimage.png?alt=media&amp;token=652b542a-a7d9-4fd2-a0f6-0b3b48cd67db" alt=""><figcaption></figcaption></figure>

### **Scenario:** The Set Text IRIS action inputs valid username credentials in the login form.

The scenario involves testing a desktop-based login form for an application. The form has username field. The Avo Assure is to execute the Test Step of entering valid login credentials. The Set Text IRIS action is used to input the username into the textbox on the login page.

### Input

Username: testuser

### Expected Result

The action needs to enter the input Text to the username field.

### Output

The Set Text IRIS Action enters testuser Input Value.


---

# 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/desktop/iris/textbox/set-text-iris.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.
