部署解决方案意味着将解决方案包作为新部署安装在 Orchestrator 文件夹中。有关解决方案部署的更多信息，请参阅了解解决方案开发生命周期。
您可以从 Studio Web 或 Orchestrator 启动解决方案部署。两个界面提供相同的基础部署体验：Studio Web 是原始界面，专为希望在单个流程中打包和部署的解决方案作者而设计； Orchestrator 是管理界面，专为租户管理员大规模管理部署而设计。此页面记录了 Orchestrator 流程。
Orchestrator 部署流程需要已发布到订阅源的解决方案包。您可以先从 Studio Web 或 Studio 桌面版发布包，然后在此处进行部署。
此步骤通常由管理员执行。
打开“部署”工作流
您可以从 Orchestrator 中的以下任何位置打开“部署”工作流：
- Deployments tab: Select Deploy in the upper-right corner.
- Packages tab: Select the Deploy row action for the package you want to deploy.
- Package sidebar: Open a package to expand its sidebar, then select Deploy in the upper-right corner of the sidebar.
- Versions tab of the Package sidebar: Select the Deploy row action for the specific package version you want to deploy.
所有四个路径都会在“设置”表单上打开相同的“部署”工作流。顶部的面包屑导航为“租户”>“解决方案”>“部署”>“部署” 。
填写“设置”表单
The Setup form is where you define what to deploy, where it lands, and how it activates. Complete the following fields, then select Deploy. The Package and Version fields are always visible; the remaining fields are grouped under the Options control, which you can expand or collapse. When collapsed, Options shows a summary of the current values (for example, the destination folder, whether triggers are enabled right away, and whether a runtime is set up).
| 字段 | 描述 |
|---|---|
| 包 | Select the solution package to deploy from the dropdown. The list shows all packages published to your tenant feed. After you select a package, its description appears beneath the field. |
| 版本 | The package version to install. Appears after you select a package. Defaults to the latest published version. The publish date and release notes for the selected version appear beneath the field. Select a different version from the dropdown if needed. |
| 选项 | Expands or collapses the deployment settings that follow. When collapsed, it shows a summary of the selected values. |
| 部署名称 | A required, tenant-unique name for this deployment. Auto-filled from the package name. Edit to use a different name. The name is validated as you type: if a deployment with the same name already exists, the form shows an error and you cannot continue until the name is unique. |
| 位置 | 将在其中创建解决方案文件夹的文件夹。默认为共享。从下拉列表中选择其他文件夹，以更改目标位置。 |
| 解决方案文件夹名称 | The name of the subfolder created inside the destination folder. Auto-filled to match the deployment name until you edit it. Edit to customize it for this deployment. |
| 立即激活 | 打开（默认情况下打开）。启用后，如果存在触发器，系统会立即启用触发器。 |
| 设置运行时 | 打开（默认情况下打开）。启用后，可在租户级别未配置默认执行计算机时配置 Serverless Runtime。 |
运行部署
完成“设置”表单后，选择表单底部的以下选项之一：
-
Deploy: validates the configuration and runs the deployment immediately. The workflow progresses through the following steps shown in the What will happen panel on the left:
步骤 描述 配置 验证并设置部署。 部署 设置文件夹并配置资源。 激活 如果启用了“立即激活”，则启用触发器并验证部署。 -
Customize (select the dropdown arrow on the Deploy button): opens the resource explorer so you can review and configure individual solution components before the deployment runs. In the resource explorer, you can:
- Filter the properties shown for a component using the Display control (All properties, Empty properties, Required properties, or Configurable properties).
- Link a component to an existing resource using Link to existing.
- Revert your changes to a component using Reset.
- Review the Issues counter (errors, warnings, and information) and the Logs panel.
When you finish, select one of the following:
- Continue to proceed with the deployment.
- Validate to check the configuration without deploying.
- Save as draft to save and resume later.
- Delete draft to discard the deployment.
Save a deployment as a draft
If you are not ready to run a deployment, you can save your progress and finish it later:
- Select Customize from the Deploy button dropdown to open the resource explorer.
- Configure components as needed.
- Select Save as draft.
The draft appears in the Deployments tab with a Draft status chip. To resume it, select the draft row, then select Continue editing. To discard it, select Delete draft.
重用现有组件（可选）
When the deployment is located outside your Personal Workspace (for example, in a shared folder), the candidate list excludes resources stored in your Personal Workspace at any folder depth, including nested subfolders. This prevents broken deployment configurations that your collaborators cannot run or maintain because they cannot access your Personal Workspace resources.
If the deployment is inside your Personal Workspace, all your accessible resources, including your Personal Workspace resources, are available for linking.
当您选择“自定义”时，资源资源管理器会显示解决方案包中的所有组件。如果租户中已存在同名组件，您可以将解决方案链接到该组件，而无需新建组件。
此选项适用于“资产”、“存储桶”、“Webhook”和“队列”。对于每个冲突，您可以：
- 保留现有组件，而不创建其他组件。
- 保留现有组件，并从解决方案中添加新字段（现有字段不更改）。
- 重命名相应服务中的冲突资源。
- 如有可能，请在解决方案部署中重命名资源。
要链接现有组件：
-
在资源浏览器中，选择要链接的组件。
-
选择“链接到现有” 。
-
在“链接到现有流程”对话框中，选择要链接到的组件。
-
选择“链接” 。
- When a resource is linked, it is not created as part of the deployment; the solution uses the linked resource directly. Linking a resource with a different name may lead to runtime errors unless the solution was developed to support this configuration.
- When you link a resource that exists in another folder, the solution stores the runtime dependency against the solution folder where the resource is copied, not the original source folder. Users with permissions on the solution folder can run the process without needing permissions on the original resource location.
监控部署状态
部署开始后，您可以从工作流视图或解决方案中的部署选项卡监控进度。可能的状态如下：
| 状态 | 描述 |
|---|---|
| 处理中 | 正在运行部署操作。 |
| 成功 | 部署已完成，所有组件均已安装。 |
| 失败 | 部署失败，已执行自动回滚。 |
| 回滚失败 | 部署失败，某些组件需要手动清理。 |
有关所有状态的详细信息，请参阅部署状态。
激活部署
如果解决方案包含应用程序，但未使用提供的链接激活这些应用程序，则部署激活将失败。有关详细说明，请参阅Orchestrator和Apps文档。
成功部署后，Orchestrator 会评估激活就绪情况。部署将显示在“部署”选项卡中，并具有以下状态之一：
-
非活动（准备激活） ：无需其他配置。选择“更多操作”图标，然后选择“激活部署” 。
-
非活动（需要设置才能激活） ：激活前，必须完成其他先决条件：
-
选择“更多操作”图标，然后选择“设置激活” 。
-
查看激活验证结果并完成必填项目：
- 添加帐户并分配角色。
- 将计算机添加到解决方案文件夹。
- 按需定义帐户-计算机映射。
- 定义每个机器人的资产值（如果适用）。
- 激活解决方案中使用的应用。
- 如果适用，请填写流程类型组件的绑定。
备注：When deploying a solution, a Default Serverless template may be automatically attached to the target folder if the Set up runtime toggle was enabled on the Setup form. This ensures the solution can run without manually configuring machine templates. If a serverless template is already inherited, no additional template is attached.
-
解析所列项目。
-
选择“验证” 。
-
选择“激活” 。
-
Result: Once your solution is deployed and successfully activated, that solution is displayed on the Deployments tab with an Active status.