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 note: beginning with the Pega Platform 8.7.4 Patch, the Resolved Issues have moved to the Support Center.

SR-A3897 · Issue 209254

Resolved authentication requirements in activity pzSetQueryDefaults for SSO setup

Resolved in Pega Version 7.1.9

Code-Security.InitialProfileSetup does not need authentication to run, but during the SSO login it calls Code-Pega-Requestor.pzSetQueryDefaults which was hard-coded to require authentication. This was an error, and the SetQueryDefaults activity no longer requires authentication.

SR-B79734 · Issue 344352

Summary report count fixed when using filter prompt

Resolved in Pega Version 7.4

The summary data count was not getting updated in a report unless the "Prompt for filter changes before displaying report" option on Report Viewer tab (Actions -> Refresh) was unchecked. This was an error in the refresh code related to the display prompt filter check and has been corrected.

SR-C2920 · Issue 344845

Summary report count fixed when using filter prompt

Resolved in Pega Version 7.4

The summary data count was not getting updated in a report unless the "Prompt for filter changes before displaying report" option on Report Viewer tab (Actions -> Refresh) was unchecked. This was an error in the refresh code related to the display prompt filter check and has been corrected.

SR-A692 · Issue 205611

Resolved duplicate portal open when using Microsoft Internet Explorer 11

Resolved in Pega Version 7.1.9

When using Microsoft Internet Explorer 11, trying to access the My Group tab in the links 'Manage Operator Schedules and Profiles' was not displaying the screen correctly on click of any operator or workbasket and an extra portal window was opened. This was a browser-specific dynamic container issue where the lack of an explicit type=button declaration was causing a form submit that triggered a main page refresh. That declaration has been added.

SR-B65131 · Issue 330322

Fixed 'when' rules for showing privileged escalation buttons

Resolved in Pega Version 7.4

Privileged escalation was displayed for a user with access to manager reports due to missing 'when' rules for hiding the Add report/Add category buttons. This has been fixed.

SR-A2268 · Issue 206068

Summary drilldown now uses entire screen

Resolved in Pega Version 7.1.9

While running summary view, the drilldown data only appeared on half of the screen and the other half was blank. This was caused by the window height logic for the drilldown using offsethright for the window size. This has been changed in RULE-OBJ-HTML RULE-OBJ-SUMMARYVieW DRILLDOWN to use view port height to make the results occupy all the window.

SR-B85544 · Issue 337433

Fixed RD fail for Japanese characters

Resolved in Pega Version 7.4

Report definition was failing when the Class name contained Japanese characters. This was an issue with the use of default encoding (now deprecated) and an update has been made to ensure the use of 'UTF-8' encoding for URLs.

INC-182375 · Issue 664344

Report filter description correctly displayed

Resolved in Pega Version 8.7

When a function alias was used in the filter of a report definition without the caption and with some value assigned, the FilterName was not getting displayed when the report was run. This has been resolved by updating RRFilters_Logic.

INC-147643 · Issue 605388

Corrected filtering logic for Report Definition with declarative join

Resolved in Pega Version 8.4.4

When using a report definition with declarative join enabled, running the report produced the correct results, but filtering on any other column resulted in all values being shown. This has been resolved by modifying the logic used for pzGetGridColUniqueValues.

INC-144103 · Issue 599682

Updated filter logic for filtering on a DateTime column

Resolved in Pega Version 8.4.4

When a class join was used in a report definition, the error "The Filter Logic used in the report is invalid" appeared while filtering rows of a report definition results on a DateTime column. This was a missed use case, and has been resolved by modifying pzGridSortPaginate to convert the data type value into the proper casing.

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