Orchestrator user guide

DELIVERY:

Last updated Sep 17, 2025

Managing Packages

Downloading a Package Version

Under Packages, select the desired tab depending on your package type. In the grid, select More Actions for a package, then click View Versions. The Package Versions window is displayed.
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.

Manually Uploading Packages to Orchestrator

By default, the maximum package size limit is 300MB.

Note: To manually upload a package with tags you need Create on Tags. If you do not have Create on Tags, the package is uploaded without tags.

Under Packages, select the desired tab depending on your package type, then select the Upload button . The Add Package window is displayed.
Click Browse and select the packages (with the .nupkg extension) you want to upload to Orchestrator.
Select I would like to see which processes can be upgraded to display all processes that use a previous version of the package being uploaded.
Select Upload. Orchestrator automatically determines the package type and displays the uploaded package in the corresponding grid under Tenant > Packages. If you selected the I would like to see which processes can be upgraded option, the Upgrade multiple processes window is displayed, showing a list of the processes that can be upgraded to a newer package version.

Figure 1. Upgrading multiple processes
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. Only the package version is updated. If you want to customize the process parameters or entry points, edit the process.

Deleting Packages

A package can only be deleted from Orchestrator if all its versions have been deleted. Package versions can be deleted if they are Inactive, i.e., not deployed to a process.

Under Packages, select the desired tab depending on your package type and locate your package in the list. From the More Actions menu for the package, select View Versions. The Package Versions window is displayed.

Figure 2. Package Versions
Select one or more versions and click Remove. Alternatively, click More actions > Delete for the package version you want to delete. The selected package versions are removed.
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

Under Packages, select the desired tab depending on your package type. In the list, select More Actions for a package, then click View Versions. The Package Versions window is displayed.
On the Versions tab, you can see all package versions of the selected package.
For the desired version, select More Actions > Show Release Notes. The Release Notes window is displayed, enabling you to check the note added in Studio for the respective version.

In addition to that, you can see the note added in Studio, as well as the Windows applications used by the respective package version, displayed in alphabetical order. If the package uses applications that cannot be identified, an Unknown apps entry is displayed, suffixed by the number of unidentified apps, in parentheses. If no applications can be retrieved, a No app(s) could be retrieved for this package message is displayed. This is most likely due to one of the following reasons:

Your Studio version is older that 2023.2.
Your Studio version is 2023.2, but there is a governance rule in place, preventing this information from being logged.
Your package was uploaded from an external feed. Only packages from internal feeds can provide this information.
The package does not use any applications.

These details are also displayed in the process window for its underlying package.

Figure 3. Package details Screenshot of package details

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

Under Packages, select the desired tab depending on your package type. In the package list, select More Actions for a package, then click View Versions. The Package Versions window is displayed.
Select the Change Log tab. You can check all package versions of the library, and for each, the corresponding release note containing information related to what has changed in-between versions.

Figure 4. Change log for package 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

Under Packages, select the desired tab depending on your package type. Select More Actions for a package, then click View Versions. The Package Versions window is displayed.
Click More Actions > Show Arguments for the desired package version. The input and output parameters of the selected package version are displayed. Managing Processes Managing Jobs Managing triggersPlease note that you cannot edit the values of the parameters at this level, only at process, jobs, and triggers ones.

Viewing package processes

You can see the processes associated to a package by clicking See processes in the following places:

In the contextual menu of the desired package at the tenant level - this displays the processes associated to all versions of that package.
In the contextual menu of a package version at the tenant level - this displays the processes associated to the particular package version you selected.

Both options above display the Processes of package window, which lists the folders where that process is included.

You can only see the folders that you have view access to, regardless of any other folders where that process might be included. The Edit option is only available for folders that you also have edit access to.

Adding Tags to Packages

You can apply tags to a package at design time in Studio. To learn how to add tags to packages, see About Publishing Automation Projects in the Studio guide.

You cannot change the tags of a package from Orchestrator. Tags are specific to each package version. On the Packages page in Orchestrator, you can see tags specific to the latest package version, regardless if it's active or inactive.

Removing Tags From Packages

