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-B11796 · Issue 281383

Column filters updated to escape values with angle brackets

Resolved in Pega Version 7.3

When attempting to apply a filter on a Repeat Grid or Report Definition column, the filter popup showed blank values for column values starting with the "" character. This was due to the browser treating "" as an HTML tag, and the pzGetGridColUniqueValues function has been updated to escape these values.

INC-140272 · Issue 595252

Report definition performance improvement

Resolved in Pega Version 8.2.8

Performance issues were seen with the pzOperatorsByWorkGroup report definition. This was traced to the report definition is adding an UPPER function for edit filter properties which caused it to take more time to run when combined with an ignore case check in the filters of the Report Definition. This has been corrected.

INC-140272 · Issue 595250

Report definition performance improvement

Resolved in Pega Version 8.5.2

Performance issues were seen with the pzOperatorsByWorkGroup report definition. This was traced to the report definition is adding an UPPER function for edit filter properties which caused it to take more time to run when combined with an ignore case check in the filters of the Report Definition. This has been corrected.

INC-141789 · Issue 601052

PD4ML upgraded

Resolved in Pega Version 8.5.2

After upgrade, a functionality to generate letters in PDF format had an image size discrepancy between portrait and landscape mode. Investigation showed that the physical dimensions were not preserved by PD4ML v4.0.6; this has ben resolved by upgrading PD4ML to 4.0.9fx1.

SR-D5388 · Issue 456426

Corrected dropdown focus issue with dynamic layouts

Resolved in Pega Version 8.3

The focus was not retained on the dropdown field whose property was used in the dynamic layout for the refresh condition. Investigation showed that in pzpega_ui_doc_focus.js, the function "focusNextElement" was setting pega.u.d.gFocusElement set to null after the first load. This has been corrected.

SR-D39302 · Issue 507982

Report name in tab uses localization

Resolved in Pega Version 8.4

After creating a field value with field name as pyCaption to localize the report definition name, the title in the report definition tab was not translated. This was traced to Step 1 of the activity displayReport using an old localization function, and has been resolved by changing the localization of document title to use pyCaption.

SR-D69914 · Issue 531739

Cookie logging restored

Resolved in Pega Version 8.4

As part of security updates, Cookies were restricted from being logged. However, this caused some business use cases such as a custom function call to obtain the list of cookies that are present in the application to stop working. To resolve this, the cookie logging restriction has been reverted.

SR-D47685 · Issue 514647

Cookie logging restored

Resolved in Pega Version 8.4

As part of security updates, Cookies were restricted from being logged. However, this caused some business use cases such as a custom function call to obtain the list of cookies that are present in the application to stop working. To resolve this, the cookie logging restriction has been reverted.

INC-164944 · Issue 636292

Logic updated to handle decision trees over 64k

Resolved in Pega Version 8.5.4

Logic updated to handle decision trees over 64kAn exception was thrown when decision trees reached the 64K size limit. This has been resolved by modifying the logic in the DecisiontableMethodBody Rule-Utility-Function where the split size nPropRowLimit is based on the number of columns.

SR-D5388 · Issue 461278

Corrected dropdown focus issue with dynamic layouts

Resolved in Pega Version 8.1.6

The focus was not retained on the dropdown field whose property was used in the dynamic layout for the refresh condition. Investigation showed that in pzpega_ui_doc_focus.js, the function "focusNextElement" was setting pega.u.d.gFocusElement set to null after the first load. This has been corrected.

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