Skip to main content

Granting robot access and distributing work

Archived

7 Tasks

30 mins

 Visible to: All users
Beginner Pega Robot Manager 8.5.3 Robotic Process Automation English
This content is now archived and is no longer updated. Progress is not calculated. Pega Cloud instances are disabled, and badges are no longer awarded. Click here to continue your progress in the latest version.

Scenario

MyTown provides utility services to its residents. MyTown routes all inquiries and service requests for existing customers to unattended robotic process automation (RPA) robots to streamline customer service capabilities. The MyTownRM application is configured with two work groups: Inquire WG and Service Request WG.

To ensure these events are created promptly, MyTown has created an application that routes the inquiries to Inquire WG and the services requests to Service Request WG, the designated Pega Robot Manager™ work groups. For the unattended RPA robots to process the work in the correct assignment types, you must create and configure the necessary robot registration operator IDs in Pega Platform™ and the decision tables in Pega Robot Manager.

  • Create two new robot registration operator IDs, InquireRegID and SvcReqReqID, and update the passwords to InqRobot1! and SvcRobot1!, respectively. 
  • Create a new access group, MyTownRM:RobotRegistration, for the MyTownRM application.
  • Include the PegaRobotManager:RobotRegistrar and the PegaRULES:PegaAPI roles in the access group.
  • Create a Queue Registration operator ID, QueueRegID, with the password, QueRobot1!, and access group, MyTownRM:RuntimeUser.
  • Remove the application instance for Work groups and robot mapping decision table.
  • Update the Work groups and requestor mapping decision table to account for both robot registration operator IDs.

Challenge Walkthrough

Detailed Tasks

1 Create the Inquire robot registration Operator ID

Note: You must successfully complete the preceding challenges, in order, before attempting to complete this task.
  1. Log in to the Pega Platform instance by using Operator ID RMSysAdmin and password myt0wn@pp1.
  2. In the Dev Studio navigation pane, click Records > Organization > Operator ID to open the Operator ID data instances.
    robot manager operator link
  3. From the list of Operator IDs, click Create to create the first robot registration Operator ID.
    Create robot registration operator id
  4. On the Create Operator ID form, in the Short description field, enter Inquire Robot Registration ID.
  5. In the Operator ID field, enter InquireRegID.
  6. In the upper right, click Create and open to display the rule form.
    Inquire Reg Operator
  7. On the rule form, in the Application Access section, to the right of the Access Group field, click the Open icon.
    Open new access group.
    Note: If the Access Group field is left blank, clicking the Open icon opens the Create Access Group form.

2 Create the MyTownRM:RobotRegistration access group

  1. On the Create Access Group form, in the Short Description field, enter MyTown Robot Registration AG.
  2. In the Access Group Name field, enter MyTownRM:RobotRegistration.
  3. In the upper right, click Create and open to open the MyTownRM:RobotRegistration rule form.
    Short description and name of robot reg access group.
  4. On the MyTownRM:RobotRegistration rule form, in the Application section, in the Name field, enter or select MyTownRM.
  5. In the Version field, enter or select 01.01.01 to build the version list.
    Application for robot reg access group.
  6. In the Available roles section, in the text box field, enter or select PegaRobotManager:RobotRegistrator.
  7. Under the text box, click Add role to add a text box field.
  8. In the text box field, enter or select PegaRULES:PegaAPI.
  9. In the upper right, click Save. 
    Saved new access group completed definition.

  10. In the upper right, click the X icon to close the MyTownRM:RobotRegistrator rule form.

Note: Creating the Access Group returns you to the InquireRegID rule form.

3 Complete the InquireRegID Operator ID configuration

  1. On the InquireRegID Operator ID rule form, in the Access Group field, enter or select MyTownRM:RobotRegistration to update the Access Group and Application information.
  2. To the left of the Access Group field, select the radio button.
    Robot reg access group selected
  3. On the InquireRegID rule form, click the Work tab.
  4. In the Routing section, click Update to display the Update Organizational Unit window.
    Update operator ID org unit structure.
  5. In the Update Organizational Unit window, expand the organization structure to the unit level and click Unit.
    Note: The top organization item name may vary.
  6. Click Update to close the window and return to the rule form.
    Update org structure for robot reg id
  7. On the InquireRegID rule form, click the Security tab.
  8. In the Access Settings section, click Update password.
  9. In the New Password field, enter InqRobot1!.
  10. In the Confirm New Password field, enter InqRobot1!, and then click Submit.
  11. In the Access Settings pane, verify that all check boxes are cleared.
    Deselected checkboxes on robot reg ID.
  12. In the upper right of the InquireRegID rule form, click Save.

