Build notes: Pega RPA Service 3.1
Build notes describe the changes that are included in each build that is created for the Pega RPA Service. Before you install one of these builds, familiarize yourself with the changes, new features, and resolved issues that are listed in the following table.
To download a build, see Download Pega RPA software. For information on system requirements, review the installation instructions.
Summary of changes
The changes that are included in the various Pega RPA Service builds are listed in the following table:
Item number |
Description |
Assemblies |
---|---|---|
Build 3.1.16.0 — January 25, 2021 — bundled with Pega Robotic Automation 19.1.73.0 |
||
BUG-594960 | This hotfix resolves an issue where a disclaimer screen would block the Server Bot Framework from starting a robot. | SchedulerDefinitions.xml Pega.RpaService.Common.dll Pega.RpaService.Loader.exe Pega.RpaService.Scheduler.exe |
Build 3.1.15.0 — September 14, 2020 — bundled with Pega Robotic Automation 19.1.61.0 |
||
EPIC-63220 |
This hotfix updates the endpoints for all calls that the Pega RPA Service makes to provide support for Pega Robot Manager 8.5. |
Pega.RPAService.Common.dll |
Build 3.1.14.0 — July 17, 2020 — bundled with Pega Robotic Automation 19.1.50.0 |
||
EPIC-63194 |
This hotfix modifies the CredMgr.exe program to ensure that it includes the same functionality available from the CredMgr UI. The following changes were made:
|
OpenSpan.Security.dll |
BUG-575637 |
This hotfix adds the *.exe.config files to the version manifest/bundle and includes these files in the cache version folder with their corresponding .exe files. |
N/A |
Build 3.1.13.0 — June 01, 2020 — bundled with Pega Robotic Automation 19.1.44.0 |
||
EPIC-62795 |
This hotfix changes the Credential Manager UI for the Pega RPA Service to ensure that the application displays correctly when you have the screen resolution of 1280 x 720. |
CredMgrUI.exe |
EPIC-62787 |
This hotfix includes the following changes:
|
Pega.RpaService.Common.dll |
Build 3.1.12.0 — April 24, 2020 — bundled with Pega Robotic Automation 19.1.39.0 |
||
EPIC-62070 |
This hotfix includes the following changes:
|
SchedulerDefinitions.xml RpaService.config Pega.RpaService.Common.dll Pega.RpaService.Loader.exe Pega.RpaService.Scheduler.exe Pega.RpaService.Service.exe |
US-355454 |
This hotfix modifies the installer to adjust permissions on the RPAService folder in the ProgramData folder to permit the Scheduler program to write log information. |
PegaRPAServiceSetup.exe |
US-358012 |
This hotfix enhances credential provider support for Robot Runtime and the Robotic Process Automation (RPA) Service in several ways:
For more information, see Integrating a Client Credential Provider. |
OpenSpan.Security.dll |
Build 3.1.11.0 — April 13, 2020 — bundled with Pega Robotic Automation 19.1.38.0 |
||
BUG-551870 |
This hotfix ensures that the Pega RPA Service uses the value defined for the ScheduledTaskStartBoundary key in the RPAService.config.xml file to schedule the runtime task. |
Pega.RpaService.Common.dll |
BUG-552492 |
This hotfix ensures that the Pega RPA Service uses the BaseURL key from the AppSettings section in the RPAService.config.xml file. The RPA Service uses the value that you specify for this key, if present, instead of the BaseURL key value in the RobotManager section of the CommonConfig.xml file. |
Pega.RpaService.Common.dll |
Build 3.1.10.0 — March 07, 2020 — bundled with Pega Robotic Automation 19.1.32.0Pega Robotic Automation builds 19.1.30-19.1.34 were removed from Digital Delivery after we discovered several bugs, some of which were resolved in RPA Service 3.1.11.0. Please download 19.1.38 from Digital Delivery. This build contains RPA Service 3.1.11.0. All features and fixes from RPA Service 3.1.10.0 are available in 3.1.11.0.
|
||
US-317631 |
This hotfix adds support for running multiple Runtime sessions on a single Windows machine if the machine supports RDP connections. To specify the maximum number of robots that you want to register with Robot Manager, use the new maximumRobots option in the RobotManager section of the CommonConfig.xml file. This hotfix also updates the CredMgrUI.exe and CredMgr.exe programs to support multiple Runtime sessions. When you set the maximum number of robots to two or more, a new RobotIndex field appears in the CredMgrUI.exe and CredMgr.exe programs when you specify the WindowsUser and RuntimeUser keys in the CredentialManagerConfig.xml file. Ensure that each robot has unique WindowsUser and RobotIndex entries. This hotfix also adds the following options to the AppSettings section in the RPAService.config.xml file:
This hot fix removes the Framework .dll dependency except for .dll files that are related to credential providers.
|
CommonConfig.xml |
US-319231 |
This hotfix adds the ConsecutiveInvalidLoginLimit option to the AppSettings section of the RPAService.config.xml file. Use this option to limit the number of failures allowed before the RPA Service stops trying to register with Pega Robot Manager. For example, if you enter 10, the RPA Service attempts to register with Pega Robot Manager up to10 times. If it fails to register 10 times, you must then restart the RPA Service. |
CommonConfig.xml |
US-349008 |
This hotfix resolves a security vulnerability in the Pega RPA Service by changing the default behavior for handling locked screens during unattended robotic sessions when running in Scheduled mode. |
CommonConfig.xml |
Build 3.1.9.0 — February 7, 2020 — bundled with Pega Robotic Automation 19.1.27.0 |
||
BUG-538964 |
This hotfix adds security enhancements to resolve potential vulnerabilities. |
Installer changes |
EPIC-59173 |
This hotfix adds security enhancements to resolve potential vulnerabilities. |
OpenSpan.Branding.dll |
ISSUE-72086 |
This hotfix adds a missing registration payload password field so that the RPA Service can register with Robot Manager. |
Not applicable |
Build 3.1.7.0 — February 7, 2020 — bundled with Pega Robotic Automation 19.1.26.0Pega Robotic Automation build 19.1.26.0 was removed. Please download 19.1.27.0 that contains RPA Service 3.1.9.0 All features and fixes from RPA Service 3.1.7.0 are available in 3.1.9.0.
|
||
EPIC-60451 |
This hotfix implements full support of the BeyondTrust credential provider for Robot Runtime. You can use your existing BeyondTrust portal to provide credentials for the registration operator, Windows user, Runtime user, ASO manager, and Credential Store. |
CommonConfig.xml |
Build 3.1.6.0 — December 4, 2019 — bundled with Pega Robotic Automation 19.1.20.0 |
||
ISSUE-68867 |
This hotfix removes the requirement of an internet connection during the installation process. |
Installer MSI files |
US-328600 |
This hotfix adds support to RPA Service for a new robot profile endpoint in Robot Manager. It reverts to an existing endpoint when a new endpoint does not exist. |
Pega.RpaService.Service.exe |
Build 3.1.5.0 — October 11, 2019 — bundled with Pega Robotic Automation 19.1.14.0. |
||
BUG-512701 |
This hotfix resolves an issue that could occur in the CommonConfig.xml file if you enabled the CredentialManager server and set the providerType to DPAPI. |
OpenSpan.Security.dll |
Build 3.1.4.0 — September 27, 2019 — bundled with Pega Robotic Automation 19.1.13.0. |
||
BUG-508009 |
This hotfix adds the ScheduledTaskStartBoundary configuration setting to the RPAService.config.xml file. Use this setting to ensure that the start boundary does not occur before the scheduled task. |
OpenSpan.WinLogon.Scheduler.dll |
US-323726 |
This hotfix adds the BaseURL key to the AppSettings section in the RPAService.config.xml file. The system uses the value that you specify in this key instead of the BaseURL key value in the RobotManager section of the CommonConfig.xml file. This key only applies to the Pega RPA Service.
|
CredentialManagerConfig.xml |
US-323723 |
This hotfix enables you to get and set custom credentials by using the IClientCredentialProvider interface. To set up custom credentials, use the CredentialManager server options in the CommonConfig.xml file, and make corresponding entries in the CredentialManagerConfig.xml file. For the credential provider, set the providerType attribute in the CredentialManagerConfig.xml file to Client and include values for the assemblyName and className attributes. |
CredentialManagerConfig.xml |
Build 3.1.3.0 — August 19, 2019 — bundled with Pega Robotic Automation 19.1.7.0. |
||
US-318438 |
This hotfix modifies the Pega RPA Service to use the correct argument format when passing the workgroup option to the Pega.Loader.exe program. In addition, this hotfix also updates the Pega RPA Service to use a signed version of the Framework binaries and modifies the CredMgrUI.exe program to ignore empty credentials. |
FrameworkBinaries/OpenSpan.Branding.dll |
ISSUE-25935 |
This hotfix adds updated copyright information for all versioned files. |
All versioned files. |
Build 3.1.2.0 — June 28, 2019 — bundled with Pega Robotic Automation 19.1.2.0. |
||
US-267153 |
This hotfix modifies the Credentials Manager (CredMgr.exe/CredMgrUI.exe) (DPAPI) tools to accept the workgroup field when you save credentials. This information can be retrieved by the Pega RPA Service or Pega Robot Runtime. This hotfix also adds workgroup support to the CyberArk and DPL credential providers. These changes allow you to retrieve different Registration Operator, Windows User, and Runtime User credentials based on your current workgroup. |
Pega.RpaService.Common.dll |
ISSUE-62354 |
This hotfix adds a default heartbeat interval of 30 seconds. This default is used if the heartbeat interval is not set on Pega Platform. This hotfix also modifies the log message if an exception is thrown. |
Pega.RpaService.Service.exe |
BUG-486961 |
This hotfix corrects a problem that prevented the system from correctly reading the value of the enabled attribute in the log4net section of the RPAService.config.xml file. |
Pega.RpaService.Common.dll |
Build 3.1.1.0 — May 31, 2019 — bundled with Pega Robotic Automation 19.1.1.0 |
||
Not applicable |
This is the initial released build of the Pega RPA Service for Pega Robotic Automation 19.1. |
Not applicable |
Updated on March 4, 2021