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-202480 · Issue 699082

Resolved report filter section freeze

Resolved in Pega Version 8.6.4

When opening a report with a count column, changing the order of one of the report columns resulted in the report freezing and requiring the report to be closed and re-run. This was traced to a double filter popup appearing that did not close after the column sorting, which happened if the report definition was configured as a summary with an aggregated column such as "Count” combined with a "Do not display group headings" setting on the Report Viewer tab. To resolve this, a new step has been added in the Activity pzPopulateSortOrder to call the pzCancelFilterLogicChanges activity.

INC-205075 · Issue 698741

Updated variable handling for filter logic to avoid reuse

Resolved in Pega Version 8.6.4

When adding the property "ItemStatus" as a filter for a report, the validation message: "This property does not exist or has no column mapping" appeared. This was traced to an empty caption for a class join property used in

INC-209399 · Issue 708570

Handling added for indexing items exceeding Kibana max size

Resolved in Pega Version 8.6.4

Indexing cases was generating errors from Kibana indicating "Failed to index document: java.lang.IllegalArgumentException: Document contains at least one immense term in field="_m_MailBody" (whose UTF8 encoding is longer than the max length 32766), all of which were skipped." To resolve this, if an embedded property exceeds the max length defined by Kibana, it will be truncated at 32k bytes in order to allow indexing to proceed.

INC-211726 · Issue 705071

Parameter logic updated for metrics activity counter

Resolved in Pega Version 8.6.4

An error was causing the PushCDHMetrics agent to fail. This was traced to an undefined parameter in the activity which was used as a counter, and has been resolved by replacing it with a local variable of type integer. In addition, an agent has been added to support publishing the model metrics.

INC-172944 · Issue 662828

Skin rule circumstancing article added

Resolved in Pega Version 8.6.4

An article on skin circumstancing best practices has been added to https://collaborate.pega.com to aid in working with this functionality.

INC-176462 · Issue 657412

Dashboard widget drilldown section adjusts dynamically

Resolved in Pega Version 8.6.4

While trying to expand the drilldown columns, text was overlapping due to the grid not adjusting the large size of data dynamically. This was traced to an unnecessary CSS rule being applied to set max-height which broke the styling. This has been resolved by removing the height limitation on detail cells.

INC-180100 · Issue 662894

Scrollbar persists for multiselect

Resolved in Pega Version 8.6.4

Selecting more than 20 values in the multiselect control caused the scrollbar to disappear. This has been resolved by removing a custom popover height calculation.

INC-183672 · Issue 701868

Corrected vertical scroll bar for iPad Mashup page

Resolved in Pega Version 8.6.4

After update, the vertical scroll bar shown on the Web Mashup page in Apple Safari on iPad continued to increase and showed excessive blank space. This was caused by the iframes,section height being considered as the iframe height, and has been resolved by setting the section height as 'auto' in case of mashups.

INC-186081 · Issue 675207

Report filter popup displays correctly

Resolved in Pega Version 8.6.4

The filter popup was not displayed on the report column for which the filter was intended. This has been resolved by updating the popover js to fix the overlay issue.

INC-187196 · Issue 680749

Resolved Ajax popup alert for optimized iOS table

Resolved in Pega Version 8.6.4

When using an application on iOS with a section that contained at least 3 tables with 'optimize code allow' set to true, refreshing caused the error "AJAX request failed. Reason: communication failure" to be displayed. This has been resolved by adding an update which will skip the alert for the pzBuildFilterIcon activity when triggered from pzpega_ui_template_grid_helpers.

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