- Getting started
- Best practices
- Writing effective prompts
- Designing Autopilot-relevant automations
- Autopilot for developers
- Autopilot for testers
- Autopilot for testers
- Quality-check requirements
- Generate tests for requirement
- Import manual test cases
- Generate tests for SAP transactions
- Generate coded automations
- Generate coded API automation
- Refactor coded automations
- Generate low-code automations
- Generate synthetic test data
- Generate test insights reports
- Search Test Manager project
- Autopilot for Everyone
- Autopilot plug-ins
- Data privacy
Designing Autopilot-relevant automations
This page is targeted for automation developers, and guides them through the best practices on building automations which are optimized for Autopilot.
Autopilot can recommend and execute automations based on the user query. It also infers argument values to help setting up the automation. For these reasons, out-of-the-box automations have additional configurations and best practices to help facilitate Autopilot features.
To build automations that can be leveraged later by Autopilot for Everyone , we suggest the following best practices:
Project best practices |
---|
|
Input argument best practices |
---|
|
Output argument best practices |
---|
|
Exception handling best practices |
---|
|
To use existing automations in Autopilot, make sure they adhere to the previously mentioned design considerations.
Autopilot recommends automations solely based on the descriptions you provide. For Autopilot to suggest the correct automation, make sure each automation has distinct descriptions, to minimize overlaps. Autopilot can also infer argument values needed for the automation, simplifying the process and reducing the need for you to understand all the details. During setup, be sure to provide clear arguments. When you run the automation, Autopilot infers the argument values from the conversation or asks for additional details.
A set of metadata properties assist Autopilot in understanding various aspects such as:
-
What the automation does
-
How the automation card is displayed
-
How to infer the argument values
-
How the automation should be run
-
Any necessary context before executing the automation
Learn how to configure Automation properties.
Autopilot chat sessions have a limited capacity for information. Therefore, when building data-heavy automations, such as retrieval tasks, make sure to return only the relevant data.
To do this, consider the following:
-
Include arguments in the automation for filtering purposes. For instance, if you retrieve events from Outlook, add arguments that could allow filtering the results by the subject or attendees.
-
Create two automations:
-
One automation to return multiple objects with limited details, and
-
One automation to return extensive details for a single object.
-
The template UiPath provides has several design-specific recommendations already applied. To use the template, access it from UiPath Marketplace > Studio > Templates page.
After designing the automation, make sure to:
-
Publish the package to the tenant where Autopilot is installed.
-
Create and deploy the corresponding process to a folder where the required users have access.
-
Configure the automation properties.