orchestrator

2022.10

false

Getting started
- Introduction
- User Options
- Logging in to Orchestrator
- Resetting Your Password
- My Profile
- 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
- Organizing Resources With Tags
- Orchestrator Read-only Replica
Tenant
- About the Tenant Context
- Searching for Resources in a Tenant
- Robots
- Folders
- Monitoring
- Managing Access and Automation Capabilities
- Machines
- Packages
- Audit
- Credential Stores
- Webhooks
  - Types of Events
  - Managing Webhooks
- Licensing
  - Managing Your Licenses
- Alerts
- Settings
Resource Catalog Service
- About Resource Catalog Service
Folders Context
- About the Folders Context
- Home
Automations
- About Automations
Processes
- About Processes
- Managing Processes
- Managing Package Requirements
- About Recording
Jobs
- About Jobs
- Managing Jobs
- Job States
- Working with long-running workflows
- Running Personal Remote Automations
- Troubleshooting Jobs
Triggers
- About Triggers
- Managing Triggers
- Using Cron Expressions
Logs
- About Logs
- Managing Logs in Orchestrator
- Logging Levels
- Orchestrator Logs
Monitoring
- About Monitoring
- Machines
- Processes
- Queues
- Queues SLA
- Exporting usage data
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)
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
Other Configurations
- Increasing the Size Limit of Package Files
- Setting up Encryption Key Per Tenant
- GZIP Compression
Integrations
- About Input and Output Arguments
  - Example of Using Input and Output Arguments
Classic Robots
- Robots
- Environments
  - Managing Environments
- Jobs
- Triggers
- Monitoring
  - Robots
- Resources
Host administration
- About the host level
- Managing system administrators
- Managing tenants
- Configuring host authentication settings
- Managing your host license
  - Allocating Licenses to Tenants
- Configuring other host settings
- Configuring system email notifications
- Audit logs for the host portal
- Maintenance Mode
Organization administration
- About organizations
- Managing organization administrators
- Managing organization settings
- Configuring organization authentication
- Configuring security options
  - Session policy
- About licensing
  - Activating your license
- Accounts and groups
  - Managing access
  - Managing accounts and groups
- Authorizing external applications
  - Managing external OAuth applications
- Overriding system email settings
- Audit logs
Troubleshooting
- About Troubleshooting
- Alerts troubleshooting
- General troubleshooting
- Upgrade troubleshooting
- Frequently Encountered Orchestrator Errors

OUT OF SUPPORT

Orchestrator user guide

Running Personal Remote Automations

This article walks RPA developers, citizen developers, and business users through the steps for running personal automations from Orchestrator by manually launching a job via the Start Job functionality or by using a trigger.

Prerequisites:

You or an administrator previously deployed the background process you want to execute to a folder you have access to.
An administrator allocated the unattended infrastructure for running jobs by adding a machine template object to the folder.

Start a Job as Yourself

Navigate to Automations > Jobs in the folder the background process resides in.
Click Start. The Start Job window is displayed.
From the Process Name drop-down, select the process you want to execute.
From the Account drop-down, select Run as Myself (Personal automation) to execute the job under your own identity. Note that this option is available only for background processes.
Configure the other settings following the instructions provided in the Starting a job documentation.
Click Start to start the job. The job is displayed as Pending on the Jobs page until a robot is available to pick it up.

Configure a Trigger to Launch Jobs as Yourself

Navigate to Automations > Triggers in the folder the background process resides in.
Click Add a new trigger. The Create trigger window is displayed.
On the Name field, give your trigger a meaningful name.
From the Process Name drop-down, select the process you want that trigger to launch jobs for.
From the Account drop-down, select Run as Myself (Personal automation) to execute the jobs launched by the trigger under your own identity. Note that this option is available only for background processes.
Configure the other settings following the instructions provided in the Managing triggers documentation.
Click Add to add the trigger. The trigger is displayed in the Triggers page and will launch a job under your own identity according to the trigger configuration.

On this page

Start a Job as Yourself
Configure a Trigger to Launch Jobs as Yourself

Was this page helpful?

PREVIOUSWorking with long-running workflows

NEXTTroubleshooting Jobs