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-A4489 · Issue 214635

Corrected filter application error in SQL generation

Resolved in Pega Version 7.2

If a report definition containing class joins used a grid repeat with filtering enabled, selecting a filter value from the pick list for any column did not apply the filter. Examination of the SQL revealed a flaw in the generated query that caused an incorrect order of evaluation of AND and OR operators in the WHERE clause, and this has been corrected.

SR-A1523 · Issue 214800

Corrected unexpected seedlist locking

Resolved in Pega Version 7.2

In some cases, it was not possible to delete a seedlist from an environment due to erroneous locking caused by duplicate primary keys being entered. To resolve this, the system will check for the error and bypass save if appropriate.

SR-A7904 · Issue 216498

Corrected variable incrementing in GetCustomPropsForTreeGrid

Resolved in Pega Version 7.2

An error with the incrementation of a variable in pzGetCustomPropsForTreeGrid was resulting in the same Joined Class being returned again and again. This has been corrected.

SR-A6581 · Issue 216111

Encoding added to handle multi-byte characters in file names exported to Excel

Resolved in Pega Version 7.2

If a report title contained multi-byte characters such as Chinese fonts, exporting the report to Excel resulted in an incorrect file name is incorrect. To correct this, UTF-8 encoding has been added to pzViewExcelData to handle these characters.

SR-A2832 · Issue 211426

Expressions allowed in trend report config

Resolved in Pega Version 7.2

Configuring a trend report using an expression for the summary view caused the execution error "Failed to find a 'RULE-EDIT-INPUT' with the name; no rules with this name were found in the rulebase". This has been resolved by reworking the 'if' condition in the JS method editInput.

SR-A6872 · Issue 216420

Filtering modified to allow searches with two-step filtering

Resolved in Pega Version 7.2

If a List View was being filtered by two columns, entering the first filter value into the "Search" text box (as opposed to selecting values from the pick list) in the filter popup caused the second filter operation to not return any results. This was an issue with the crossScriptingFilter, which has been modified to allow two-step filtering.

SR-A5814 · Issue 216307

Resolved blank list page navigation

Resolved in Pega Version 7.2

If there was a backslash (escape characters) in the double quoted report parameters passed from the section, no data was shown when navigating to the next page in a ListView report. This was caused by multiple encodings of the escape characters while moving back and forth between the pages. The filtering has been updated to correct this issue.

SR-A6387 · Issue 216159

Resolved errors while saving in summary view

Resolved in Pega Version 7.2

While saving an existing summary view, the error message "Output type: ** Your Field Definition does not match with Chart Definition. Verify it" was generated if only the third column was selected at the time of the save. In addition, selecting any checkbox other than the first in the chart's data tab during save of the summary throws an error. These issues have been fixed.

SR-A3914 · Issue 212709

Added null check to handle uninitialized object in prweb/PRServlet URL

Resolved in Pega Version 7.2

A NPE error was seen on the UI and in PegaRULES log when accessing PegaRULES URL when PRPC was deployed as an enterprise application and transaction type was "CMT" or "Container". This was found to be caused by the prthread object in EngineAPIclass not being initialized at the time the operation was called, and a null check has been added to handle such cases.

SR-A4720 · Issue 212436

Corrected focus for tabbing Ruleset inclusion data entry

Resolved in Pega Version 7.2

Data entry for "RuleSets To Include" was behaving unexpectedly when using keyboard-only input: when a value was entered in the "Minimum Version" text field, pressing TAB on the keyboard shifted focus from the next textbox to the top of the sheet due to a row-refresh added for app context. 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