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.

SR-A23916 · Issue 253818

BIX extract WO handling corrected

Resolved in Pega Version 7.2.2

After upgrade, a BIX report was not working correctly due to the difference in work object handling. During BIX extract, the currently extracted WO was being maintained on a tempPage that was not subsequently being used for the lookup. This has been fixed.

SR-A76413 · Issue 254770

Custom datatypes import support added to SQL RD

Resolved in Pega Version 7.2.2

After upgrade, external classes of type 'text' mapped to an external DB were throwing an error while executing report definition. This was due to the method used to get the column type, and the logic has been updated to correct this.

SR-A52484 · Issue 251721

BIX Extract retains pre-upgrade filenames and columns

Resolved in Pega Version 7.2.2

After upgrade, extract rules were created with underscores replacing dashes in the original filenames and ExtractIndentifier and ExtractDateTime columns were added to the output csv file. This was an inadvertent change related to enhancements made to filename conventions, and has been corrected with the prconfig "bix/retainOriginalFileNameForCSV" to retain the filename as provided in the extract rule and the prconfig "bix/ignoreAdditionalColumnsInCSV" to not add the new additional columns pxExtractIdentifier and pxExtractDateTime when upgrading rulesets.

SR-A24412 · Issue 249993

Calendar icon display fixed for Microsoft Internet Explorer11

Resolved in Pega Version 7.2.2

Calendar icons were not displayed in a data table in Microsoft Internet Explorer 11 due to the browser not supporting the icon rendering. A meta tag has been added in the ReviewHarness to correct this.

SR-A23686 · Issue 249793

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-A75946 · Issue 252101

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-A96852 · Issue 264159

Resolved OOM error when adding VDB DNode

Resolved in Pega Version 7.2.2

A memory leak was found relating to JBDC PreparedStatement objects (char arrays allocated to hold database query results) used when VBD loads its data partitions. This has been fixed with the addition of code to close the PreparedStatement objects created when loading Actuals partition data.

SR-A99782 · Issue 266250

XSS vulnerability closed in Warning Justification Text field

Resolved in Pega Version 7.2.2

A potential XSS vulnerability has been addressed in the Warning Justification Text field.

SR-A96515 · Issue 267504

Added handling for Qualsys security scan

Resolved in Pega Version 7.2.2

A stack overflow error was being generated when running a Qualsys vulnerability security scan on servers hosting IBM WebSphere and Pega, resulting in two of the three Pega nodes in production becoming unresponsive and requiring a restart. This was caused by the third party tool connecting to port 7003, which is used by Stream data set server, and sending unknown requests. To avoid this, the system has been updated to not send back a response if the channel is closed

SR-A79502 · Issue 253855

Corrected ability to add DNode port via prconfig

Resolved in Pega Version 7.2.2

Adding DNode Port via prconfig was not taking effect due to the configuration values being stored as strings, but the code which reads the storage port configuration treats the setting as integer. 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