UiPath Orchestrator

Managing Packages

Manually Uploading Packages to Orchestrator

This functionality is useful when, for example, the Studio instance in which you design processes is not connected to Orchestrator.

Please note that, by default, the maximum package size limit is 30MB. This value can be changed in IIS, as explained here.

  1. In the Packages page, click the Upload button. The Upload Package window is displayed.
  1. Click Browse and select the packages (with the .nupkg extension) you want to upload to Orchestrator (by default, when not connected to Orchestrator it is %ProgramData%\UiPath\Packages).
  2. (Optionally) Select I would like to see which processes can be upgraded to display all processes using a previous version of the package being uploaded.
  3. Click Upload. The package is uploaded to Orchestrator and it is displayed in the Packages page. If you selected to view processes that can be upgraded, the Upgrade multiple processes is displayed.
  1. Use the checkboxes to select which processes to upgrade and click Upgrade. The selected processes are updated to the new package version and the window closes.

Downloading a Package Version

  1. In the Packages page, click View Versions. The Package Versions window is displayed.
  1. Click More Actions > Download package for the corresponding package version you want to download. The package is downloaded to the default location configured in your browser, in the .nupkg format. From here you can upload it to another Orchestrator instance.

Note:

The Download button is enabled only if you use a local feed, and you have View permissions on Packages.

Deleting Package Versions

Packages can only be deleted from Orchestrator if they have the Inactive status. A package has this status only if it is not deployed to a process.

  1. In the Packages page, click View Versions. The Package Versions window is displayed.
  1. Select one or more versions and click Remove. The selected package versions are removed.
  2. Click Remove All Inactive to delete all inactive versions of the selected process. If a package version is part of a process (it is active), it is NOT going to be deleted. If all the versions are inactive, they are all deleted.

Displaying Release Notes for one Package Version

  1. In the Libraries page, click View Versions. The Package Versions window is displayed.
  2. On the Versions tab you can see all package versions of the library displayed.
  1. For the desired version, click More Actions > Show Release Notes. The Release Notes window is displayed, enabling you to see the note that was added in Studio for the respective version.

Note that you have the option to manually download package versions from the Release Notes window as well. The process is similar to downloading them from the Versions tab.

Displaying Release Notes for all Package Versions

  1. In the Packages page, click View Versions. The Package Versions window is displayed.
  2. Click the Change Log tab. You can see all package versions of the library, and for each, the corresponding release note containing information related to what has changed in-between versions.

Note that you have the option to manually download package versions from the Change Log tab as well. The process is similar to downloading them from the Versions tab.

Viewing the Arguments of a Package

  1. In the Packages page, click View Versions. The Package Versions window is displayed.
  2. Click More Actions > Show Arguments for the desired package version. The input and output parameters of the selected package version are displayed. Please note that you cannot edit the values of the parameters at this level, only at process, jobs, and schedules ones.

Exploring Packages

You can view and explore the graphical representation of any .xaml file that is part of a package version in a manner similar to that of Studio's Designer panel. This feature enables for a smoother cooperation between developers and Orchestrator managers.

  1. In the Packages page, click Explore Package next to a package. The Explore Package window is displayed, in which you have access to all the versions of the selected package.
  2. Click a version you want to see more about. All .xaml files available in the project are displayed, along with the project author, description, and date at which it was uploaded to Orchestrator. The .xaml file that was set as Main in Studio is marked here accordingly, and the project dependencies are displayed under the Dependencies section.
  3. Click a .xaml file. The workflow is displayed.
  4. To view all the variables, arguments, or imports available in the selected file, click the Variables, Arguments, or Imports button. The corresponding panel is displayed, similar to that available in Studio.
  1. Double-click any scope to see a focused view of the workflow.
  1. (Optionally) Click Expand All to get a better view of a workflow section.
  2. Click any activity to view its properties. Please note that you can also copy the value of any property.

Details are available on each of the aforementioned fields, buttons, and panels in the Field Descriptions page.



Managing Packages


Suggested Edits are limited on API Reference Pages

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