Skip to main content

Using Pega Robot Simulator

4 Tasks

55 mins

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

Scenario

MyTown wants to use Pega Robot Simulator to mimic a multi-robot scenario for specific work groups and assignment types. By simulating the scenario, testers can understand any obstacles that can arise and provide the ability to test how Pega Robot Manager™ works under different conditions. Testers intend to use the Pega Robot Simulator to check the connection and configuration of Robot Manager, its supporting applications, and robots to ensure proper alignment with business needs for the MyTown RM application.

To finalize testing, complete the following tasks:

  • Download and configure the Pega Robot Simulator to start Robotic Process Automation (RPA) Services for each case type and register robots for each work group.
  • Create cases for each assignment type to test the access of the robots to the correct assignment types based on the settings configurations.
Note:  Enter the Operator IDs and passwords in the Robot Simulator precisely as you created them in the previous challenges because they are case-sensitive. If you receive any errors, verify your Operator ID and password and re-enter as needed. You might need to restart the Robot Simulator to re-enter the credentials. 

The following table provides the credentials you need to complete the challenge:

Role User name Password
Robot Manager System Administrator RMSysAdmin myt0wn@pp1

 

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 Verify the case type installation

  1. In the Pega Platform™ instance for the challenge, enter the following credentials:
    1. In the User name field, enter RMSysAdmin.
    2. In the Password field, enter myt0wn@pp1.
  2. In the navigation pane of Dev Studio, click Case Types.
  3. Confirm that the two new case types, Inquiry and Service Request, are associated with the assignment types and work groups.
    The Inquiry and Service Request case types.

2 Configure the RPA Simulator

  1. Click the following link to download the Robot Simulator .zip file to a local directory.
  2. Extract the contents of the Robot Simulator ZIP file to theRobotManagerChallengeAssets folder.
Note: Create a new folder on your desktop named RobotManagerChallengeAssets if you have not already done so in the Configuring Organization Structure challenge. 
  1. From the extracted Pega Robot Simulator folder, double-click PegaRPARobotSimulator.exe to start the application.
  2. In the Enter the robot server url field, on the RPA Simulator Login window, enter https://#######.pegaacademy.net/prweb to connect the Robot Simulator to your Pega training instance.
    Robot Simulator version 22.
  3. In the Enter credentials used to start robots section, enter the login information:
    1. In the User field, enter InquireRegID.
    2. In the Password field, and InqRobot1!
  4. Under the Enter credentials used to create cases section, enter the login information:
    1. In the User field, enter QueueRegID.
    2. In the Password field, and QueRobot1!
      Note: The entered credentials are case-sensitive.
      The login credentials for the Robot Simulator.
  5. On the RPA Simulator Login window, click Login.
    The RPA Simulator Main window is displayed.
    Note: If you receive an error message that states you cannot connect or that your credentials are rejected, confirm the URL and the user and password values.

3 Start RPA Services for Service Request and Inquiry

  1. In the upper-left corner, click File > Load simulation template.
    Load simulation template.
  2. In the File Explorer, select the default_profile.sim file, and then click Open.
    Select the default simulation template.
  3. In the RPA Simluator Login window, click Login to load the template.
    Loading the simulation template.
  4. In the RPA Simulator Main window, in the Select a RPA Service list, select REQRPA.
  5. Click Start.
    The RPA Simulator Configure RPA Service window is displayed.
    The RPA Simulator Configure RPA Service window.
  6. In the RPA Simulator Configure RPA Service window, clear the Use Default credentials check box.
    1. In the User field, enter SvcReqRegID
    2. In the Password field, enter SvcRobot1!
      Start RPA Service window
    3. Leave all default values as is and click Start RPA Service to close the configuration window and update the RPA Service Status.
      RPA Service status update
  7. In the header of Dev Studio, click Launch portal > Robot Manager to open the Pega Robot Manager dashboard.
    Launch the Robot Manager Portal.
  8. In the navigation pane of Robot Manager, click the Unattended RPA > Work groups to access the Work groups landing page.
  9. On the Work groups landing page, click Service Request WG to access the work group details page.
    The Work groups screen of Pega Robot Manager showing assigned robots.
  10. On the work group details page, confirm that the SRQ00 and SRQ01 robots are in the work group in Standby mode.
    The the SRQ00 and SRQ01 robots in standby mode.
    Note: If the robots do not appear in the work group, stop the RPA Simulator Main window, and then exit the Robot Simulator. Validate the credentials for the needed service and attempt to restart.  
  11. Repeat steps 4-10 to start the INQRPA Service by selecting the Use default credentials checkbox in the RPA Simulator Configure RPA Service window. 

    Use default credentials.

