> 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/common-iris-keywords/drop-iris.md). # Drop IRIS This is a pre-built action which comes under the element captured from the Desktop AUT using IRIS method. It instructs the Avo Assure Client to drop IRIS object which is captured from desktop application and save the result in output variable as ‘True’ or ‘False’. ### Syntax  **Input:** `N/A` **Output:** `;(Optional)`
### **Usecase/Example**
### **Scenario:** Simulate Drop Action to Move Files in Desktop File Management Application. Consider a scenario where a desktop file management application is being automated for testing, requiring files to be dropped from one folder to another. With the help of the **Drop IRIS** action, the drop action is simulated to ensure that files are successfully moved between folders. ### Expected Result This Action need to drop file in folder. ### **Output** The **Drop IRIS** successfully performed, and output stored in {Status} variable as True --- # 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/desktop/iris/common-iris-keywords/drop-iris.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.