Edit

Distribute tasks

General overview

There are various types of Bot Tasks. For example, several lines of businesses may want to automate different types of applications. In this case, there is a need to divide RPA Units into separate queues with one type of tasks to be transferred to the first queue, the second type of tasks—to the second, and so on. The reasons for the segregation can be as follows:

• Regulatory or security requirements
• Business Processes of a significantly varying nature in terms of applications used
• Segregated development teams for different Business Processes with no direct communication or collaboration path, for example, when different service providers are responsible for implementations

To distribute RPA tasks, use the unified method of task routing via fleets. Fleets stand for groups of RPA Units used to segregate tasks according to their business purpose.

note

For the legacy RPA fleet configuration using the fleet attribute in the XML configuration of the RPA plugin, see Robotics plugins. If both a Bot Source fleet and the legacy attribute are present, the Bot Source settings have priority.

Configure fleets for RPA tasks

Before you proceed with the fleet setup, configure RPA Units on the RPA Windows server.

To configure fleets, perform the following steps:

1. Go to INSTALL_DIR/bot-agent/conf/units and modify or copy the unit{Unit_id}.yml file, where {Unit_id} refers to the RPA Unit identifier.

2. Change unit_id and fleet.

   unit_id: 2
   fleet: shared
   

   shared is the default fleet. If your unit_id is more than 9, remove the last 0 in each port—the maximum number for one machine is 99.

3. To define custom fleets to submit tasks to, specify fleet for each RPA Unit:

   unit_id: 3
   fleet: SAP
   

tip

To set up fleets using the Bot Source functionality, refer to Work with fleets.