- 简介
- 入门指南
- 可在任何画布上构建
- 使用案例构建
- 使用流构建
- Build with BPMN
- 运营
- 监控
- 正在优化
- 参考信息
先决条件
Checklist of requirements for Maestro Orchestrate, covering tenant enablement, the services that Flow uses, Studio Web system requirements, and environment readiness.
Maestro Orchestrate is based on UiPath® Studio Web. For Studio Web requirements, check Automation Cloud System Requirements.
Use this checklist to verify your environment is ready for Maestro Orchestrate. It covers tenant enablement, user roles and app permissions, and Unattended licensing across tenant, machine template, and folder. Missing any item can result in pending jobs or a disabled Open in Process Mining button.
Orchestrator 权限
在发布 Maestro Orchestrate 流程的 Orchestrator 文件夹中,您需要以下权限:
- Processes.view和Processes.edit — 用于查看或编辑 Maestro Orchestrate 流程。
- Jobs.view 和 Jobs.edit——用于查看或编辑流程实例(作业)。您可以在文件夹级别授予等效权限。如需更多详细信息,请查看“默认角色和权限”。
Minimum permissions for Case execution
This section lists the folder-level Orchestrator permissions needed to execute a Case process — starting cases, driving them through stages, completing tasks, and viewing case data. The built-in Automation User role covers most of these by default, but is missing a few permissions required at runtime.
Case processes are driven from one of two execution surfaces, each using a different permission family:
- Maestro Orchestrate operate view — the default surface for operators and developers. Uses the Jobs permission family.
- Case Apps — 企业用户的替代界面。使用Apps权限系列执行相同的操作。
Maestro Orchestrate operate view permissions
| 权限 | 用途 | 默认情况下,在 Automation User 中 |
|---|---|---|
| Jobs.view | 查看案例状态、阶段和执行历史记录。 | 是 |
| 作业.创建 | 通过消息开始或中间事件启动案例或向案例发送信号。 | 是 |
| 作业.编辑 | 推动案例:重新打开案例,选择下一阶段,提交事件,或取消、暂停、继续和重试。 | 是 |
| Actions.view 、 Actions.Create 、Actions.edit | 查看并完成案例创建的人机回圈 Action Center 任务。 | 是 |
| Processes.view | 阅读支持案例的流程定义。 | 是 |
| Assets.view | 查看未掩码的资产支持值。 | 是 |
| Connections.view | 通过 Integration Service 执行对第三方集成的调用。 | 是 |
| Triggers.view 、触发器.创建 | 当案例在“等待触发”步骤暂停时,在运行时注册触发器。 | 否 — 手动添加 |
| Logs.view | View variable values in the Maestro Orchestrate operate view. Can be omitted for fully automated, headless execution. | 否 — 手动添加 |
在“等待触发”步骤暂停的案例会在运行时注册触发器。如果没有Triggers.Create ,此步骤将失败,并显示 403 错误。此要求不会在权限审核中出现,仅在案例到达等待步骤时出现。
案例 Apps 权限
If users work through a Case App instead of the Maestro Orchestrate operate view, the same operations require Apps permissions instead of Jobs permissions:
| 权限 | 用途 | 默认情况下,在 Automation User 中 |
|---|---|---|
| Apps.view | 查看案例及其任务。 | 是 |
| Apps.编辑 | 重新打开案例、选择下一阶段或取消案例。 | 否 — 手动添加 |
| Apps.创建 | 发送消息以开始案例或向案例发送信号。 | 否 — 手动添加 |
推荐设置
从内置的“自动化用户”角色开始,并添加:
- Triggers.view和Triggers.Create
- Logs.view
- Apps.view 、 Apps.edit和Apps.Create — 仅当用户通过案例应用程序工作时
不需要权限
The following are not required to execute a Case process: Jobs.delete, Processes.edit, and create, edit, or delete permissions on Assets, Queues, Connections, and Storage Buckets.
Starting a case from Orchestrator is authorized by Orchestrator using the starting user's permissions. Maestro Orchestrate does not re-check this authorization.
Flow prerequisites
Flow processes use these services. Turn them on for the tenant, as Managing services describes.
| 服务 | What Flow processes use it for |
|---|---|
| Orchestrator | Runs deployed processes and stores their runs. Required. |
| Integration Service | 与其他应用程序 (例如 Slack 或 Gmail) 的连接。 |
| Action Center | 人工步骤,例如审批和升级。 |
| Data Fabric | Data entities that processes read and write. |
| Document Understanding 和 智能提取处理 (IXP) | 从文档中读取和提取数据的节点。 |
Builders usually create, test, and deploy their first Flow processes in a Personal Workspace, a private folder that belongs to each user. Turn on Personal Workspaces for the users or groups that build, as Personal workspaces describes.
To build Flow processes in VS Code, install the UiPath Maestro extension. Flow in VS Code lists what else it needs.
执行设置
对于从 Maestro Orchestrate 调用的流程,通过已部署智能体流程中的包要求管理其执行设置。检查链接执行设置。
无人值守的 Runtime 设置
虽然 Maestro Orchestrate 本身不需要分配 Runtime,但由 Maestro Orchestrate 流程启动的作业可能需要无人值守的 Runtime。对于通过 Maestro Orchestrate 调用的 RPA 工作流:
- 至少有一个用户或机器人帐户启用了无人值守,被分配给租户并添加到目标文件夹。阅读“Unattended Robot 设置”以了解配置步骤,阅读“机器人帐户”以了解服务帐户,阅读“管理机器人”以了解文件夹分配。
- 您的文件夹包含已分配 Runtime 的计算机模型。查看“计算机模板”。
“优化”选项卡和 Process Mining
- 您的租户已启用 Process Mining。 查看“在 Automation Cloud 中启用服务”。
- Existing Maestro Orchestrate permissions let you see the Optimize tab and access the Process Optimization app.
- 要在自动创建的“流程优化”应用程序中编辑数据转换,您需要 Process Mining Developer 角色。阅读“设置用户”。
- 您在 Process Mining 中拥有“流程优化”应用程序的“编辑数据”、“编辑仪表板”和“查看”权限。 阅读“管理 Process Mining 应用程序的访问权限”。