Build notes: Pega Synchronization Engine 3.1
Build notes describe the changes that are included in each build that is created for the Pega Synchronization Engine. 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 PRA software. For information on system requirements, review the installation instructions.
Summary of changes
The changes that are included in the various Pega Synchronization Engine builds are listed in the following table.
Item number |
Description |
Assemblies |
---|---|---|
Build 3.1.17.0 — March 17, 2021 — bundled with Pega Robotic Automation 19.1.77.0 | ||
US-356668 US-356679 |
This hotfix updates the Synchronization Server to run on .NET Core 3.1. | All assemblies that are part of the Synchronization Server. |
Build 3.1.16.0 — November 25, 2020 — bundled with Pega Robotic Automation 19.1.69.0 |
||
US-385205 US-386884 |
This hotfix adds elements to the Installer that allow updates to the KeepTryingMinutes key in UpdaterConfig.xml. |
Not applicable |
US-386885 US-390014 |
This hotfix changes how the system interprets the
For more information, see UpdaterConfig.xml. |
Pega.UpdaterService.exe |
US-389262 US-389278 |
This hotfix adds a new product-content manifest file, productsystem.manifest, that supports PostUpdateActions, PostInitializeActions, and PreLoadActions. | Pega.ProductLoader.exe Pega.Updater.Models.dll Pega.Updater.Shared.dll Pega.Updater.Utils.dll Pega.UpdaterService. Downloader.dll |
ISSUE-84054 | This hotfix sets the .exe files to always copy to the latest cache version folder. This change ensures that the .exe file picks up the DLL from the newest folder when running a new version of the product. | Not applicable |
Build 3.1.15.0 |
||
|
The changes in this build were published in 3.1.16.0. |
|
Build 3.1.14.0 — August 19, 2020 — bundled with Pega Robotic Automation 19.1.55.0 |
||
US-373353 |
This hotfix adds the KeepTryingMinutes key to the appSettings section of the Updater.config.xml file. Use this key to specify how the UpdaterService should try to connect to the Updater Server. If you omit this key or enter zero (0), the UpdaterService only attempts to connect once. If you enter 5, for example, the UpdaterService attempts to connect to the Updater Server for five minutes. Install version 3.1.15.0 or later for a one-step installation process. Version 3.1.15.0 and later also prompt you to set the KeepTryingMinutes key. For more information, see UpdaterConfig.xml file.
|
Pega.UpdaterService.exe |
Build 3.1.13.0 — June 29, 2020 — bundled with Pega Robotic Automation 19.1.48.0 |
||
BUG-568248 |
This hotfix ensures that the Pega Synchronization Engine does not contact the Pega Synchronization Server if the base product version is the same as the version that the system is loading. |
Pega.ProductLoader.exe |
EPIC-62548 |
This hotfix adds the Use64bitRuntime and HideSplashScreen keys to the ProductLoader section of the UpdaterConfig.xml file. Use these keys to perform the following tasks:
|
Pega.ProductLoader.exe |
EPIC-58247 |
This hotfix adds the Pega.CacheUpdater utility. Use this utility to load product bundles directly to the cache without using the Pega Synchronization Server. For more information, see Pega.CacheUpdater utility. |
Pega.CacheUpdater.exe |
Build 3.1.12.0 |
||
|
The changes in this build were published in 3.1.13.0. |
|
Build 3.1.11.0 — May 8, 2020 — bundled with Pega Robotic Automation 19.1.41.0. |
||
BUG-547933 |
This hotfix ensures that the C:\ProgramData\Pegasystems folder and the C:\ProgramData\Pegasystems\Updater folder have consistent permissions. Both folders provide permissions to the system and everyone groups by default. Administrators can control the permissions on these folders. |
Not applicable |
Build 3.1.10.0 — April 24, 2020 — bundled with Pega Robotic Automation 19.1.39.0. |
||
US-349950 |
This hotfix allows the Pega Synchronization Engine and Server to resolve files in subfolders, in order to support potential future functionality. |
Pega.Loader.exe Pega.ProductLoader.exe Pega.Updater.dll Pega.UpdaterService.exe Pega.UpdaterService.Downloader.dl |
Build 3.1.9.0 — March 07, 2020 — bundled with Pega Robotic Automation 19.1.32.0. |
||
US-344908 |
This hotfix modifies the Pega Synchronization Engine so that it can acquire and wait for information about multiple Runtime sessions from the Pega RPA Service. The RPA Service creates this information when it starts multiple Robot Runtime sessions. Use the new MultipleRuntimeMutexTimeoutSecs option in the ProductLoader section of the UpdaterConfig.xml file to specify the length of time that the Pega Synchronization Engine should wait for this information. |
UpdaterConfig.xml |
Build 3.1.8.0 — February 26, 2020 — bundled with Pega Robotic Automation 19.1.31.0. |
||
US-343299 |
This hotfix enables you to use the Pega Synchronization Server in a Citrix mixed-mode environment on the Citrix server. Robot Runtime now passes parameters to the Pega.Loader.exe file so that the Pega Synchronization Engine can switch to the correct Robot Runtime version for the package that the client loads. |
Pega.ProductLoader.exe |
Build 3.1.7.0 — February 7, 2020 — bundled with Pega Robotic Automation 19.1.27.0. |
||
EPIC-60451 |
This hotfix ensures that the executable path for a Pega Windows Service is encapsulated with quotes when updated. This encapsulation resolves potential security vulnerabilities. |
Pega.UpdaterService.Downloader.dll |
Build 3.1.6.0 — February 7, 2020 — bundled with Pega Robotic Automation 19.1.26.0. Pega Robotic Automation build 19.1.26.0 was removed. Download 19.1.27.0, which contains Pega Synchronization Engine 3.1.7.0. All features and fixes from build 3.1.6.0 are available in build 3.1.7.0.
|
||
US-338705 |
This hotfix ensures that when Robot Manager is not in use, the Runtime PackageDownloader creates a package manifest based on the StartUp project settings defined in the RuntimeConfig.xml file. In addition, Pega Synchronization Engine no longer rejects a manifest that does not have a JSON assignment. These changes allow you to launch products based on additional settings when Robot Manager is not connected. |
Pega.PackageDownloader.exe |
US-338531 |
This hotfix adds robotindex support to the Synchronization Engine product loader command line options. This addition is needed when running multiple Runtime sessions on a single machine. |
Pega.ProductLoader.exe |
Build 3.1.5.0 — November 22, 2019 — bundled with Pega Robotic Automation 19.1.19.0. |
||
US-325572 |
This hotfix adds updated copyright information for all versioned files. |
All versioned files |
BUG-519844 |
This hotfix removes a requirement for an internet connection. |
Installer MSI files |
Build 3.1.4.0 — August 19, 2019 — bundled with Pega Robotic Automation 19.1.7.0. |
||
US-318439 |
This hotfix enhances the Pega Synchronization Engine Product.Loader to support the workgroup and operatorId command line options. The Pega.ProductLoader.exe program passes these options to the Package Downloader and Robot Runtime. |
Pega.ProductLoader.exe |
Build 3.1.3.0 — August 02, 2019 — bundled with Pega Robotic Automation 19.1.4.0. |
||
US-311230 |
This hotfix modifies the Pega Synchronization Engine setup wizard to allow you to select which application the Pega.Loader will launch: Robot Runtime or Agile Desktop. You can also accept the default, which lets the Pega Synchronization Server specify the application to launch. If you install Pega Synchronization Engine from the command line, use these command line parameters:
-p Runtime -e OpenSpan.Runtime.exe
-p Runtime -e OpenSpan.AgileDesktop.exe The default is to let the Pega Synchronization Server specify the application to launch. There are no command line parameters for this option.
|
Not applicable |
US-315717 |
This hotfix modifies the Pega.ProductLoader so that it accepts all command line parameters and continues if you include parameters that are not expected. |
Pega.ProductLoader.exe |
Build 3.1.2.0 |
||
|
The changes in this build were published in 3.1.3.0. |
|
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 Pega Synchronization Engine for Pega Robotic Automation 19.1. |
Not applicable |
Updated on March 17, 2021