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-D50787 · Issue 520484

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

Resolved in Pega Version 8.2.6

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 519237

Eligibility Builder integer sorting revised

Resolved in Pega Version 8.2.6

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-D53176 · Issue 541794

Error when adding function filter will persist

Resolved in Pega Version 8.2.6

When an exception occurred while adding a filter in the report viewer, the error was shown but cleared due to an immediate refresh of the parent section. Analysis found that step2 of pzGetFiltersFromContent was failing, after which the error was shown, the section reload happened, and the error disappeared. To resolve the error being cleared prematurely, the pzOnLoadReloadReport control has been modified so that when there are messages on the top level page (pyReportContentPage), a parameter will be set on HarnessContextMgr to not to clear them during the next refresh call.

SR-D55801 · Issue 524292

Corrected HTML error generated on export to PDF

Resolved in Pega Version 8.2.6

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-D65256 · Issue 528006

DisplayCommandMenu holds value during runtime filter changes

Resolved in Pega Version 8.2.6

In report definition, under report viewer tab, the 'enable column command menu' option was disabled. When the report was launched, the menu was not displayed for each column as expected; after applying the filter changes, the column menu options were unexpectedly displayed. This was traced to previous work done on the implementation of the navigation menu for auto-generated grids. Because pyDisplayCommandMenu is exposed on the ruleform itself, disabling the command menu from the ruleform caused changes to the filter to reset and pyDisplayCommandMenu was set back to true regardless of what was configured on the ruleform. To correct this, updates have been made to ensure that pyDisplayCommandMenu is not overwritten when there are changes to a filter during runtime.

SR-D65327 · Issue 534570

Backspace keydown handler updated for all textinput modes

Resolved in Pega Version 8.2.6

Attempting to use the Backspace key to remove input from a number cell (either Integer or Decimal) did not work. When the action was performed by a Manager, the Backspace key works as expected. Investigation showed the logic in the keydown handler for the backspace key in pega_report_events.js was only ignoring the e.preventDefault() call when the textinput node type was text, not number or other input types. To correct this, the keydown handler has been updated so the backspace key in pega_report_events.js maintains the default backspace functionality for all textinput modes, not just those of type 'text'.

SR-D76943 · Issue 541371

SmartInfo icon functional for reports

Resolved in Pega Version 8.2.6

After enabling Smart Info for a list Report definition, the activity was not getting called and section was not getting displayed. Investigation traced this to encryption added in an earlier version which caused the SmartInfo API to receive a parameter in an unexpected format. Because this incompatibility would affect all APIs not compatible with the encryption, this encryption for the API has been reverted.

SR-D69098 · Issue 534042

Export to Excel works for for report definition with duplicate columns

Resolved in Pega Version 8.5

After adding a date column to a report definition (2nd column in the report), the data displayed correctly in the UI but Export to Excel failed with the error "Section 'pzRDExportWrapper' execution error on page '' of class 'Rule-Obj-Report-Definition'. : The Reference .pyDateValue(2) is not valid." This was traced to an out of bounds exception thrown if there were two or more columns with the same calculation. When preparing for export, the column with the duplicate calculation would not get added to the map of report UI fields. To resolve this, the system has been updated to allow report definition columns with the same calculation to be properly mapped to a UI field.

SR-D69108 · Issue 543846

Handling added for drag-and-drop with deleted report templates

Resolved in Pega Version 8.5

After adding a new report, an error appeared when trying to use drag-and-drop to add a column (Page List) from the Data Explorer in the report browser. This was traced to refactor work done to use the Record API throughout reporting: the ruleset on new reports was not being reset from a Pega- ruleset to an application ruleset, causing columns the referenced properties defined outside the platform to be rejected. This use case was missed because case types define their own report templates on creation, but in this scenario those had been deleted. To resolve this, the system has been updated to call pxChooseBestRuleset from pxShowReport in order to enable the use of properties defined in the application prior to saving the report.

SR-D91038 · Issue 553165

Corrected report with combo chart in Case Manager portal

Resolved in Pega Version 8.5

After adding the required columns a report in the report viewer and then adding a combo chart and dropping the summarized column on the y-axes and group by column on X-axis, clicking on "done editing" generated the error "pyUI.pyChart: You must have at least two Aggregate Columns in the chart series .pyUI.pyChart.pyDataAxis(1).pyChartOutputType: A Combo chart requires at least 1 Chart Type be a Column". Investigation showed that the second DataAxis page was getting deleted in the pzCleanChartDataAxis activity, causing the validation to fail. This has been resolved by adding a 'when' rule to "pzChartIsSingleY" that checks for "SingleYAxisClustered" chart and refers the same in pzCleanChartDataAxis to skip the data axis deletion.

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