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-A2378 · Issue 210254

Added check for missing getFieldValues page in standalone listview

Resolved in Pega Version 7.2

In some installations, executing list view -> getFieldValues as a stand alone generated the error "Failed to find instance @baseclass". This was traced to the "LISTVIEW_getFieldValues" page not being present, and a check has been added to resolve this problem.

SR-A2378 · Issue 211007

Added check for missing getFieldValues page in standalone listview

Resolved in Pega Version 7.2

In some installations, executing list view -> getFieldValues as a stand alone generated the error "Failed to find instance @baseclass". This was traced to the "LISTVIEW_getFieldValues" page not being present, and a check has been added to resolve this problem.

SR-A4717 · Issue 214606

Added handling for Microsoft Internet Explorer double-submit on enter

Resolved in Pega Version 7.2

When using the Microsoft Internet Explorer browser, List view was throwing an error on submission by pressing 'enter keyboard key' while working as expected when using the submit button. This was traced to an Microsoft Internet Explorer issue that fires the 'onunload' event twice if it is redirected from within the event handler, and has been resolved by applying a flag-based condition check while executing to prevent the second firing.

SR-A5424 · Issue 213337

Check added to handle mismatched property names given in referred page

Resolved in Pega Version 7.2

If a property name was provided in a list criteria by referring page name, it generated type mis-match error even though the property was of the same type. Creating a new RD with same criteria avoided this error, but a check has been added to "Validate_Report_Condition" to determine whether the property is a leaf or page property . If it is a page property, the system will prefix that property with a "." to resolve the mis-match issue.

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.

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