SR-B90290 · Issue 338672
Case mismatch fixed for pyDateSetID
Resolved in Pega Version 7.4
The column name for a property defined in Data-NLP-Report-Summary was pyDateSetID, which did not match exactly the property ID of pyDataSetID. This caused issues with Microsoft SQL Server where property names and column names must match exactly. If the UDF functions are present, this is worked around by reading the value from the BLOB. However, if you are running without UDF functions, attempting to access this property generated an error. This case mismatch has been fixed.
SR-B91127 · Issue 340063
Fixed missing records in exported PDF report
Resolved in Pega Version 7.4
A report record which contained double-quotes (") was not displayed in an exported PDF if it was part of a Summary type report definition. In this case, when the drill down was enabled the ddpath attribute was generated in the markup; because the value contained "" double quotes, the markup became corrupted. To fix this, RRDATASUMMARYSPREADSHEETGENERATION now contains code to disable the drill down while doing the export to PDF.
SR-B92724 · Issue 341584
Chart in section modified to better handle decimals
Resolved in Pega Version 7.4
When using a customized report definition for TimelinessByJourneyType with precision set to "zero", some lines were assigned the same label due to rounding, e.g., labels for lines at 0.9 and 1.1 would both render as "1". To avoid this, the FusionJsonDataGenerator has been modified to hide unneeded chart lines and set default chart values for AxisMaxValue to 2 and numDivLines to 1 in cases where decimals is set to 0.
SR-B92748 · Issue 341371
Case Insensitive Search fixes for Segments
Resolved in Pega Version 7.4
In order to fix an issue where Case-Insensitive Search was not working in Segments, the following changes have been made: 1) If case insensitive property is selected and the key is a text property, the system will do case insensitive matching while inserting records to confirm whether a key was already inserted before. 2) The 'when' condition has been modified to make the case insensitive checkbox visible for custom import purposes.
SR-B92748 · Issue 342174
Case Insensitive Search fixes for Segments
Resolved in Pega Version 7.4
In order to fix an issue where Case-Insensitive Search was not working in Segments, the following changes have been made: 1) If case insensitive property is selected and the key is a text property, the system will do case insensitive matching while inserting records to confirm whether a key was already inserted before. 2) The 'when' condition has been modified to make the case insensitive checkbox visible for custom import purposes.
SR-B92748 · Issue 342540
Case Insensitive Search fixes for Segments
Resolved in Pega Version 7.4
In order to fix an issue where Case-Insensitive Search was not working in Segments, the following changes have been made: 1) If case insensitive property is selected and the key is a text property, the system will do case insensitive matching while inserting records to confirm whether a key was already inserted before. 2) The 'when' condition has been modified to make the case insensitive checkbox visible for custom import purposes.
SR-B94946 · Issue 343693
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-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.