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.

INC-139130 · Issue 591861

Tab Headers accessible in Report Filter with keyboard

Resolved in Pega Version 8.6

Tab Headers such as "Available Values" were not accessible with a keyboard in the modal to select values for Report Filters. Instead, the focus marker directly shifted to content and toggling between Tabs was not possible. Investigation showed that at runtime for report definitions, the value for prevElement was null, which threw an error and caused the rest of the function to not run. This has been corrected by adding null checks for prevElement and newElement in the function tabClickCallback in the pega_report_events js file.

INC-139295 · Issue 588139

Report Shortcuts resolve datapage parameter references

Resolved in Pega Version 8.6

After upgrade, no results were displayed in case manager portal report browser. This was traced to a data page value that was not resolved at runtime when a data page was used in the report definition shortcut to pass a parameter value. Investigation showed this was due to a change made for v8.4 to correct an issue with data page variables that were not persisting if a report was made with pre-exisiting filters. To resolve this, the logic related to pzResolveCopyFilters has been updated.

INC-140110 · Issue 600397

Large filter values accepted in Report Definition edit

Resolved in Pega Version 8.6

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-140353 · Issue 592214

Updated filter logic for filtering on a DateTime column

Resolved in Pega Version 8.6

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.

INC-141322 · Issue 594512

Resolved drill up doubling the filter box

Resolved in Pega Version 8.6

When opening a report with a visual graph, clicking on one of the filtered options, leaving this box open (not submitting it) and then clicking on a bar in the visual graph of the report showed the contents of the graph, but then clicking on the report link to go back to the report overview caused a doubled filter box to be displayed. The report would then have to be reopened before being able to continue. The problem was that the value of .pyUI.pyConfigSecToShow was still set to "filter" after the drill down. When the drill back up happened, the report was trying to show the filter configuration section from before but the context was no longer available and it failed. This has been resolved by adding a call to pzCancelFilterLogicChanges in pzDrillUpReport to set the filters to the previous values and reset the value of pyConfigSecToShow.

INC-143191 · Issue 596468

Scheduled tasks landing page shows all tasks

Resolved in Pega Version 8.6

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-144103 · Issue 599680

Updated filter logic for filtering on a DateTime column

Resolved in Pega Version 8.6

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.

INC-144333 · Issue 603261

Documentation updated for reindexing of specific classes

Resolved in Pega Version 8.6

The documentation for rebuilding search indexes has been updated to specify that selected class is the only one taken into account for re-indexing; child classes need to be added separately.https://community.pega.com/knowledgebase/articles/system-administration/85/rebuilding-search-indexes-user-interface

INC-145810 · Issue 599464

BIX log shows correct corrupted BLOB pzInskey

Resolved in Pega Version 8.6

An update has been made to ensure the correct inskey is shown in the BIX logs for a corrupted BLOB.

INC-147166 · Issue 601800

AvailableProperties cleanup added after save

Resolved in Pega Version 8.6

The Report filter value auto-complete was displaying an incorrect list of values. This was traced to pyAvailableProperties not being cleaned up after being created and used in a prior process, and has been resolved by ensuring pyAvailableProperties is removed on save so it can be cleanly built when needed.

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