Free cookie consent management tool by TermsFeed Robots [Appian RPA v9.4]
The capabilities described on this page are included in Appian's standard capability tier. Usage limits may apply.

What is a robot?

A robot is a digital worker that's made up of two parts: a host machine and an agent. A robot needs a workspace, just like a human worker does. The host machine is the environment in which the digital worker completes robotic tasks. The host machine can be a physical machine, such as a separate computer, or a virtual machine on a cloud server. Multiple robots can map to the same host machine.

To execute a robotic task, the robot needs certain data or information from the server. The robot communicates with the server through an agent, which is a file you install on the host machine. Agents must be up and running on the host machine for robotic tasks to execute properly and communicate the results back to the console.

Where to manage robots

The Operations Console is designed to allow Operations Managers to set up and maintain a fleet of robots to support robotic task executions. Any user who is added to the Designer role, System Administrator role, or a member of the RPA Operations Managers system group has access to the Operations Console.

Administrators can control who has access to the Operations Console by updating a user's group membership in Appian.


What you can do in the Operations Console

By default, Operations Managers can perform the following actions:

  • Access the Operations Console
  • Execute robotic tasks on a robot

Additionally, Operations Managers can perform the following actions when they share permissions with the robot they're interacting with:

Only administrators can create and delete robots in the Operations Console.


See also

If you need more information about managing robots or information about generally monitoring things in Appian RPA, see the Manage category.

Open in Github Built: Fri, Feb 23, 2024 (09:13:35 PM)