Unattended robot registration
Every unattended robot must successfully register with Pega Robot Manager before the robot can process assignments. An administrative operator (also called a registration operator) performs the registration process with an appropriate Access Role. The robot is assigned to a base Work Group during registration according to the configuration specified in the decision tables. A successful registration assigns the robot to the correct base Work Group with the appropriate Access Groups and roles.
For example, an organization that has various unattended robots across different divisions or units. One area has a small number of robots, while another has a larger number. Managing how the robots are registered, provisioned, or shared may vary because of the number of robots. Flexibility at the decision table and settings level let the administrator determine managing the way robots are implemented across an organization.
For more information about configuring robotic Work Groups, see Pega Robot Runtime Work Group provisioning.
RPA Service assisted robot registration
The RPA Service is a Windows service that runs on the unattended robot and communicates with Robot Manager. The RPA Service is responsible for starting the Windows session for unattended robots when directed to do so by Robot Manager. This direction might result from a Robot Manager user action or Auto-balancing or Scheduling. When an RPA Service-assisted robot runs, it registers with a Work Group based on a cascading series of criteria.
The first criterion checks whether the robot was previously assigned to a Work Group. If the robot had a previous assignment to a Work Group, then the robot retains its last Work Group. If a robot is stopped, moved to a new Work Group, and then started again, it starts in the Work Group to which it was moved.
If a robot is not associated with any Work Group, the system checks the WorkgroupSpecifiedInPayloadTakesPrecedence dynamic system setting. When the value of WorkgroupSpecifiedInPayloadTakesPrecedence is true, the Robot Runtime commonconfig.xml setting or a command line parameter determines the Work Group of the robot. When the value of WorkgroupSpecifiedInPayloadTakesPrecedence is false, Robot Manager uses decision tables to identify the base Work Group for the robot.
The system first checks the pyGetWorkGroupByRobotID decision table to try to identify the base Work Group. If that decision table is invalid, the system then uses pyGetWorkGroupForRobotByRequestorOperatorId. If that decision table is also invalid, the system falls back to the Work Group specified by the registration request. This setting is equivalent to the value of WorkgroupSpecifiedInPayloadTakesPrecedence as true.
Check your knowledge with the following interaction:
This Topic is available in the following Module:
Want to help us improve this content?