Automation Co-Pilot Desktop Assistant automation activities

As an attended user who runs attended bots, you can perform several automation activities using Automation Co-Pilot Desktop Assistant .

Automations page overview

Automation Co-Pilot Desktop Assistant is designed for users with either an attended license, an Automation Co-Pilot Business User license, or both. Attended Bot Runners can use their license to run bots, while users with an Automation Co-Pilot Business User license can run processes. Users with both licenses can run both bots and processes. Click Users and roles for Automation Co-Pilot for more details.

The Control Room administrator adds Active Directory (AD) users by selecting AD domain, providing environment details, and assigning a role and device license. The administrator can further deploy the Control Room RBAC by specifying role-based privileges and permissions at the bots and Bot Runner level. Users with an attended Bot Runner license can launch this application, use their AD credentials to sign in and review the list of available bots, and run the specific bot.

In Automation Co-Pilot Desktop Assistant, you can view a list of available bots for you to run in the Automations page.

Automations page in Automation Co-Pilot Desktop Assistant.

Based on your permission, you can view alerts and notifications from Automation Co-Pilot through your desktop. To access the alerts, click the New notifications display with the (new-notification) icon:

Notification icon

You can re-size the page to fit your screen and have its contents automatically adjust.

Automations page that's been resized.

From the Automations page, you can also pin, sort, or search for bots.

Key features

Prepared session for automation deployment
When deploying Automation Co-Pilot automations on either hidden or visible runtime windows, a prepared (pre-warmed) session is now used, which results in shorter automation execution time. If this session is terminated, the automation will prepare a new session for subsequent deployments.
Continue pending automation
You can continue any pending automation that you started from different Automation Co-Pilot Desktop Assistant instances. If you start an automation from one instance and then reconnect to continue the automation on another instance, the automation will process.
This provides a consistent automation experience no matter which instance you use to access Automation Co-Pilot Desktop Assistant.
Consistent state
Automation Co-Pilot Desktop Assistant will remain in a consistent state regardless of how many Automation Co-Pilot Desktop Assistant instances you use. The state will be updated to the latest state across all Automation Co-Pilot Desktop Assistant instances.
View and run any available bots
To view and run any available bots, simple click Start to start the automation.
Sample of start button
View status or control bot progress in one page
After you run a bot, you can view its progress in real time.
The progress details of a bot run contains information such as:
  • The name of the bot.
  • The action that is currently being performed.
  • The line number that is being executed.
  • The total number of lines in the bot.
  • Status of the bot run (% completed).
The progress details are displayed only when a bot is run on a local device by a user with Attended Bot Runner license.
Sample of a bot running to show its progress and additional controls.
You can also pause, start (resume), or stop the bot progress.
By presenting the status and bot controls on one unified page, this ensures consistency for each bot run.
Note: To use the bot controls, you must have the Managed my activity permission. Otherwise, you can view the controls only.
View detailed status
You can view the details of a bot status .
For example, you can use the details to troubleshoot the automation if an error occurs.

Sample of a detailed error status from a bot.