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-125113 · Issue 203182

Localized labels displaying in Safari

Resolved in Pega Version 7.2

Localized headers were not displaying properly on Safari browsers if the Fat List mode was used for the grid headers. Rendering worked as expected using Field Value mode. This was an issue with localized labels not rendering properly when the width of the Safari browser is reduced, and has been fixed. In addition, an issue with the header values being added dynamically instead of using constant values for a mobile browser grid using responsive mode has also been fixed.

SR-A7487 · Issue 221276

Better Japanese font handling in CreatePDF smart shape

Resolved in Pega Version 7.2

The CreatePDF smart shape was not able to properly parse Japanese font characters in section data. This has been corrected by changing the default font to 'MS PGothic' which better supports Japanese.

SR-A8298 · Issue 218280

Resolved connection reset error on nested grid harness refresh

Resolved in Pega Version 7.2

When the Harness contains nested Grids, refreshing the harness would throw ?Bad Request -Connection reset? error. This was caused by a large number of hidden fields created by Grids being included in the request query string, thus exceeding the GET request size limit. The issue is now fixed by not adding the hidden fields to the query string when Refresh is called without Submit.

SR-A8430 · Issue 218096

Resolved connection reset error on nested grid harness refresh

Resolved in Pega Version 7.2

When the Harness contains nested Grids, refreshing the harness would throw ?Bad Request -Connection reset? error. This was caused by a large number of hidden fields created by Grids being included in the request query string, thus exceeding the GET request size limit. The issue is now fixed by not adding the hidden fields to the query string when Refresh is called without Submit.

SR-A2361 · Issue 214536

XSS fix updated for IAC with CSRF tokens

Resolved in Pega Version 7.2

After updating to address a potential XSS security issue, some problems were found with using IAC with CSRF tokens in the pathinfo. Additional checks have been added to handle this scenario.

SR-125113 · Issue 193442

Localized labels displaying in Safari

Resolved in Pega Version 7.2

Localized headers were not displaying properly on Safari browsers if the Fat List mode was used for the grid headers. Rendering worked as expected using Field Value mode. This was an issue with localized labels not rendering properly when the width of the Safari browser is reduced, and has been fixed. In addition, an issue with the header values being added dynamically instead of using constant values for a mobile browser grid using responsive mode has also been fixed.

SR-125113 · Issue 216785

Localized labels displaying in Safari

Resolved in Pega Version 7.2

Localized headers were not displaying properly on Safari browsers if the Fat List mode was used for the grid headers. Rendering worked as expected using Field Value mode. This was an issue with localized labels not rendering properly when the width of the Safari browser is reduced, and has been fixed. In addition, an issue with the header values being added dynamically instead of using constant values for a mobile browser grid using responsive mode has also been fixed.

SR-A7487 · Issue 221274

Better Japanese font handling in CreatePDF smart shape

Resolved in Pega Version 7.2

The CreatePDF smart shape was not able to properly parse Japanese font characters in section data. This has been corrected by changing the default font to 'MS PGothic' which better supports Japanese.

SR-A12341 · Issue 224036

Corrected implementation for DataFlow key non-match

Resolved in Pega Version 7.2

If a DataFlow Dataset configured against a Report Definition had a property key name that was not identical to the column name in the database table, the Dataflow failed to execute with error " Incorrect implementation for Report Definition as a data flow source. Property-to-database table column mapping was not applied correctly". The implementation has been fixed to resolve this issue.

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