- 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
- Running and testing your projects
- Managing automations
- Web app projects - Preview
Studio Web User Guide
System requirements
To find out what are the requirements for using Studio Web, see the Automation Cloud System Requirements.
- Design time - You can design
automations with UI Automation activities in Studio Web from:
- Google Chrome - available on Windows and macOS.
- Microsoft Edge - available on Windows.
- Safari - available on macOS.
Studio Web and the target web apps must be rendered in the same browser (Chrome, Edge, or Safari) and the UiPath extension must be installed for the browser.
-
Run time - Automations built with UI Automation and Studio Web run by default on serverless robots in the UiPath Cloud in Chrome. With the help of UiPath Orchestrator, they can be configured to run unattended on Windows, macOS, and Automation Cloud robots where the browser and the corresponding UiPath extension are installed.
Note: Support for the Safari browser extension is only available if you install UiPath Assistant 2024.10.5 or higher.
In response to Google’s timeline for Chrome Manifest V2 (MV2) deprecation, starting from June 2024, existing Studio Web extensions for Chrome and Edge have been updated to be fully compatible with Manifest V3, while retaining the same extension IDs for both browsers (Chrome and Edge).
No action is required to receive the new MV3 extensions, which will be automatically updated when you reopen the browser. Following the upgrade to MV3, the debugging banner notification will be displayed each time you start an interactive selection.
When the automation runs on serverless robots, the MV2 extension is still used. The robot serverless image will also be updated to include the pre-installed MV3 extension for Chrome before the Chrome MV2 deprecation in stable versions.