4 Process cases with Pega Robot Simulator

  1. In the navigation pane of Robot Manager, click Unattended RPA > Work groups to return to the Work groups landing page.
  2. On the Work groups landing page, click Service Request WG tile. 
  3. In the row for robot SRQ00, click More > Start.
    Start the robot.
  4. In the Start robots dialog box, click Yes to confirm you want to start the selected robot
    The Start robots dialog box.
  5. Refresh the page and verify the status icon changes from light blue to green after the robot starts successfully.
    The startup status for the SRQ00 robot.
  6. Repeat steps 3-4 to begin the Start process for the SRQ01 robot.
  7. Return to the RPA Simulator Main window, and then in the Select a case type list, select MyTownRM-Work-ServiceRequest.
    The MyTownRM-Work-ServiceRequest case type.
  8. Click Create. 
    Creating the case.
  9. Ensure the following options are selected in the RPA Simulator Case Creation window:
    1. Clear the Maintain case load automatically check box.
    2. In the Work queue list, select Service Requests AT@MyTownRM.
    3. In the Cases to create field, enter 10.
    4. Click Start Case Creation.
      ​ Start case creation for service request queue
  10. In the Case Creation confirmation pop-up, click OK.
    Confirm case creation
  11. In the RPA Simulator Case Creation window, click Cancel.
  12. Return to Pega Robot Manager, and then confirm that the 10 cases are in the Assignment Type queue.
    The Service Request work group screen showing ten requests in the queue.
  13. In the Assignment Types section, click Start to begin the queue processing. 
  14. In the Start assignment type dialog box, click Submit.
    Start assignment type.
  15. Confirm that the status message on the assignment type changes from Standby to Running, and that the robots begin processing the cases in the assignment type.
    The running assignment type.
    Note: Processing cases can take a few minutes, and it may be necessary to refresh the page to view an updated list.
  16. After all cases are complete, click Stop to stop the Assignment Type.
    Assignment type stopped
  17. In the Stop Assignment type dialog box, click Submit.
    Stop assignment type dialog box.
  18. Confirm the status message changes from Running to Standby, and that the robots stop processing the cases in the assignment type.
  19. In the Robots section, select the checkbox for both robots.
  20. In the upper-right corner, click More > Stop.
    Stopping the two robots.
  21. In the Stop robots dialog box, click Yes to confirm you want to stop the robots.
    Confirm stop of multiple robots
  22. In the navigation pane of Robot Manager, click Unattended RPA > Robots to access the Robots landing page
  23. On the Robots landing page, verify there are now two robots in Standby mode assigned to the Inquiry work group.
    INQ robots on Standby status.
  24.  Select the INQ00 and INQ01 checkboxes.
  25. Click Bulk actions > Start, and then click Yes to turn on the selected robots.
    Bulk start.
  26. Verify that the robots now have the Started status.
    INQ robots with Started status
  27. In the navigation pane of Robot Studio, click Unattended RPA > Work groups to return to the Work groups landing page.
  28. On the Work groups landing page, click the Inquiry WG tile. 
  29. Repeat steps 7-21 to process cases and stop robots for the Inquiry work queue.

Confirm your work

  1. In the navigation pane of Robot Studio, click Unattended RPA > Robots to access the Robots landing page.
  2. On the Robots landing page, verify there are now four total robots in Standby mode assigned to both the Service Request and Inquiry work groups.
    Verify that all robots are available in the two work groups.
  3. After testing both cases, in the RPA Simulator Main window, in the RPA Service Status section, click Stop on each RPA service to close all simulator services.
    Stopping the robot simulator.
  4. Wait a few minutes, refresh the Robots landing page, and then verify all robots now have the Off status.
    Verify that all robots are off.
  1.  On the Navigation panel, click the operator ID icon and then click Log off.

 



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