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.

INC-131942 · Issue 574322

Orphaned CSS reference removed from DisplayReport harness

Resolved in Pega Version 8.2.8

An intermittent invalid CSS error was appearing in the DisplayReport harness when an operation resulted in the regeneration of the harness content. This was traced to a reference to the workform_pyReportingSkin CSS, which was used in old reporting features and is not in use anymore. The reference has been removed to resolve this issue.

INC-135719 · Issue 580689

Corrected reference exception for filter on a grid sourced from a parameterized report definition

Resolved in Pega Version 8.2.8

An Invalid Reference Exception was thrown after attempting to apply a filter on a grid sourced from a parameterized report definition. This was traced to work done to allow cross-scripting filters to allow filters to contain special characters, and has been resolved.

INC-140110 · Issue 600399

Large filter values accepted in Report Definition edit

Resolved in Pega Version 8.2.8

Report definition edit filter values were not accepting large comma separated values properly. This has been resolved by modifying the logic in RRFilters_Logic to use ReportFilter.getReportFilters.

INC-143191 · Issue 596470

Scheduled tasks landing page shows all tasks

Resolved in Pega Version 8.2.8

Due to pzGetScheduledTasks listview having a hardcoded limitation of 500 records to be fetched, not all scheduled tasks were being shown in the scheduled tasks landing page. This has been resolved by modifying the pyCreateSummary activity to use a newly created Report Definition to fetch data instead of list view.

INC-144756 · Issue 602724

Security improved for searches

Resolved in Pega Version 8.2.8

Authentication requirements have been added to activities associated with searching.

INC-120343 · Issue 573075

Explicit parent added for descendants in subreport to correct summary

Resolved in Pega Version 8.2.8

When using a Report Definition with a Summarize column and a subreport with join class, it was not considering implementation class work objects. As a result, the prepared values were only partially computed. This was traced to the SubReport in SetQuery not having reference to a parent for the descendants classes, and has been resolved by explicitly setting the parent value.

SR-D90400 · Issue 563185

Explicit parent added for descendants in subreport to correct summary

Resolved in Pega Version 8.2.8

When using a Report Definition with a Summarize column and a subreport with join class, it was not considering implementation class work objects. As a result, the prepared values were only partially computed. This was traced to the SubReport in SetQuery not having reference to a parent for the descendants classes, and has been resolved by explicitly setting the parent value.

INC-119669 · Issue 562586

Special character handling added to filters for table sourced with parameterized RD

Resolved in Pega Version 8.2.7

Filters were not working on a table when sourced with a report definition which accepted a parameter value containing special characters (Eg: S&P). This has been resolved by using StringUtils.reversibleCrossScriptingFilter in the pzGetGridColUniqueValues activity to allow filters to contain special characters.

SR-D56590 · Issue 525300

Notification option for change of search nodes removed from Cloud

Resolved in Pega Version 8.2.7

The search landing page for Pega Cloud was displaying a checkbox to enable sending automatic emails if the search node was modified. As the description of the notification 'Notify on change of search host nodes' suggests, this option is to send notifications only when a search host node has been modified(addition/removal) from the search landing page. This is not applicable for the automatic addition/removal of search nodes that happens on starting the node. As the addition/removal of nodes is not allowed from the search landing page on Cloud environments, this option is not applicable for Cloud and the checkbox has now been removed for that environment.

SR-D81496 · Issue 547169

Data Social tag class FTS index query improvements

Resolved in Pega Version 8.2.7

A query intended to select from the link tag table to see if any cases were linked to the tag in question and then index the tag change was causing performance issues. Investigation showed that checking tag associations during FTS indexing fetched all matching rows from the table even though one was sufficient. To resolve this, the query will be created with max result count = 1, fetching up to 2 rows from the table.

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