- 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
- Audit
- Cloud robots
- Folders Context
- Automations
- Processes
- Jobs
- Apps
- Triggers
- Logs
- Monitoring
- Queues
- Assets
- Storage Buckets
- Test Suite - Orchestrator
- Resource Catalog Service
- Authentication
- Integrations
- Classic Robots
- Troubleshooting
About Assets
Assets usually represent shared variables or credentials that can be used in different automation projects. They allow you to store specific information so that the Robots can easily access it.
Additionally, an extra level of security is provided, as all assets of type Credential stored here are encrypted with the AES 256 algorithm. They can be invoked by RPA developers when designing a process, but their values can be hidden from them.
The Assets page enables you to create new assets. It also displays all previously created assets, which can be edited or deleted.
The Get Asset and Get Credential activities used in Studio request information from Orchestrator about a specific asset, according to a provided AssetName. If the AssetName provided in Studio coincides with the name of an asset stored in the Orchestrator database, and the Robot has the required permissions, the asset information is retrieved and used by the Robot when executing the automation project.
There are four types of assets:
- Text - stores only strings (it is not required to add quotation marks)
- Bool - supports true or false values
- Integer - stores only whole numbers
-
Credential - contains usernames and passwords that the Robot requires to execute particular processes, such as login details for SAP or SalesForce.
Note:All asset types are encrypted in the Orchestrator database by default.
Existing assets are also encrypted when updated.
The value assigned to an asset can have either or both of the following value types:
All accounts receive the asset value unless a specific value is assigned on a per-account basis.
-
All accounts receive the asset value.
-
All accounts receive the global value, except for John Smith, who receives a particular value only defined for their account.
The value is received only by the specified account-machine pair. When specifying account-machine pairs, make sure they are valid i.e., the configured account-machine mappings in the tenant or folder do not exclude them, otherwise job execution is not possible on that pair, hence the asset does nothing.
- Assets per user-machine only work on Robots v20.10 or newer.
-
Known issue (added September 2023): You are wrongly allowed to unassign the machine configured for an asset from the folder that the asset pertains to. This, in turn, also removes the account, thus rendering the asset unusable. Please be mindful of this limitation when removing machines from folders.
