To move robots between work groups, either manually or by using a schedule, you must define a list of eligible candidate work groups for each administrative operator (registration operator) that registered the robots. All robots that were registered by the same administrative operator can move to those work groups.
When you create a work group instance by using the Pega Robot Manager user interface, the resulting work group ID consists of the specified base work group name followed by the at sign (@) and the business application name. For example, for a base work group named WorkGroup1 created in the MyApp application, the name of the created work group is WorkGroup1@MyApp.
With Pega Robot Manager, you can update the pyGetWorkGroupByRobotID decision table and the pyGetWorkGroupForRobotByRequestorOperatorID decision table through the Pega Robot Manager user interface. For more information, see Changing settings from the Pega Robot Manager interface.
- In the navigation panel of Dev Studio, click Records.
- Expand the Decision category, and then click Decision Table.
- Click the pyGetCandidateWorkGroupListByDispatchOperator decision table in the @baseclass class and save the table to your application ruleset.
- For each administrative operator (registration operator), provide a
comma-separated list of candidate work group IDs. All robots registered by a specific operator can be moved between the specified candidate work groups. The move command can be entered by Pega Robot Manager users or based on a schedule. The list of candidate work groups must contain the ID of a robot's base work group, which is the work group where the robot was assigned when it was first registered. For more information, see About Decision tables.
- Click Save.
- Access group assignment for robots
After the robot registration sequence determines a valid work group for a robot, Pega Robot Manager must also identify an access group to which to map the work group.