How Tricentis RPA works

A Bot is a sequence of actions that you want to perform. These actions are called Steps. Each Step is an automated task that you would otherwise do manually.

You design, test, and publish your Bots in RPA Studio (see the RPA Studio documentation).

With RPA Orchestrator, you use these Bots in production.

RPA Orchestrator consists of two main elements:

• RPA Cockpit, where you trigger Bot runs and view their results.

• Agents, which execute the tasks you defined for your Bots.

Available Agents poll the server that holds RPA Orchestrator at regular intervals.

When you trigger a Bot run, the server forwards the information to the first available Agent. The Agent then executes the Bot Steps.

RPA Orchestrator saves the results to your database and displays them in the RPA Cockpit.

A note on Agents

Agents execute the Steps that you defined when you designed your Bot in RPA Studio.

That means that Agent machines need to have access and the necessary permissions for the applications and files that you want to modify.

For instance, if you designed your Bot to check whether a certain file exists, the Agent must have access to the directory where the file is located.

Or if you designed your Bot to write data to a Microsoft Excel file, the Agent must have the following:

• Microsoft Excel installed

• Access to the directory where the file is located

• Permission to write to the file

Or if you want the Bot to send emails, you need to ensure that your Agent machines and the mail server are able and allowed to communicate via the specified ports.

What's next

Now that you know how Tricentis RPA works, get to know your work environment in RPA Orchestrator.