- 入门指南
- 设置和配置
- 自动化项目
- 依赖项
- 工作流类型
- 控制流程
- 文件比较
- 自动化最佳实践
- 源代码控件集成
- 调试
- 日志记录
- 诊断工具
- 工作流分析器
- 变量
- 参数
- 导入的命名空间
- 编码自动化
- 基于触发器的 Attended 自动化
- 录制
- 用户界面元素
- 选取器
- 对象存储库
- 数据抓取
- 图像与文本自动化
- Citrix 技术自动化
- RDP 自动化
- VMware Horizon 自动化
- Salesforce 自动化
- SAP 自动化
- macOS 用户界面自动化
- ScreenScrapeJavaSupport 工具
- Webdriver 协议
- 扩展程序
- Studio 测试
- 故障排除
Studio 用户指南
Solutions group everything needed to automate an end-to-end business process, offering you the capabilities to develop automation projects together with their dependencies and deploy them across tenants as a whole.
Solutions are cloud-level containers for modeling an end-to-end automation as a single, versioned unit. In a solution, you can create and orchestrate:
- RPA 工作流
- API 工作流
- 智能体
- 智能体流程
- Apps (with human-in-the-loop validations)
All these components share solution-scoped resources (assets, connections, queues, storage, etc.) that you manage centrally at the solution level. Solutions are also portable—package once and deploy across tenants and organizations with environment-specific configuration.
To learn more, refer to the Studio Web user guide.
The Project panel allows you to manage the projects in your solution, as well as the project files in each project.
Inside the Project panel, you can:
- Use the
Add to Solution button to:
- Create a new automation project and add it to your solution.
- Import an existing automation project.
Note: You can also access the Add to Solution window by right-clicking inside the Solution panel.
- Use the
Search bar to find specific projects, files, pages, actions, variables, or arguments in your solution.
- Right-click the solution to rename it or open it in Studio Web.
- Right-click a project to:
- Open the project in Studio and access the context menu for projects with project-specific options.
- Open the project in Studio Web in a new browser tab.
- Remove the project from the solution.
When you open a solution in Studio, you can only make changes to RPA projects. Other types of projects included in a solution cannot be modified from Studio and require you to continue editing the solution in Studio Web (this includes app projects, agentic processes, API projects, and agents).
Projects that cannot be modified in Studio are greyed out in the Solution panel. You can right-click a project that is not supported in Studio to either open it in Studio Web or remove it from the solution. When opening the project in Studio Web, changes are saved to cloud and the project is opened in a new browser tab.
The experience of designing and debugging RPA projects within a solution is the same as with standalone RPA projects.
The Defined Resources panel displays the resources included in your solution. The panel can be collapsed. Resources are automatically added to a solution as they are used by activities and are grouped under these categories:
- Apps - 由自动化提供支持的用户界面，允许您构建连接到数据的自定义业务应用程序。
- 资产- 可在不同自动化项目中使用的共享变量或凭据。
- “业务规则” - 用于存储和管理“决策模型”和“表示法”(DMN) 文件的对象。
- 连接- Integration Service 连接，可帮助在单个用户和外部应用程序之间建立任务。
- 可提供对许可知识库访问权限的上下文- 上下文基础索引。
- 流程- 链接到特定文件夹的包版本。
- 队列- 队列是一个容器，可用于存储不限数量的项目。
- 存储桶- 创建自动化项目时利用的文件夹存储解决方案。
- 任务目录- 操作容器，您可以在其中根据各种条件对操作进行分类。在创建操作时，使用 Studio Web 中的操作创建活动设置存储操作的目录。
- 依赖项- 在上下文中链接到特定项目的活动类别。
Activities are aware of the solution context. Inside activities that handle solution resources (for example, Add Queue Item), the resource picker widget displays all available resources (assets, queues, connections, etc.). You can also use the Open Orchestrator button to manage platform resources in Orchestrator.
Changes made to a solution are always synced to the cloud, allowing you to seamlessly switch between Studio and Studio Web.
After you create a solution in Studio Web, you have the option to continue working in Studio. From the Workspace page in Studio Web, open the menu on the right side of a solution and select Open in Studio Desktop. Alternatively, open the solution in Studio Web, right-click the solution name in the Solution Explorer, and select Open in Studio Desktop.
- Open in Browser - Open the solution in Studio Web. If the solution is locked by Studio Web, an error is displayed and the solution is opened in a new tab in read-only mode.
- Sync with Cloud - Push the changes that you made in Studio and continue building your solution in Studio Web.
You can add a solution under Git version control by selecting the Add To Source Control label in the status bar. This allows you to manage commits and branches at solution level.
- Studio detects when a project is part of a solution. Opening a local project that is part of a solution automatically opens the entire solution context.
- When converting a cross-platform project to the Windows compatibility, the project is converted directly, without the option to create a copy of the original project.
- New solutions can only be created in Studio Web. You can open and edit existing solutions in Studio, which is context-aware and allows you to enhance solutions with cross-platform and Windows RPA projects.
- Renaming individual projects is currently supported only in Studio Web.
- You can only publish the current RPA project from Studio.
- Some project types (agentic processes, apps, API workflows, or agents) can only be opened and edited in Studio Web. You can use Studio for its powerful RPA design and debug experiences, and Studio Web to access agentic automation features.
- Solution packaging and deployments occurs only in Studio Web. Support for solutions will be added to CI/CD integrations with UiPath CLI in the future.
- You can view Windows projects in the Solution Explorer in Studio Web, but you can edit them only when you open the solution in Studio.
- Only one user can work on a solution at a time. We introduced a solution-level lock to prevent unsolvable conflicts (for example, when one user builds an API workflow project in Studio Web while another edits an RPA project in Studio). Without this lock, a later sync to cloud could overwrite one set of changes. This limitation will be removed once Studio Web supports local workspaces (saving the entire solution to disk), allowing standard Git flows to safely resolve conflicts.
- Use Git at the solution level to version automation projects together with their configurations.
- Deploy the solution for debugging in Studio Web before opening it in Studio. This ensures all solution resources and projects are deployed in Orchestrator and are ready for use in Studio.
