UiPath Orchestrator

UiPath Orchestrator 指南

The Packages page displays all the projects published from UiPath Studio, as well as the ones that were manually uploaded.




添加到租户订阅源中的包是全局资源,这意味着它们可在各个文件夹中使用。它们简称为“包”,并在“包”页面(“租户”上下文 >“包”)中进行管理。


添加到文件夹订阅源的包是特定于文件夹的资源,这意味着它们分开保存,并且仅在它们已添加到的文件夹中可用。它们通常称为“文件夹包”,并在“文件夹包”页面(“文件夹”上下文 >“自动化”选项卡>“文件夹包”)中进行管理。


使用 v3 订阅源 URL 会导致包出现几个显示问题。

  • 包的发布日期不正确。
  • 对于 MyGet 提要,包的总数比上传到提要的实际包数要多得多。


个人工作区订阅源类似于文件夹订阅源。发布到个人工作区订阅源的包是特定于工作区的资源,这意味着它们分开保存,并且仅在它们已添加到的工作区中可用。个人工作区默认情况下带有专用订阅源。添加到工作区订阅源的包将自动部署为该工作区上下文中的流程。它们在“文件夹包”页面(“个人工作区”上下文 >“自动化”选项卡>“文件夹包”)中进行管理。


发布到 Orchestrator 的包将发送到使用 NuGet 协议(NuGet、MyGet)的默认网页应用程序。在 Orchestrator 计算机上,文件夹路径显示在 UiPath.Orchestrator.dll.config 文件中的 Storage.Location 参数下。在机器人计算机上,此文件夹路径在 UiPath.settings 文件的 NuGetServerUrl 参数中设置。如果机器人未连接到 Orchestrator,则包的默认位置为 %ProgramData%\UiPath\Packages

Orchestrator 使用此 NuGet 应用程序来维护包版本。将包部署到环境时,包将分发到指定环境中的每个机器人(位于 %USERPROFILE%\.nuget\Packages 文件夹中)。

For more information, see the About the Activities Feeds, About Automation Projects on the Robot, and Configuring Tenant Settings pages.


将包发布到 Orchestrator 或其他自定义位置时,系统会在 Studio 中配置包版本控制。有关可用的版本控制架构的详细信息,请参阅此处的 Studio 文章。

Release notes for a package version, as well as input or output parameters have to be configured in Studio in order to be accessible in Orchestrator. The first mentioned feature enables developers to keep track of changes between package versions, while the latter enables you to better integrate third-party tools.


  • “活动”- 当前已部署到流程或新式文件夹;
  • “不活动”- 当前未部署到流程或新式文件夹(只有这些流程可以删除)。


Process = standard RPA process.
Business Process = StudioX projects.
Testing = Test automation project.
Legacy Process = a project with no available metadata.


To help you migrate packages from one Orchestrator instance to the other with ease, such as from a testing environment to a production one, it is possible to download any version, be it active or not. Please note that this is only possible if you are using an internal feed, and you have View permissions on Packages.
From here, you can upload one or multiple packages to another Orchestrator, by using the Upload button. When uploading such .nupkg archives manually you can also check if there are any existing processes that can be upgraded and perform that action instantly, as described here.


Similar to the Studio's Designer panel, the Explore Package option enables you to view and explore the graphical representation of any .xaml file that is part of a package version. The file set as Main is labeled accordingly, and all dependencies are mentioned for each package version. Please note that only packages in internal feeds can be viewed using the Package Explorer.

It is possible to view all the variables, arguments, and imports created for a specific package, exactly like you would in Studio. The properties of an activity are displayed if selected, along with their values, if any. To learn how to view all of these, see Managing Packages.


The Explore Package also allows you to compare the differences between any two selected versions of a package, pointing out workflow files that were added, modified or deleted, and highlighting changes in folders or the dependencies list. It's possible to view the differences between the selected versions' workflow .xaml files, presented side by side, earliest file version on the left, with deleted content highlighted in red, modified content in yellow, and added content in green. Click here to learn how to compare package versions and workflows.




  • “查看”- 查看所有与包相关的详细信息,查看可以升级的流程,以及浏览和下载包(这两个也需要内部订阅源);
  • “编辑”- 目前不授予任何其他权限;
  • “创建”- 手动上传包或从 Studio 发布包;
  • 删除 - 删除不活动的包。


  • 查看 - 查看所有与文件夹包有关的详细信息,查看可以升级的流程,以及浏览和下载文件夹包(这两个也需要内部订阅源);
  • “编辑”- 目前不授予任何其他权限;
  • 创建 - 手动上传文件夹包或从 Studio 发布它们;
  • 删除 - 删除不活动的文件夹包。

Read more about Roles.

2 年前更新

建议的编辑仅限用于 API 参考页面

您只能建议对 Markdown 正文内容进行编辑,而不能建议对 API 规范进行编辑。