- 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
- Configuring automation capabilities
- Audit
- Settings - Tenant Level
- Resource Catalog Service
- About Resource Catalog Service
- Folders Context
- Automations
- Processes
- Jobs
- Triggers
- Logs
- Monitoring
- Queues
- Assets
- Storage Buckets
- Test Suite - Orchestrator
- Other Configurations
- Integrations
- Host administration
- Organization administration
- Troubleshooting
About Resource Catalog Service
Resource Catalog is a tenant-level service used to aggregate resources, serving as the foundation for tags that categorize said resources.
It is very useful in helping you keep track of the relationship and dependencies between various resources across UiPath® services, making them easily manageable in ever expanding automations.
Tags stored by the Resource Catalog Service can be created for Orchestrator assets, processes, queues, storage buckets, and machines, for Studio packages, and for Action Center actions.
This centralized solution allows you to:
- cross-reference resources between services - for example, if you add a tag to an asset in Orchestrator, that tag becomes available for actions as well.
- group resources by business case - for example, you can add the same tag to all objects that will be used in an automation, such as a machine template, a process, a queue, and various assets.
- filter and find all objects with the same tag - if, for example, you want to see all objects pertaining to a certain automation, you can simply search, at the tenant level, for the tag corresponding to that automation, and the relevant objects will be displayed.
The Resource Catalog is involved in both single-node and multi-node Orchestrator installations.
For the initial deployment or update of this service, you can use the parameters in the Publish-ResourceCatalog.ps1 script.
For migrating user data from Resource Catalog to Orchestrator, you can use the parameters in the MigrateTo-ResourceCatalog.ps1 script.
