Skip to main content

Resolved Issues

View the resolved issues for a specific Platform release.

Go to download resolved issues by patch release.

Browse release notes for a selected Pega Version.

NOTE: Enter just the Case ID number (SR or INC) in order to find the associated Support Request.

Please update your bookmarks. This site will be discontinued in Dec 2024.

Pega Platform Resolved Issues for 8.1 and newer are now available on the Support Center.

SR-A90037 · Issue 260736

Handling added for BIX command line parameter combination

Resolved in Pega Version 7.2.2

Running a series of comma separated extract rules to an XML file from the Pega BIX command line using -i parameter resulted the incorrect elements in the corresponding XSD file. Running each extraction separately generated the XSD file correctly. This was caused by multiple XML extracts run using -i and without -a and -p resulting in incorrect XSD schema generation for one of the extracts, and handling has been added to ensure the proper generation.

SR-A23970 · Issue 249825

RecreateIndexesForClass OOM resolved

Resolved in Pega Version 7.2.2

Running the activity RecreateIndexesForClass after creating a new Declare index rule in order to reindex old existing work objects was causing a JVM OOM error that required a restart. This was traced to the API fetching all of the records at once to reindex and save, and has been resolved by modifying the function to do an Obj-browse of all the instances and reindex/save the instance one by one.

SR-A23686 · Issue 248675

Support extended for NUMERIC types in RD SQL joins/filters

Resolved in Pega Version 7.2.2

Support has been extended for NUMERIC types in Report Definitions, more specifically to support references to NUMERIC properties in join and filter conditions in RDs using SQL Server 2012, by updating the IDENTITY column type handling in the RUF pzCheckCompatibilityOfColumnTypes function.

SR-A91225 · Issue 259591

Support extended for NUMERIC types in RD SQL joins/filters

Resolved in Pega Version 7.2.2

Support has been extended for NUMERIC types in Report Definitions, more specifically to support references to NUMERIC properties in join and filter conditions in RDs using SQL Server 2012, by updating the IDENTITY column type handling in the RUF pzCheckCompatibilityOfColumnTypes function.

SR-A102616 · Issue 272058

Apache Struts JARS updated to improve security

Resolved in Pega Version 7.2.2

The Apache Struts JARs have been updated to resolve the following potential security vulnerabilities: The REST plugin in Apache Struts 2 2.3.20 through 2.3.28.1 allows remote attackers to execute arbitrary code via a crafted expression. Apache Struts 2 2.3.20 through 2.3.28.1 mishandles token validation, which allows remote attackers to conduct cross-site request forgery (CSRF) attacks via unspecified vectors. The URLValidator class in Apache Struts 2 2.3.20 through 2.3.28.1 and 2.5.x before 2.5.1 allows remote attackers to cause a denial of service via a null value for a URL field.

SR-A99141 · Issue 270060

Class visibility of System-Ruleset-Index made Tenant Only

Resolved in Pega Version 7.2.2

The class visibility of System-Ruleset-Index has been modified to Tenant Only.

SR-A99858 · Issue 266990

Added config for size of Hazelcast async thread pool

Resolved in Pega Version 7.2.2

The default size of the async thread pool was calculated by Hazelcast as a multiple of the number of CPU cores, so on vary large servers (which support many JVMs) each JVM had many more threads than necessary and performance issue were noted. To resolve this, an enhancement has been added to allow the maximum asynchronous thread pool size to be configured through a prconfig.xml setting called "Hazelcast/async/thread/count".

SR-B2504 · Issue 272623

pxCommitDateTime BIX extraction more robust

Resolved in Pega Version 7.2.2

The exported XML file was not including the pxCommitDateTime column even when that column was included in the BIX extraction. This was traced to the site trying to perform the commit on the same work object more than once: performing the commit the second time caused the previous value to be overridden by the new commitdatetime. That led to the pxCommitDateTime not being stored in the BLOB, and since BIX extracts the data from source table's BLOB, it cannot extract the value of pxCommitDateTime. To resolve this, the source query that BIX uses has been modified to get both pzPVStream and pxCommitDateTime (if the column is present in the source table) and use the value of pxCommitDateTime from the resultset while writing to the output file.

SR-A98078 · Issue 270393

FlowActionPlayback supports Activity with class name

Resolved in Pega Version 7.2.2

The logic in FlowActionPlayback has been updated to support a pyActivity parameter that also contains the class name. The classname will be trimmed and the primarypage class name only will be used for further activity resolution.

SR-A95046 · Issue 263375

Master Agent exception resolved

Resolved in Pega Version 7.2.2

The Master Agent generated an exception while expanding a property with backreferences on a ReadOnly ClipboardPage while trying to estimate the size of all Node level data Pages. This has been fixed.

We'd prefer it if you saw us at our best.

Pega.com is not optimized for Internet Explorer. For the optimal experience, please use:

Close Deprecation Notice
Contact us