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.