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-D15261 · Issue 487511

Added ability to edit or SaveAs out-of-the-box 'Case Volume' report

Resolved in Pega Version 8.1.6

It was not possible to perform Edit or Save As to a Private category for the Pega out-of-the-box report 'Case Volume', which is under the Public category 'Case Metrics'. This was traced to certain out-of-the-box report definitions being saved with a pz prefix which does not support the "Save As" functionality, and has been resolved by adding a Property-Set step above "Call pxCreateRecord" to set .pyRuleAvailable to "Yes".

SR-D21808 · Issue 490282

Filter values retained when editing a report with custom filters

Resolved in Pega Version 8.1.6

After running a report, if some filter values were selected and then the Edit Report button was clicked and simulated data and actual data fields were toggled, the filter values were lost when exiting the report editor. In the Edit Report Page, trying to drag a new filter condition was not working and the Change logic buttons were not visible. These functions worked as expected when a custom Filter section was not used. This was traced to the custom filter page being cleared in the pzCreateCustomFilterPage activity where the step for creating new page should be skipped if it already exists. To resolve this, a parameter will be set to show if the report was rerun in "reRunReport", and a check has been added in pzCreateCustomFilterPage to see if the report was rerun before running the other 'when' conditions.

SR-D11289 · Issue 484054

Mobile support added for Report Definition chart slider

Resolved in Pega Version 8.1.6

Because the report definition ruleform chart slider was historically not supported on mobile devices, enabling the touch API in Google Chrome resulted in confusing behavior where the slider worked in mobile mode on a laptop but not on a mobile device. This was due to the chart slider being a jQuery UI slider component (ui-slider) that was built without support for mobile devices. An enhancement has now been added to utilize the jQuery UI Touch Punch library, which makes jQuery UI components mobile-friendly, by loading it at the start of pzRRChart.

SR-D15089 · Issue 485331

Handling added for single quotes in custom DateTime controls when using Export to Excel

Resolved in Pega Version 8.1.6

A previously resolved issue with the timezone not being appended to datetime when exporting to Excel if a custom control was used has been further updated to better handle single-quote strings in custom DateTime controls.

SR-D15469 · Issue 487524

Export to Excel formats the DateTime filter for localized values

Resolved in Pega Version 8.1.6

When exporting to Excel, filter criteria were given in GMT rather than the localized timezone. This was caused by the implementation of localizeDateTimeString method not formatting the output string for the locale/timezone during export to Excel, and has been corrected to display the localized filter values when the filter values include DateTimes.

SR-D22885 · Issue 494165

Added check for empty class properties to report scheduler

Resolved in Pega Version 8.1.6

A report that was looking for events in the most recent X hours by using the "Difference In Hours" filter function ran in the foreground but failed with an exception when running under the scheduler. The same report ran as expected in background without the filter. This was traced to a classname property not being set on the clipboard, and has been resolved by adding a check for empty classes on the clipboard when scheduling a report.

SR-D15275 · Issue 490025

Report title displayed properly when prompting for filter changes

Resolved in Pega Version 8.1.6

Launching a report from the report browser showed a blank for "Report tab title" if the option "Prompt for filter changes before displaying report" was checked. This has been corrected by adding pzRDWinTitle to the harness Code-Pega-List.pzRRDisplaySection so it will display the name of the report when prompting for filter changes.

SR-D22386 · Issue 495016

Corrected Report Definition SQL firing before filtering

Resolved in Pega Version 8.1.6

When a report definition had "prompt for filter changes" enabled, it was still querying the database when displaying the filtering prompt. This was causing a performance issue, and has been resolved by upadting runReport to no longer run the query before displaying the filter page.

SR-D2400 · Issue 438741

Security for ExporttoPDF tool process improved

Resolved in Pega Version 8.1.6

In order to increase system security, the tool process around iframe HTML tags used in generating a PDF with chart image data has been improved.

SR-D26190 · Issue 496521

Corrected decimal format for Export to Excel and removed null values inserted in empty columns

Resolved in Pega Version 8.1.6

When viewing a report in the viewer or exporting it to Excel, cells that did not have a value in them appeared empty. However, pulling the report into a third-party tool generated an error related to the apparently empty cells. This was caused by the system being set to populate the excel cell with empty string values in cases where there was no value present in the property, causing the error with the third-party tool. To resolve this, the export to Excel code has been modified so that it does not generate anything for cells that have null/empty value. In addition, exported reports containing decimal columns were displayed in an incorrect format, using '0.' instead of '0' . This has also been corrected.

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