Running processes locally
Control Room allows you to manage, orchestrate, and schedule the execution of your software robots in a central place. Control Room has Processes, which contain steps that Runtime Environments execute. A Runtime Environment can be a Docker container or an actual physical or virtual machine running the Robocorp Workforce Agent application.
This article instructs how to set up a Control Room workforce process to run on a local machine via Robocorp Workforce Agent.
Please note: Using this approach, the robot's triggering is still the responsibility of Control Room. Suppose you plan to set up attended automation, allowing the end-user to trigger the robot and interact with it. In that case, we suggest you look into the Robot Assistant feature instead.
You will need a Robocorp account for accessing Control Room and Robocorp Workforce Agent, available for Windows, macOS, and Linux to follow along. If you haven't already, you might want to follow the Quickstart guide to get familiar with Control Room.
Install and link Robocorp Workforce Agent
Follow the Robocorp Workforce Agent installation guide to install and link Robocorp Workforce Agent to your workspace in Control Room. Make sure your Robocorp Workforce Agent is correctly linked and running:
Environments page of your workspace in Control Room, you should now see your Robocorp Workforce Agent, marked as
With the Robocorp Workforce Agent set up and running, we are ready to assign it something to do!
Set the step in your process to point to your local environment
- In Control Room, navigate to your process and open a step
- Edit the environment of the step to point to your local environment
- You can now return to the Process view in Control Room and run the process.
- Note that
Robocorp Workforce Agentapplication itself does not show anything other than just logging about the execution; it is designed to stay in the background.
- Note that
By installing and running Robocorp Workforce Agent in a target system, you can run your robots there. Robots are triggered and scheduled in Control Room, and artifacts and logs are uploaded to Control Room.
Tip: Different steps in a process can be executed in different environments as needed. This enables you, for example, to off-load heavy processing steps that do not need the resources of the local machine to Control Room containers or other machines.
"The step that needs Maria's machine" can be implemented to be as small and quick as possible so that the previous and following process steps can handle the heavy lifting.