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-D49491 · Issue 515320

Updated sorting parameters order for better matching

Resolved in Pega Version 8.4

After choosing sorting for a column in a main summary report and then drilling down, a message appears indicating no records found even though there were results. The query showeds that the values for the 'where' clause were sent in the wrong order, causing a parameter mismatch. This has been resolved with an update to get the iterator before sorting so parameters match up correctly.

SR-D49667 · Issue 516473

Filtered By Label read by JAWS in report browser

Resolved in Pega Version 8.4

When using Firefox, any FilteredBy text in the Report Browser was not being read by JAWS. This was traced to Firefox interpreting the filters in the Report Viewer as not having any distinguishing accessibility label, and has been resolved by adding aria roles to the filters in the Report Viewer.

SR-D50569 · Issue 515437

Primary page paramter explictly set to resolve fix/edit Scheduled Tasks issue

Resolved in Pega Version 8.4

After upgrade, the top section of report details was getting blanked out when using the Reporting | Components | Scheduled Task to open a report and "update" it to fix issues. This was an unintended side effect of updating the Review harness to display the Perform harness when clicking Update, which was done to correct an earlier issue with UI validations when using the out of the box schedule report functionality. To resolve this, pxScheduleTaskWrapper has been updated to explicitly set the parameter page according to the primary page's values when not in the report browser.

SR-D50787 · Issue 520485

Excel time values will default to server datetime if operator time zone is null

Resolved in Pega Version 8.4

After upgrade, a scheduled report that contained a column using pxDateTime that was supposed to use EST instead used GMT when run and exported to Excel. This has been resolved with an update that will default to using the time zone of the server If the time zone of the operator is empty or null.

SR-D50819 · Issue 519238

Eligibility Builder integer sorting revised

Resolved in Pega Version 8.4

In 'Offer' on the Eligibility tab, the Builder was sorting integer properties by the value of the integer as a text string rather than the whole number. Example: 1, 10, 12, 13, 100, 2, 20, 29, 299, 3 instead of the expected 1, 2, 3, 10, 11, 12, 20, etc. This was traced to the system sorting the results using tools.sortPageList() in order to sort by localized (string) value, which is not appropriate for values of any type other than string. To resolve this, the system will skip the manual sort step for numeric columns since the values are appropriately sorted by the database.

SR-D55289 · Issue 524108

FusionCharts upgraded to resolve drill down issues

Resolved in Pega Version 8.4

Drill down reports were not working when the results were displayed with huge data that came up with a scroll bar or if the report was scrolled down and a drill down was attempted when the scroll bar was in the bottom or middle of the scroll line. The hover icon was different i.e., the hand icon was replaced with arrow icon, or sometimes the hand icon displayed without showing the data. The tooltip was also not displaying as expected when hovering on the chart. It was possible to drill down when the scroll bar was in the top or the focus was moved outside the chart and brought back in again. This was traced to bugs in the FusionChart libraries, and has been resolved by upgrading to FusionCharts 3.14.0-sr.1.

SR-D55801 · Issue 524293

Corrected HTML error generated on export to PDF

Resolved in Pega Version 8.4

After exporting a report to PDF, the PDF could be viewed but repeated instances of the error "<th> missing ‘>’ for end of tag" were logged. This was traced to missing the closing '>' for th in the pzRRDataListHeaderRow HTML rule when "Enable column command menu" is unchecked in ReportViewer options, and has been corrected.

SR-D58552 · Issue 522088

Report Definition filter editing shows all values correctly

Resolved in Pega Version 8.4

After launching a report, certain values were not populated on the pop-up when editing the filters or the commas separating the values did not appear. This was traced to the activity pzGetSelectedValues containing an older implementation of column type checking, causing it to report some embedded property references as being of type "Included Page" instead of the type of the ultimate property. This has been resolved by updating step 1 to only use this logic if pyDataType is not set, which should already be set for all filters and columns, and the formatting has been corrected.

SR-D65937 · Issue 528980

Support added for calling Export to Excel directly from RD

Resolved in Pega Version 8.4

When using Export to Excel directly from a report definition, a date column specified using pxDatetime was shown as applied date format in the resulting Excel file. The column was formatted as expected if the export was called from an activity. This was traced to the recent refactoring of Export to Excel: it was not expected that it would be called directly, but rather that it would be invoked from a report viewer ruleform. In order to support this direct use, step calls have been added to the pzRDExportWrapper activity to call pzMergeAutoGen before the engine call. This step will merge the pyModes pages from pxDateTime control.

SR-D18725 · Issue 488208

OrgUnit delete works as expected

Resolved in Pega Version 8.4

After creating two organization units such as Unit1 and Unit11 on the same level and mapping one operator to Unit11, attempting to delete Unit1 resulted in an error indicating the operator had to be deleted first even though unit1 had no operator associated with it. This was traced to Obj-List performing a 'like' check instead of exact match check for the deletion, and has been resolved by updating the ValidateDelete activity to do obj-browse instead of obj-list.

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