Subscribe

UiPath Orchestrator

The UiPath Orchestrator Guide

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

Package Feeds


Feeds are package streams that allow you to store and group packages in order to control their availability and isolation.

Tenant Feed

Packages added to the tenant feed are global resources, meaning they are available across folders. They are referred to as simply "packages" and are managed on the Packages page (Tenant context > Packages).

Folder Feed

Packages added to a folder feed are folder-specific resources, meaning they are kept separate and only available in the folder they have been added to. They are often referred to as "folder packages" and are managed on the Folder Packages page (Folder context > Automations tab > Folder Packages).

Only root folders can be configured with a dedicated package feed. All subfolders inherit the package feed setting from the root parent. Access to the feed is controlled by the folder-scoped Folder Packages permission set.

Using v3 feed URLs results in a couple of display issues with packages.

  • The publish date of a package is not correct.
  • For MyGet feeds, the total number of packages is much greater than the actual number of packages uploaded to the feed.

Personal Workspace Feed

A personal workspace feed resembles a folder feed. Packages published to a personal workspace feed are workspace-specific resources, meaning they are kept separate and only available in the workspace they have been added to. A personal workspace comes with a dedicated feed by default. Packages added to a workspace feed are automatically deployed as processes in the context of that workspace. They are managed on the Folder Packages page (Personal Workspace context > Automations tab > Folder Packages).

Feed Considerations

Packages published to Orchestrator are sent to a default web app that uses the NuGet protocol (NuGet, MyGet). On the Orchestrator machine, the folder path is displayed in the UiPath.Orchestrator.dll.config file, under the Storage.Location parameter. On the Robot machine, this folder path is set in the NuGetServerUrl parameter, in the UiPath.settings file. If your Robot is not connected to Orchestrator, the default location of the packages is %ProgramData%\UiPath\Packages.

Orchestrator uses this NuGet app to maintain package versions. When you deploy a package to an environment, the package is distributed to each of the Robots in the indicated environment (in the %USERPROFILE%\.nuget\Packages folder).

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

Package Versions


Package versioning is configured in Studio when publishing a package to Orchestrator or other custom location. For details on the available versioning schemas, check the Studio article here.

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.

A package version can have the following statuses:

  • Active - it is currently deployed to a process or a modern folder;
  • Inactive - it is not currently deployed to a process or a modern folder (only these can be deleted).

Package Migration


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.

Package Explorer


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.
Please note that flowcharts are displayed similarly to standard workflow diagrams.

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.

Package Permissions


To perform various actions on the Packages page you need to be granted the corresponding permissions on Packages:

  • View - view all package-related details, view which processes can be upgraded, and explore and download packages (these two also require internal feeds);
  • Edit - doesn't grant any additional rights at the moment;
  • Create - manually upload packages or publish them from Studio;
  • Delete - delete inactive packages.

To perform various actions on the Folder Packages page you need to be granted the corresponding permissions on Folder Packages:

  • View - view all folder package-related details, view which processes can be upgraded, and explore and download folder packages (these two also require internal feeds);
  • Edit - doesn't grant any additional rights at the moment;
  • Create - manually upload folder packages or publish them from Studio;
  • Delete - delete inactive folder packages.

Read more about Roles.

Updated 26 days ago



Packages


Suggested Edits are limited on API Reference Pages

You can only suggest edits to Markdown body content, but not to the API spec.