SR-B96629 · Issue 347927
Read-only values display in review harness
Resolved in Pega Version 7.4
A pxDropDown control was configured to use different values for the property and display values that were sourced from a Data Page, which in turn was sourced from a report definition. The display property value was retrieved via a joined class on the report and referenced using pxPage().PropertyName syntax. When the control was rendered on the Review harness in read only mode, the display value was not showing even though the property was set. This was due to the pageGroups caption property for the dataPage not being resolved in template_display. To correct this, two extra APIs have been added that contain logic to map the string based property groups to the JSON pxResults of the data Page.
SR-B96629 · Issue 342674
Read-only values display in review harness
Resolved in Pega Version 7.4
A pxDropDown control was configured to use different values for the property and display values that were sourced from a Data Page, which in turn was sourced from a report definition. The display property value was retrieved via a joined class on the report and referenced using pxPage().PropertyName syntax. When the control was rendered on the Review harness in read only mode, the display value was not showing even though the property was set. This was due to the pageGroups caption property for the dataPage not being resolved in template_display. To correct this, two extra APIs have been added that contain logic to map the string based property groups to the JSON pxResults of the data Page.
SR-B96971 · Issue 347091
Custom filter value populated during runtime
Resolved in Pega Version 7.4
Default filter values were not applied to the initial run of a report, but did work after Apply was pressed. Investigation showed that the page used for a custom filter section was not sanitized between report runs. If a report is closed and then rerun in a new window, the prior filter values were preserved from before instead of reinitialized. This has been corrected.
SR-B97271 · Issue 342728
GetConnectors RD added to Data-Rule-Summary
Resolved in Pega Version 7.4
A report definition rule named 'pxGetConnectors' has been added to the Data-Rule-Summary Class of the Pega-IntegrationEngine ruleset to support third-party application integration.
SR-C1144 · Issue 344593
Missing columns added to InstanceList RD
Resolved in Pega Version 7.4
After upgrade, .pyItemId and .pxProcessingNodeId were missing from the pyInstanceList Report Definition. This was due to these two columns being missed during the conversion to Report definition, and this has now been fixed.
SR-C1738 · Issue 345628
Timestamp fixed for Export to Excel
Resolved in Pega Version 7.4
When trying to do a Export to Excel on a report definition with one of the columns being a Date time property, an extra 'a' was seen in the date time columns in Excel. In this case, 'a' is valid for formatting Java datetimes while 'AM/PM' is the equivalent for Excel, so the 'a' will be replaced with AM/PM in the summary viewexcel data.
SR-C2850 · Issue 348798
Missing buttons returned to Marketing report browser
Resolved in Pega Version 7.4
After upgrade, the Report Browser in the Pega Marketing portal was missing the 'Add Category' and 'Add Report' buttons. This was due to a difference in the UI-kit for the header, and has been fixed.
SR-C2920 · Issue 344845
Summary report count fixed when using filter prompt
Resolved in Pega Version 7.4
The summary data count was not getting updated in a report unless the "Prompt for filter changes before displaying report" option on Report Viewer tab (Actions -> Refresh) was unchecked. This was an error in the refresh code related to the display prompt filter check and has been corrected.
SR-C9779 · Issue 351372
Performance improvement for data page sourced by RD
Resolved in Pega Version 7.4
Performance improvements have been made to using a Data page sourced by a report definition by removing the step that creates an unneeded parameter page.
SR-B45056 · Issue 328736
XSS filtering added to getClassOfPageReference
Resolved in Pega Version 7.4
XSS filtering has been added to the URL produced when using getClassOfPageReference.