Table of Contents

Article

RPA Service processing flow

This article describes what happens when you use the Pega RPA Service and is provided for informational purposes. By using the RPA Service, you can schedule Robotic Processing Automation (RPA) sessions when you are using Pega Robotic Automation versions 8.0 SP1 2019 and later. For best results, upgrade to version 8.0 SP1 2025 or later.

If you are using Pega Robotic Automation versions 8.0 SP1 2018 and earlier, you must use the RPA Scheduling Service. For more information, see RPA Scheduling Service processing flow. You must have Pega Robotic Automation 8.0 SP1 2019 or later to use Pega Robot Manager version 6. For more information, see Pega Robot Manager version 6.

The following steps describe how the RPA Service works:

  1. The system administrator uses the Pega Robotic Automation Credentials Manager utility (credmgr.exe or credmgrui.exe) to store user credentials. These credentials are used to log in to the Robotic Automation Runtime virtual machine.
    • Windows session user credentials are used to log in to the virtual machine.
    • Robotic Automation Runtime session user credentials are used to define the user who starts the openspan.runtime.exe application.
    • Registration Operator credentials are used to communicate with Robot Manager.
  2. If you set the mode to Scheduled, the system administrator configures the RpaSchedule.json file. This file contains the information that the RPA Service needs to schedule one RPA Runtime session per weekday.
  3. The system administrator ensures that the Pega RPA Service (OpenSpan.WinLogon.Service.exe) is running. Restart the service any time you change the credentials, the RPAService.config file, or the RpaSchedule.json file.
  4. The system administrator leaves the virtual machine on the Windows lock screen.
  5. The system uses the user credentials that are defined in the Credentials Manager to log in to this session:
    • If you set the mode to Scheduled, at the time specified in the RpaSchedule.json file, the Pega RPA Service logs the virtual machine in to a Windows session.
    • If you set the mode to OnDemand, Pega Robot Manager uses the RPA Service to start and stop the robots.
  6. The RPA Service creates a task in the Windows Task Scheduler to start the Robotic Automation Runtime session within the next few minutes as the Robotic Automation Runtime user that is specified in the Credentials Manager.
  7. Robotic Automation Runtime starts. As with any RPA session, the Registration Operator is used to begin the registration process. Robotic Automation Runtime uses the robotName value in the CommonConfig.xml file as its operator ID. Robotic Automation Runtime retrieves the workgroup information from the CommonConfig.xml file. For more information, see Common Configuration Settings.
  8. Robotic Automation Runtime registers with the Pega Robot Manager.
  9. Robotic Automation Runtime gets its package assignment.
  10. Robotic Automation Runtime retrieves the package from the Package Server.
  11. Robotic Automation Runtime begins to process work assignments.
  12. The RPA Service notifies Robotic Automation Runtime when it is time for its session to end. The RPA Service retrieves information about how long the session lasts from the RpaSchedule.json file.
  13. Robotic Automation Runtime finishes processing its current work assignment and then shuts down.
  14. The RPA Service logs out of the Windows session user.

Tags:

Published February 12, 2019 — Updated March 27, 2019


100% found this useful

Related Content

Have a question? Get answers now.

Visit the Pega Support Community to ask questions, engage in discussions, and help others.