- Getting started
- Introduction
- User options
- Logging in to Orchestrator
- Resetting your password
- Robots
- Robot Statuses
- Robot Settings
- Auto Updating Client Components
- Orchestrator Configuration Checklist
- Best practices
- Organization Modeling in Orchestrator
- Managing Large Deployments
- Automation Best Practices
- Optimizing Unattended Infrastructure Using Machine Templates
- Unattended automation
- Useful concepts in unattended automation
- How is unattended automation performed
- Organizing Resources With Tags
- Orchestrator Read-only Replica
- Exporting grids in the background
- Tenant
- About the Tenant Context
- Searching for Resources in a Tenant
- Robots
- 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
- Folders
- Managing Folders
- Classic Folders Vs Modern Folders
- Migrating From Classic to Modern Folders
- Administration of Modern Folders
- Personal Workspaces
- Managing Personal Workspaces
- Monitoring
- Unattended sessions
- User sessions
- License
- Managing Access and Automation Capabilities
- Assigning Roles
- Managing Roles
- Default roles
- Configuring access for accounts
- Enabling personal automations
- Enabling unattended automations
- Configuring robot accounts to run unattended automations
- Machines
- Managing Machines
- Assigning Machine Objects to Folders
- Configuring Account-machine Mappings
- EDR Protection Status
- Packages
- Managing Packages
- About Libraries
- Managing Libraries
- Audit
- Credential Stores
- Managing credential stores
- Integrating credential stores
- Webhooks
- Types of Events
- Managing Webhooks
- Licensing
- Managing Your Licenses
- Alerts
- Configuring Alerts
- Alert Emails
- Setting up Alert Emails
- Settings - Tenant Level
- Resource Catalog Service
- About Resource Catalog Service
- Automation Suite Robots
- About Automation Suite Robots
- Prerequisites
- Executing Unattended Automations With Automation Suite Robots
- Regenerating Client Secrets
- Frequently Asked Questions
- Folders Context
- About the Folders Context
- Home
- Automations
- About Automations
- Processes
- About Processes
- Managing Processes
- Managing Package Requirements
- Recording
- Live streaming and remote control
- Troubleshooting live streaming and remote control
- Jobs
- About Jobs
- Managing Jobs
- Job States
- Working with long-running workflows
- Running Personal Remote Automations
- Process Data Retention Policy
- Triggers
- About triggers
- Time triggers
- Queue triggers
- Managing triggers
- Creating a time trigger
- Creating a queue trigger
- Managing Non-Working Days
- Using Cron Expressions
- Triggering jobs on the last day of the month
- Logs
- About Logs
- Managing Logs in Orchestrator
- Logging Levels
- Monitoring
- About Monitoring
- Machines
- Processes
- Queues
- Queues SLA
- Exporting usage data
- Queues
- About Queues and Transactions
- Queue Item Statuses
- Business Exception Vs Application Exception
- Studio Activities Used With Queues
- Queue Item Retention Policy
- Bulk uploading Queue Items using a CSV file
- Managing Queues in Orchestrator
- Managing Queues in Studio
- Managing Transactions
- Editing Transactions
- Field Descriptions for the Transactions .csv File
- Review Requests
- Assets
- About Assets
- Managing Assets in Orchestrator
- Managing Assets in Studio
- Storing Assets in Azure Key Vault (read only)
- Storing Assets in HashiCorp Vault (read only)
- Storing Assets in AWS Secrets Manager (read only)
- Storage Buckets
- About Storage Buckets
- CORS/CSP Configuration
- Managing Storage Buckets
- Moving Bucket Data Between Storage Providers
- Orchestrator testing
- Test Automation
- Test Cases
- Field Descriptions for the Test Cases Page
- Test Sets
- Field Descriptions for the Test Sets Page
- Test Executions
- Field Descriptions for the Test Executions Page
- Test Schedules
- Field Descriptions for the Test Schedules Page
- Test Data Queues
- Managing Test Data Queues in Orchestrator
- Managing Test Data Queues in Studio
- Field Descriptions for the Test Data Queues Page
- Test Data Queue Activities
- Testing Data Retention Policy
- Integrations
- About Input and Output Arguments
- Example of Using Input and Output Arguments
- Classic Robots
- Robots
- Managing Robots
- Robot Statuses
- Setup Samples
- Environments
- Managing Environments
- Jobs
- Triggers
- Monitoring
- Robots
- Resources
- Troubleshooting
- About Troubleshooting
- Alerts troubleshooting
- General troubleshooting
- Frequently Encountered Orchestrator Errors
Orchestrator user guide
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:
Global Value
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.
Value Per Account-Machine
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.
Value Per Account
The value is received only by the specified account. If Global Value is disabled, at least one per-account value must be provided.