4 Create the Service Request robot registration Operator ID

  1. In the upper right of the InquireRegID rule form, click Save > Save As to create a new Operator ID.
    Service Request robot reg id start
  2. In the Short description field, update the description to Service Request Robot Registration ID.
  3. In the Operator ID field, update the value to SvcReqRegID.
  4. In the upper right, click Create and open to open the SvcReqRegID rule form.
    SvcReq robot reg id create and open
  5. In the Contact Information section, in the Full name field, enter Service Request Robot Registration ID.
  6. In the Email field, enter SvcReqRegID.
  7. In the upper right of the SvcReqRegID rule form, click Save. 
    Service Request robot registration ID
  8. On the SvcReqRegID rule form, click the Security tab.
  9. In Access Settings section, click Update password.
  10. In the New Password field, enter SvcRobot1!.
  11. In the Confirm New Password field, enter SvcRobot1!, then click Submit to return to the rule form.
  12. In the upper right of the SvcReqRegID rule form, click Save.

5 Create the Queue Management operator ID

  1. From the Dev Studio header, click the Operator ID tab. 
  2. From the list of Operator IDs, click Create to create the first robot registration Operator ID.
    Create robot registration operator id
  3. On the Create Operator ID form, in the Short description field, enter Queue Robot Registration ID.
  4. In the Operator ID field, enter QueueRegID.
  5. In the upper right, click Create and open to display the QueueRegID rule form.
    Short description and Operator ID of robot registration id
  6. On the Access Group field, in the Application Access section, enter or select MyTownRM:RuntimeUser.
  7. To the left of the Access Group field, select the radio button.
  8. On the QueueRegID rule form, click the Work tab.
  9. In the Routing section, click Update to display the Update Organizational Unit window.
    Update operator ID org unit structure.
  10. In the Update Organizational Unit window, expand the organization structure to the unit level and click Unit.
    Note: The top organization item name may vary.
  11. Click Update to close the window and return to the QueueRegID rule form.
    Update org structure for robot reg id
  12. On the QueueRegID rule form, click the Security tab.
  13. In the Access Settings section, click Update password.
  14. In the New Password field, enter QueRobot1!.
  15. In the Confirm New Password field, enter QueRobot1!, and then click Submit.
  16. In the Access Settings pane, verify that all check boxes are cleared.
  17. In the upper right of the QueueRegID rule form, click Save. 

6 Remove the inherited application instance of the Work group and robot mapping

  1. From the Dev Studio header, click Launch portal > Robot Manager to open the Robot Manager portal.
  2. In the navigation header, click Settings to display the Settings page.
  3. On the Settings page, click Robot Registration to display the decision tables.
  4. From the list of Decision Table instances, expand Work group and robot mapping. 
    Work group and robot mapping expanded
  5. In the Work group and robot mapping section, click the More icon and select Remove. A Remove configurations window is displayed.
  6. In the Remove configurations window, click Submit. The MyTown RM now inherits the values from the Pega Robot Manager decision table. 
    Work group and robot mapping complete
  7. From the list of decision tables, collapse Work group and robot mapping. 

7 Update the Work group and requestor mapping

  1. From the list of decision tables, expand Work group and requestor mapping.
  2. In the Work group and requestor mapping section, click the More icon and then select Edit. 
  3. In the first row of the of section, click the Edit icon. The Work group and requestor mapping window is displayed. 
    WG and Requestor Mapping edit 1
  4. In the Requestor Identifier field, delete the RMSysAdmin text and enter or select InquireRegID.
  5. On the Work group and requestor mapping window, click Submit.
    WG and Requestor Mapping edit 2
  6. In the Work group and requestor mapping section, click Add row. The Work group and requestor mapping window is displayed.
  7. In the Work group and requestor mapping window, click Add requestor.
  8. In the Requestor identifier field, enter or select SvcReqRegID.
  9. In the Work group identifier field, enter or select Service Request WG@MyTownRM, and then click Submit.
    WG and Requestor Mapping edit 3
  10. In the Default Work group section, leave the default value. 
  11. On the Work group and requestor mapping section, click Save. 

Available in the following mission:

Return to mission

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