- Getting started
- Best practices
- Tenant
- About the Tenant Context
- Searching for Resources in a Tenant
- Managing Robots
- Connecting Robots to Orchestrator
- Storing Robot Credentials in CyberArk
- Storing Unattended Robot Passwords in Azure Key Vault (read only)
- Storing Unattended Robot Credentials in HashiCorp Vault (read only)
- Storing Unattended Robot Credentials in AWS Secrets Manager (read only)
- Deleting Disconnected and Unresponsive Unattended Sessions
- Robot Authentication
- Robot Authentication With Client Credentials
- SmartCard Authentication
- Managing Packages
- About Libraries
- Managing Libraries
- Audit
- Settings - Tenant Level
- Resource Catalog Service
- Folders Context
- Automations
- Processes
- Jobs
- Triggers
- Logs
- Monitoring
- Queues
- Assets
- Storage Buckets
- Test Suite - Orchestrator
- Other Configurations
- Integrations
- Classic Robots
- Host administration
- Organization administration
- Troubleshooting
Orchestrator User Guide
Managing 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.
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.
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.
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.
- In the Packages page, 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 ProcessesManaging JobsManaging triggersPlease note that you cannot edit the values of the parameters at this level, only at process, jobs, and triggers ones.
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.
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.
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.
.xaml
file that is part of a package version like Studio's Designer panel. This feature enables smoother cooperation between developers and Orchestrator managers.
-
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.
Details are available on each of the aforementioned fields, buttons, and panels in the Field Descriptions page.
.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.
Here's how you can view the differences at the package version level, and then at the workflow file level:
Read on for step by step instructions:
- Downloading a Package Version
- Manually Uploading Packages to Orchestrator
- Deleting Packages
- Displaying Release Notes for One Package Version
- Displaying Release Notes for All Package Versions
- Viewing the Arguments of a Package
- Adding Tags to Packages
- Removing Tags From Packages
- Exploring Packages
- Comparing Packages and Workflows