RPA Scheduling Service processing flow
This article describes what happens when you use the Pega RPA Scheduling Service and is provided for informational purposes. By using the RPA Scheduling Service, you can schedule Robotic Processing Automation (RPA) sessions when you are using Pega Robotic Automation versions 8.0 SP1 2018 and earlier.
If you are using Pega Robotic Automation versions 8.0 SP1 2019 and later, the Pega RPA Service provides additional features, such as the ability to use Pega Robot Manager version 6 and later and run RPA robots in OnDemand mode. For more information, see Pega RPA Service processing flow
- The system administrator uses the Pega Robotic Automation Credentials Manager utility (credmgr.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.
- The system administrator configures the RpaSchedule.json file. This file contains the information that the RPA Scheduling Service needs to schedule one RPA Runtime session per weekday.
- The system administrator ensures that the Pega Windows Auto-Login Scheduling service (OpenSpan.WinLogon.Service.exe) is running. This service must be restarted after you make changes to the RpaSchedule.json file.
- The system administrator leaves the virtual machine on the Windows lock screen.
- At the time specified in the RpaSchedule.json file, the RPA Scheduling Service logs the virtual machine in to a Windows session. The system uses the user credentials that are defined in the Credentials Manager to log in to this session.
- The RPA Scheduling 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.
- Robotic Automation Runtime starts. As with any RPA session, the RPA master registration credentials are used to begin the registration process. Robotic Automation Runtime uses the computer name as its operator ID. Robotic Automation Runtime retrieves its work group from the CommonConfig.xml file. For more information, see Common Configuration Settings.
- Robotic Automation Runtime registers with the Pega Robot Manager.
- Robotic Automation Runtime gets its package assignment.
- Robotic Automation Runtime retrieves the package from the Package Server.
- Robotic Automation Runtime begins to process work assignments.
- The RPA Scheduling Service notifies Robotic Automation Runtime when it is time for its session to end. The RPA Scheduling Service retrieves information about how long the session lasts from the RpaSchedule.json file.
- Robotic Automation Runtime finishes processing its current work assignment and then shuts down.
- The RPA Scheduling Service logs out of the Windows session user.
For more information, see Pega Robot Manager version 5.1.
Published February 12, 2019 — Updated March 13, 2019