orchestrator

latest

false

Getting started
- Introduction
- Robots
  - Robot Statuses
  - Robot Settings
- Auto Updating Client Components
- Time-to-live Periods
- Orchestrator Outbound IP Addresses
- Notifications
Best practices
- Organization Modeling in Orchestrator
- Automation Best Practices
- Optimizing Unattended Infrastructure Using Machine Templates
- Unattended automation
- 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
- Folders
- Monitoring
- Access control
- Configuring automation capabilities
  - Enabling personal automations
    - Enabling individual users to run personal automations
- Machines
- Packages
- Audit
- Credential Stores
  - Integrating credential stores
  - Managing credential stores
- Webhooks
  - Types of Events
  - Managing Webhooks
- Licensing
  - Managing Your Licenses
- Settings
  - Robot Security Tab
  - Scalability Tab
    - SignalR (Robots)
Cloud robots
- Automation Cloud™ Robots - VM
- Configuring VPN for cloud robots
- My notifications
Folders Context
- About the Folders Context
- Home
Automations
- About Automations
Processes
- About Processes
- Managing Processes
- Managing Package Requirements
- Recording
Jobs
- About Jobs
- Managing Jobs
- Job States
- Working with long-running workflows
- Running Personal Remote Automations
- Process Data Retention Policy
Apps
- About Apps
- Publishing an App to a Tenant
- Managing Apps
- Running a Deployed App from a Folder
Triggers
- About triggers
- Managing triggers
- 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
Queues
- About Queues and Transactions
- 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
Test Suite - Orchestrator
- 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
- Testing Data Retention Policy
Resource Catalog Service
- About Resource Catalog Service
Authentication
- About Authentication
Integrations
- About Input and Output Arguments
  - Example of Using Input and Output Arguments
Classic Robots
- Robots
- Environments
  - Managing Environments
- Jobs
- Triggers
- Monitoring
  - Robots
- Resources
Troubleshooting
- About Troubleshooting
- Frequently Encountered Orchestrator Errors

Orchestrator User Guide

DELIVERY:

DELIVERY:

Automation Cloud Automation Cloud Public Sector Automation Suite Standalone

Last updated Oct 30, 2024

Managing Assets in Studio

Studio has two activities, Get Asset and Get Credential, that the Robot can use to extract information from assets stored in the Orchestrator database.

They are displayed in the Activities panel, under Orchestrator > Assets, and are part of the UiPath® Core activities pack.

The Get Asset activity should be used with the String, Boolean and Integer assets, while Get Credential should be used with Credential assets.

Note: The asset name is not case sensitive. For example, "Text" and “teXt” are the same.

Using the Get Asset Activity

In Orchestrator, create a string, boolean or integer asset.
In Studio, create a string, boolean or integer variable, depending on the type of asset you want to use from Orchestrator. For example, if you want to work with a string asset, create a string variable.
From the Activities panel, drag a Get Asset activity to the Main panel.
In the Properties panel, in the AssetName field, type the name of the Orchestrator asset you want to use, and place it between quotation marks. For example, if in Orchestrator the asset name is StringAsset, write "stringasset" in Studio.
In the Properties panel, in the Value field, enter the variable created at step 2. This variable stores information from the specified Orchestrator asset, if the AssetName coincides with the asset name that is stored in the Orchestrator database, and the Robot has the required permissions.

Using the Get Credential Activity

In Orchestrator, create a Credential asset.
In Studio, create a String variable. This is used to store the username part of the credentials.
Create a SecureString variable. This is used to store the password. The SecureString is a special .NET Framework variable type that is encrypted within the framework.
In the Properties panel, in the AssetName field, type the name of the credential asset, as it is in Orchestrator, and place it between quotation marks. For example, "amazon_login".
In the Properties panel, in the Password field, enter the SecureString variable.
In the Properties panel, in the Username field, enter the string variable. The credential asset stored in Orchestrator can be used by the Robot too, as long as the AssetName coincides with the asset name that is stored in the Orchestrator database, and the Robot has the required permissions.

On this page

Using the Get Asset Activity
Using the Get Credential Activity

Was this page helpful?

PREVIOUSManaging Assets in Orchestrator

NEXTStoring Assets in Azure Key Vault (read only)

Support and Services

Get The Help You Need

Learning RPA - Automation Courses

UiPath Community Forum

Trust and Security

© 2005-2024 UiPath. All rights reserved.