SR-D47414 · Issue 513077
"Use null if empty" checkbox honored for GetSelectValues
Resolved in Pega Version 8.2.5
When Report Definition rule uses parameters as a value for filter criteria, a moderate performance warning was generated: ''Some of your filters are using a parameter with the "Use null if empty" option NOT selected. Please ensure that you do pass the parameter. Otherwise, the filter will be dropped entirely and execution of the report will result in very poor performance. If you do not want this behavior, select the "Use null if empty" option.'' When the "Use null if empty" checkbox was selected as suggested, the "Select values" button gave an empty list of possible values. This was traced to refactoring work done on Select Values which changed it to be backed by a Report Definition and Grid instead of a List View: the option was intended to be only temporarily disabled, but was missed. To correct this, the activity pzGetSelectValues has been updated to honor the checkbox and appropriately disable the "Use null if empty" option on the selected filter on the temporary copy of the report definition before it is executed.
SR-D48173 · Issue 515339
Resolved hang caused by cancelling report calculation
Resolved in Pega Version 8.2.5
When dragging a calculation into the report editor filter area, clicking X on the cancel modal that appeared caused a JavaScript exception to occur. This exception later prevented the ability to click the "done editing" button on the report. This has been resolved by modifying the pzpega_report_rafpopup.sj -- doRefresh API to pass the correct argument to reload the section API.
SR-D48442 · Issue 514046
ExportMode parameter sent to resolve duplicate rows in Export to Excel
Resolved in Pega Version 8.2.5
On performing Export to Excel for a report definition, duplicate rows were being exported for a column which had a TextAreaWithExpandSmall UI Control. Investigation showed that this control was looking for the exportmode parameter, which was not being sent. This parameter is now being sent.
SR-D49491 · Issue 515319
Updated sorting parameters order for better matching
Resolved in Pega Version 8.2.5
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-D50805 · Issue 516098
Eligibility Builder Select Values search box is visible
Resolved in Pega Version 8.2.5
On the Offer rule, Eligibility tab in Eligibility Builder, when creating an eligibility row that used ' {property} equals {value}', on the Select values menu -> Existing values, there was no search box to navigate the list of property prompt values. This was traced to the select values gadget not using the "Prompt value" to be displayed as its label, and has been fixed.
SR-A100292 · Issue 270065
Select Values from join properly displayed on chart
Resolved in Pega Version 7.3
In charts of report definitions using a join, properties with prompt select values were displaying the actual data rather than the prompt values. This was due to a handling difference for properties from joins: before rendering the chart, report data was copied to a page that did not have the correct pxObjClass, creating the assumption that the property applied to @baseclass. To resolve this, the class will be set on the page that contains the target property.
SR-A103079 · Issue 273545
Check added for RD date time values
Resolved in Pega Version 7.3
An exception was generated when running RD by choosing the relationship for a datetime property as "Is not null" in filter conditions before displaying the data. This has been fixed with the addition of a check for the date time value.
SR-B10828 · Issue 282620
Surrounding spaces trimmed from property labels to ensure localization
Resolved in Pega Version 7.3
Property labels in the add reports screen were not localized because the value was given as "Contact Channel " with a trailing space. To resolve this, the pzReportExplorerNode control has been updated to trim leading and trailing spaces before performing localization.
SR-B11379 · Issue 281867
Backwards compatibility added for imported RDs to ensure Export to PDF option given
Resolved in Pega Version 7.3
After upgrade, the Export to PDF option was not visible under actions. This occurred when the Report Definition exported from an earlier version did not contain the property "pyUI.pyUserInteractions.pyShowDataOnly" in the rule XML, causing the 'when' rule pzShowExportToPDFLink to be evaluated to false. To correct this, the pzUpgradeOnOpen Data-transform has been modified to create the pyShowDataOnly property and assign it to false if it was not present or if the value is empty/null so the Export option will appear as expected.
SR-B11675 · Issue 284417
Cursor correctly changes to hand in Report Wizard popup
Resolved in Pega Version 7.3
The hand icon was not displaying as expected when the cursor was placed on the Search icon in the "Report Wizard" pop up window. This has been fixed.