You can remove tags from a package at design time in Studio. To learn how to remove tags from packages, see About Publishing Automation Projects in the Studio guide.

Comparing Packages and Workflows

You can view the differences between any two selected versions of a package, knowing what changed: added, modified or deleted .xaml files, changes in folders, or the dependencies list. You can also compare the two selected versions' workflow .xaml files, graphically presented side by side. This feature enables Orchestrator managers to view what changed in the packages and workflows without requiring Studio access.

Under Packages, select the desired tab depending on your package type, then select Explore Package next to a package. The Explore Package window is displayed, giving you access to all the versions of the selected package. Note that the Explore Package option is only available in the Automations and Test Automations grids.
Click the Compare button above the list of package versions to toggle the compare mode. A checkbox appears in front of each package version.
Check the boxes corresponding to the package versions you want to compare. You can only compare two package versions at a time.

Alternatively, you can compare the same .xaml file corresponding to two package versions. To do this, expand one package at a time and select the workflow file.
Click the Compare button below the list of package versions. This button is activated after you select two checkboxes. The Comparing window is displayed, containing a list of results with the newest selected version's workflow files, along with the project author, and description. The workflow file set as Main in Studio is marked accordingly, and the project dependencies are displayed under the Dependencies section.

Alternatively, if you chose to compare workflow files in the previous step, the two workflows are displayed side by side, the earliest file version on the left.
Filter the differences that are displayed by selecting one of the options in the top-right corner of the window:
- All - displays all the differences between the compared package versions or workflow files. This is selected by default, displaying a summary of all the differences.
- Added - highlights in green the files, folders, or dependencies added to the package version, or the containers, connectors, and activities added to the workflow files shown in the Comparing window, along with their exact number.
- Modified - highlights in yellow the files, folders, or dependencies that were changed within the package version, or the containers, connectors, activities, and properties or property values that were changed within the workflow files shown in the Comparing window, along with their exact number.
- Deleted - highlights in red the files, folders, or dependencies that were deleted from the package version, or the containers, connectors, and activities that were deleted from the workflow files shown in the Comparing window, along with their exact number.
  
  Figure 5. Comparing window
Click the Compare button next to a workflow file from the list of results. The two workflows are displayed side by side, the earliest file version on the left, and with an individual scroll for each workflow. All the changes that happened in the file between the two package versions at the container, connector, or activities level are highlighted and color-coded as follows:
- Green highlight for added content
- Yellow highlight for modified content
- Red highlight for deleted content.
  
  Figure 6. Comparing flowcharts
  
  If only minor changes were performed at the workflow level, such as positioning of activities or connectors, you are notified that the logic hasn't been altered.
(For containers only) Double-click a container activity. The Comparing window displays only the activity within both package versions, for a focused view. If the activity exists in only one of the workflow files, then it is displayed in the corresponding workflow's side. Navigate back from the container to the workflow by clicking the breadcrumb trail.

Figure 7. Comparing flowcharts
Click any activity to view the changes to its properties. All the changes that happened in the activity between the two package versions are highlighted and color-coded, as mentioned before.

Exploring Packages

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

Note:

You cannot explore compiled packages using this feature.
You can view Studio packages that are uploaded along with all their .xaml sources (i.e. the Include Sources option selected in the Publish options > Compilation settings section) in their entirety in the package explorer. This applies to Windows and cross-platform projects.

Learn more about automation projects in the Studio guide.

Under Packages, select the desired tab depending on your package type, then select Explore Package next to a package. The Explore Package window is displayed, giving you access to all the versions of the selected package. Note that the Explore Package option is only available in the Automations and Test Automations grids.
Select 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 set as Main in Studio is marked accordingly, and the project dependencies are displayed under the Dependencies section.
Select a .xaml file. The workflow is displayed.
To view all the variables, arguments, or imports available in the selected file, select the Variables,Arguments, or Imports button. The corresponding panel is displayed, similar to that available in Studio.

Figure 8. Viewing all variables, arguments, or imports available in a selected file
Double-click any scope to see a focused view of the workflow.

Figure 9. Workflow
Click Expand All to get a better view of a workflow section.
Select any activity to view its properties. Please note that you can also copy the value of any property.