- Release notes
- Getting started
- For administrators
- Designing automations
- Creating an automation from an idea
- Creating a project
- How to start an automation
- Managing project files and folders
- Connecting automations to your accounts
- Configuring activities
- Managing the activities in a project
- Passing values between activities
- Iterating through items
- Managing the data in a project
- Configuring a project to use your data
- Using file and folder resources
- Debugging banner notification after extension upgrade to Manifest V3
- Autopilot Recorder for UI Automation
- Running and testing your projects
- Managing automations
- Web app projects - Preview
- Studio Web API
Autopilot Recorder for UI Automation
Autopilot Recorder for UI Automation is an AI-powered tool which aims to significantly accelerate and simplify the process of scaffolding basic UI Automation sequences.
You can create UI Automation sequences using the Recorder both by generating activities via a natural language prompt and by manually adding them.
There is no support for adding loops of conditional logic. The Recorder can only handle a pre-defined list of basic UI Automation activities.
Extract Data Table is not supported yet.
Once you have created the desired sequence, simply select Save. The activities needed to perform the sequence are then populated in your Studio Web workflow canvas.
To access the Autopilot Recorder for UI Automation, follow these steps:
- Open an existing Studio Web project or create a new one.
- In the workflow, add a Use Browser activity.
- Under Work in scope, select a tab to automate from the drop-down menu.
- Select the Generate the UI
automation activities using Autopilot icon from the top right corner of
the informative screenshot box or the Generate button. The
Generate button is visible only when there are no activities inside
the Use Browser activity.
- The Recorder is now open.
To generate activities via text prompt in the Recorder, follow these steps:
- Select the plus button.
-
Proceed with either step a or b. Regardless of the choice, the outcome is the same.
-
- Select the Generate with Autopilot option from the list. This creates a placeholder activity card.
- Write a text
prompt in the Describe your actions on this page text
field, then press the
Enter
key or select the arrow symbol. A prompt is most effective if it precisely describes the task at hand. This could include instructions such as "create a new supplier" or "create a time off request between 25 and 30 December", instead of a generic instruction like "click the 'new' button".
- Write a text prompt
in the search box, then press the
Enter
key or select the Generate with Autopilot option.
-
- The activities are now
generated from the prompt. The Recorder uses only the following UI
Automation activities to generate sequences:
- Click
- Type Into
- Get Text
- Select Item
- Check/Uncheck
- The generated activities are
populated in the Recorder. To transition to the next application state,
select the Test button. The Test button is a one-click
default-configured execution attempt with the sole purpose of helping you
transition to the next application state so that you can continue
scaffolding your automation.
- You have transitioned to the
next application state. Executed activities are marked with a green
checkmark. If, for some reason, the Test default-configured
best-effort execution attempt fails, you can still interact with the
application freely to manually execute the necessary steps. If the prompt is
not covered in its entirety, select the Continue 'prompt'
button.
- A new activity has been added
in the Recorder. To transition to the next application state, select the
Test button.
- You have transitioned to the
next application state. You can use the Continue 'prompt' and
Test alternatively until you reach the desired application state
and the entire prompt is covered.
To manually add an activity in the Recorder, follow these steps:
- Select the plus button.
- Choose one of the following UI Automation activities from the list:
- Click
- Type Into
- Get Text
- Select Item
- Check/Uncheck
- Hover
- Keyboard Shortcuts
- Take Screenshot
- Get Attribute
- Mouse Scroll
- Check Element
- Indicate a target by selecting a UI element on the screen.
- Indicate an anchor by selecting a nearby UI element that helps to uniquely identify the target.
- Select Confirm.
- The activity is now added in the Recorder.
Options | Description |
---|---|
Generate button | Opens the Recorder. You can also select the Generate the UI automation activities using Autopilot icon from the top right corner of the informative screenshot box. |
Plus button | Opens the search bar and the drop-down activity list. |
Activity card | You can perform the following:
|
Activity card hamburger menu | This contains the following options:
|
Test button | Executes all generated activities. This is a default
configuration execution meant to help you to transition from one
state of the application to another.
Note: The Test button is not available in
Safari.
|
Continue 'prompt' button | Generates new activities in the Recorder to cover the entire prompt. |
Delete key
| Deletes the selected activity card. Advanced user keyboard shortcut; no confirmation prompt is displayed. |
Generate with Autopilot trash bin button | Deletes the Generate with Autopilot placeholder activity card. |
Esc key
|
Returns to the Studio Web canvas. If you have made changes in the Recorder, a pop-up with the Save your changes made in the
Selection Helper? message is displayed. You can
select:
If the Properties panel is open, pressing
Esc
takes you back to the Activities view of the Recorder.
|
Cancel button | Returns to the Studio Web canvas without saving any changes. |
Save button | Saves your workflow sequence and populates the activities in the Studio Web canvas. |
Help (F1) icon | Opens the documentation page. |
Autopilot is enabled by default for all users.
You can disable Autopilot capabilities via Automation Ops governance policies in two ways:
- By adding a Studio Web policy and setting the Allow Autopilot option to No.
- By adding a AI Trust Layer policy and disabling the Enable calls to third party AI models through AI Trust Layer toggle button.
When either one of these options is disabled, you can still use the Autopilot Recorder for UI Automation, but you cannot generate activities via text prompts, you can just manually add activities in the Recorder.