- 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)
- Deleting Disconnected and Unresponsive Unattended Sessions
- Robot Authentication
- Robot Authentication With Client Credentials
- SmartCard Authentication
- Audit
- Resource Catalog Service
- Folders Context
- Automations
- Processes
- Jobs
- About Jobs
- Managing Jobs
- Job States
- Working with long-running workflows
- Running Personal Remote Automations
- Troubleshooting Jobs
- Triggers
- Logs
- Monitoring
- Queues
- Assets
- Storage Buckets
- Orchestrator testing
- Other Configurations
- Integrations
- Classic Robots
- Host administration
- Organization administration
- Troubleshooting
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.