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.