Skip to main content

Moving robots manually between workgroups

3 Tasks

20 mins

Visible to: All users
Beginner Pega Robot Manager 8.6.4 Robotic Process Automation English


MyTown is opting for unattended Robotic Process Automation (RPA) to manage the spike in Service Requests that occur on Mondays and Tuesdays of each week. Historically, the data shows inquiries trend down during that same time. The MyTown RM application intends to manage this workload shift by allowing only those robots in Inquiry work group to move to the Service Request work group. The robots in the Service Request work group cannot be moved. 

The default Candidate work group and requestor mapping created by MyTown must be modified to implement this business need. You are asked to use the RPA services in the robot simulator to test the available work groups and ensure the Robot registration settings are configured to support balancing the workload. You must also test that the robots from the Inquiry work group can move to the Service Request work group by manually moving them within Pega Robot Manager.

You must initiate your own Pega instance to complete this Challenge.

Initialization may take up to 5 minutes so please be patient.

Detailed Tasks

1 Update the Candidate work group and requestor mapping

  1. If Pega Robot Simulator is running, on the RPA Simulator Main window, click Stop for each REQRPA and INQRPA service.
  2. Launch the Pega Training instance and log in with user name RMSysAdmin and password myt0wn@pp1
  3. From the Dev Studio header, click Launch portal > Robot Manager to open the Robot Manager portal.
  4. On the left navigation panel, click Settings > Robot registration to display the Robot registration landing page.
  5. Open the Candidate work group and requestor mapping section
  6. Click More icon >  Edit  to open the section in the edit view
    edit work group mapping
  7. Click the Pencil icon to edit the row in the table
  8. In the Candidate work group and requestor mapping edit dialog, enter InquireRegID in the Requestor identifier field
    Dialog box to update candidate work group and requestor mapping.
  9. On the Service Request WG line, click the Trash icon to delete the work group.
    The candidate work group and requestor mapping dialog box with the icon to delete work group.
  10. Click Submit to close the window
  11. Click Save to finish saving changes within the table
    save work group and requestor mapping

2 Validate updated work group and requestor mapping

  1. On the left navigation panel, click Unattended RPA > Robots to display the Robots landing page.
  2. On the Robots tab, click INQ00 to access the Robot Details page.
    The Robots screen of Pega Robot manager with INQ00 robot selected.
  3. On the Robots Details page, hover over the number of possible work groups to display the original configuration of the decision table.
    The INQ00 robot screen showing possible work groups.
  4. Open Pega Robot Simulator, if not already running. Otherwise skip to step 5.
    1. On the Pega Robot Simulator login screen, confirm that the robot server URL matches the URL of the Pega instance.
      1. In the Enter credentials used to start robots section, enter:
        1. In the User field, enter InquireRegID.
        2. In the Password field, and InqRobot1!
      2. Enter credentials used to create cases section, enter:
        1. In the User field, enter QueueRegID.
        2. In the Password field, and QueRobot1!
    2. Click Login to access Pega Robot Simulator.
  5. In the RPA Simulator Main window, from the Select a RPA Service drop-down, select INQRPA.
    1. Click Start to display the RPA Simulator Configure RPA Service window.
    2. On the RPA Simulator Configure RPA Service, clear the Use default credentials check box.
      1. In the User field, enter InquireRegID
      2. In the Password field, enter InqRobot1!
      3. Click Start RPA Service.
  6. In your browser, on the Pega Robot Manager tab, click the browser Refresh. The page refreshes and the number of possible work groups for INQ00 is updated to 1.
  7. On the Robot Details page, hover over the possible work groups and confirm that Inquiry WG is now the only work group displayed.
    The INQ00 robot screen showing one possible work group.
  8. In the RPA Simulator Main window, start the RPA service for REQRPA by logging in with user name SvcReqRegID and password SvsRobot1!.
  9. Confirm that the Service Request robots have two possible work groups configured.

3 Move robots from Inquire work group to Service Request

  1. In the left navigation panel, select Unattended RPA > Workgroups.
  2. On the Work groups landing page, click Inquiry WG. The Inquiry WG details page is displayed.
    The Work groups screen of Pega Robot Manager indicating the Inquiry group.
  3. On the Inquiry WG details page in the Robots section, click the Move robots here. The Move robots dialog is displayed.
    The workgroup details screen with the option: Move robots here.
  4. On the Move robots dialog, select SRQ00, and then click Move. The Inquiry WG page refreshes showing the newly added robot, SRQ00.
    The move robots dialog box with one robot selected to be moved to another work group.
    The work group details showing moved robot.
  5. In the browser, click the Back button to return to the Work groups landing page.
  6. On the Robots landing page, click Service Request WG to display the Service Request work group details page.
  7. In the Robots frame on the Service Request work group details page, click Move robots here.
  8. In the Move robots window, select SRQ00 and then click Move. The SRQ00 robot is returned to the base work group.
Note: In the RPA Robot Simulator, remember to stop the two RPA services, INQRPA and REQRPA. 

Available in the following mission:

If you are having problems with your training, please review the Pega Academy Support FAQs.

Did you find this content helpful?

Want to help us improve this content?

We'd prefer it if you saw us at our best.

Pega Academy has detected you are using a browser which may prevent you from experiencing the site as intended. To improve your experience, please update your browser.

Close Deprecation Notice