Table of Contents

Article

Robotic Processing Automation Scheduling service

Pega® Robotic Automation includes a Scheduling service that you use to schedule Robotic Processing Automation (RPA) sessions. With the RPA Scheduling service, you can log in to a virtual machine as a Windows user and start or stop Pega Robotic Automation Runtime. You can also specify daily schedules for a robot to better manage production systems whose applications are not available all day and every day.

To specify the login information to use to identify the Windows system user when starting the virtual machine, use the Pega Robotic Automation Credentials Manager utility. The RPA Scheduling service only works under the following scenarios:

  • You are logged in as the user that you specified in the Credentials Manager, or
  • No users are logged in.

Before you can use the Robotic Automation Scheduling service, complete the following tasks:

  1. Installing the Robotic Automation Scheduling service
  2. Enabling the RPA Scheduling service to simulate a Secure Attention Sequence
  3. Configuring Robotic Automation Runtime in Robotic Process Automation implementations
  4. Scheduling when a Robotic Process Automation robot runs

The following steps describe how the RPA Scheduling service works:

  1. 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.
  2. 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.
  3. The system administrator makes sure 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.
  4. The system administrator leaves the virtual machine on the Windows lock screen.
  5. 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.
  6. 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.
  7. 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.
  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 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.
  13. Robotic Automation Runtime finishes processing its current work assignment and then shuts down.
  14. The RPA Scheduling service logs out of the Windows session user.

For more information, see Pega Robot Manager version 3.

Published September 1, 2017 — Updated July 6, 2018


100% found this useful

Have a question? Get answers now.

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