ROBIN Robot 2.0.0 (ROBIN Robot Employee) - the mandatory component of the Robin platform, designed for local launch and control of the work of software robots created in the Studio.

ROBIN Robot has functionality:

Composition and versions of ROBIN Robot

ROBIN Robot consists of modules:

  1. ROBIN Player - the Robin Robot user interface provides management of local robots. Robin Player launches robots created in Robin Studio (extension files .robin-robot).
  2. ROBIN Agent - an application ensuring the interaction of the components of the Robin Studio-Robin Orchestrator-Robot Robot-Executor platform.
  3. ROBIN Executor - performing engines (.net, java, python), which ensure the performance of scenarios on the platforms.

ROBIN Robot has two versions:

What kind of robots are running on Linux

When creating a robot script for Linux, make sure that the actions used are implemented in java and python. Such robots run on both Linux and Windows in the same way. Actions implemented in .net run only on windows

The ROBIN Robot also has several delivery options:

Standalone option

Enterprise variant

There is also a Cloud delivery option for managing software robots on a separate workstation under the control of the ROBIN Cloud service (see the ROBIN Cloud portal for a description of how to use the ROBIN Cloud).

Robot launch options

One ROBIN Robot license allows an unlimited number of robot scenarios to be run on a single workstation. Sequential and parallel running of scenarios is also available.

Parallel execution of scenarios is possible for robots that do not use UI applications and the same resources for operation. Such robots can work simultaneously with each other or with the user, since all actions are performed in the background without using application windows.

Robots that use application UI in their work are launched sequentially. Only one software robot can work with the UI at a time.

Example

A robot reading an Excel file, working with email, operating system processes, performing background calculations, interacting with web pages - it runs entirely in the background and its actions may not be visible to the user.

For a robot that runs a desktop application scenario, it is important for the application window to be open, so such a robot cannot work simultaneously with the user or another robot of the same type.