> For the complete documentation index, see [llms.txt](https://docs.pixiebrix.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.pixiebrix.com/integrations/automation-anywhere/enhancing-aari-forms.md).
# Enhancing AARI Forms
Enhancing AARI Forms within the Control Room
## FAQs
### How do I control which AARI requests my mods runs on?
AARI uses a URL routing approach called “hash” routing. The AARI path/request appears after the `#` in the URL.
Therefore, to control which mods/AARI pages the mod runs on use a Sites rule with an Advanced: Match Rules > URL Patterns rule
The Sites for your mod could contain the root AARI URL:
```
https://[[Control Room URL]]/aari/*
```
Example:
In the URL Patterns, fill the hash with the URL pattern. In AARI, the request reference follows the pattern *processId*-**runId.**
Therefore to match all runs of a given process, provide a regular expression pattern for the reference:
### How do I control which AARI task my mod runs on?
AARI does not encode the active task in the URL. Therefore, to restrict an mod to a particular task, you have to check the page content.
{% hint style="warning" %}
**This approach must be combined with a trigger to detect task initialization, because PixieBrix may perform the check before the task list elements have been rendered on the page.**
{% endhint %}
This approach must be combined with a trigger to detect task initialization, because PixieBrix may perform the check before the task list elements have been rendered on the page.
To restrict an mod to when a particular task is selected, use the Advanced: Match Rules > Selectors configuration
For example, to restrict by task name, where *Task Name* is the name of the task
`.task-list--selected .task-list__details-title:contains("Task Name")`
---
# 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.pixiebrix.com/integrations/automation-anywhere/enhancing-aari-forms.md?ask=&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.