orchestrator
2024.10
true
- 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
- Configuring automation capabilities
- Managing Packages
- About Libraries
- Managing Libraries
- Audit
- Resource Catalog Service
- Automation Suite robots
- Folders Context
- Automations
- Processes
- Jobs
- Apps
- Triggers
- Logs
- Monitoring
- Queues
- Assets
- Storage Buckets
- Test Suite - Orchestrator
- Integrations
- Troubleshooting
Orchestrator User Guide
Last updated Nov 13, 2024
Managing Libraries
Note: Uploading a library requires your user to have Create permissions on Libraries. Read more about .
This functionality is useful when, for example, the Studio instance in which you design processes is not connected to Orchestrator.
- On the Libraries page, click Upload. The Upload Library window is displayed.
- Click Browse and select the library package (with the .nupkg extension) you want to upload to Orchestrator. The name of the file is displayed in the Upload Library window.
- Click Upload. The library is uploaded to Orchestrator, and it is displayed on the Libraries page. It is stored either in the host feed or in the tenant feed, as configured on the Deployment tab, in the Settings page. Details about feeds here.
Note: The Download button is enabled for libraries only if you use a local feed, and you have View permissions on Libraries. Read more about .
Note: This action depends on the settings
you have chosen at the tenant level, on the Deployment tab:
- Only host feed - libraries are uploaded to the host feed, which means that they can be deleted only from the host level.
- Only tenant feed and Both host and tenant feed - libraries are uploaded to the tenant feed or to the tenant and host feed, which means that they can be deleted from the tenant level.
- On the Libraries page, click View Versions. The Package Versions window is displayed.
- Click the Versions tab. You can see all package versions of the library displayed.
- Select a specific version or multiple and click Remove. The selected package versions are removed.
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.
