SR-A16638 · Issue 233607
Changed edit control to prevent Google Chrome adding zeroes when localizing
Resolved in Pega Version 7.2.1
When using Google Chrome in some locales, zeros were being added to values in the skin and corrupting entered values. This was due to Google Chrome defaulting to localizing input type numbers, which caused dual localization after the control had already localized the value after reload. When input type is text, only the control localization will happen, so a workaround for Google Chrome has been added where the type of control has bene changed to text in the editable mode for the pyItemAlignment section.
SR-A21931 · Issue 242711
XY chart Dashboard reports updated to handle empty data
Resolved in Pega Version 7.2.1
Dashboard reports were not loading when using RD as the source for XY charts if the data returned was completely empty. RUF: pzControl ? pzRuntimeFusionXYDataJSON has been updated to handle this missing use case.
SR-A21931 · Issue 233188
XY chart Dashboard reports updated to handle empty data
Resolved in Pega Version 7.2.1
Dashboard reports were not loading when using RD as the source for XY charts if the data returned was completely empty. RUF: pzControl ? pzRuntimeFusionXYDataJSON has been updated to handle this missing use case.
SR-A22365 · Issue 243530
Multi-parameter function value handling added to Report Definition chart
Resolved in Pega Version 7.2.1
When a chart control was configured using the property panel in design view, the chart preview did not update appropriately if it used a column defined by a function that with two or more parameters. To handle this, part of com.pega.pegarules.priv.desktop.reporting.chart.AutoChartConfigTranslator.translateDataItem(DataItem, ClipboardPage) has been refactored such that it only splits pyReportColumnKey on the first ',' (comma).
SR-A24516 · Issue 247668
Reports correctly deleted
Resolved in Pega Version 7.2.1
Reports are not deleted after deleting a shortcut, causing errors when trying to create reports using the same name. The logic for UpdateCheckIn has been corrected so that it will not jump to block the rule and will instead delete the rule.
SR-A17916 · Issue 234503
NPS Report drilldown filters corrected
Resolved in Pega Version 7.2.1
The recent changes to the NPS Report drilldown activity to call pzUpgradeOnOpen data transform have been further refined to correct a filtering error. When the filters were upgraded using the pzSetFilterDataType data transform, the value of the pyIsLeftOperandAFunction property was not appropriately set to true/false (depending on the value of the filter). This led the drilldown to incorrectly think that the column was a property instead of a calculation if the calculation used nested calculations, and has been resolved.
SR-A17916 · Issue 233771
NPS Report drilldown filters corrected
Resolved in Pega Version 7.2.1
The recent changes to the NPS Report drilldown activity to call pzUpgradeOnOpen data transform have been further refined to correct a filtering error. When the filters were upgraded using the pzSetFilterDataType data transform, the value of the pyIsLeftOperandAFunction property was not appropriately set to true/false (depending on the value of the filter). This led the drilldown to incorrectly think that the column was a property instead of a calculation if the calculation used nested calculations, and has been resolved.
SR-A17016 · Issue 234926
Repaired multiple-value filters for RD data transform
Resolved in Pega Version 7.2.1
When using a report definition in which the filter values were supplied through the data transform rule, a single given value was correctly passed but multiple values were not. This was traced to the encoding of double quotes which were then not replaced in the correct step, and has been fixed.
SR-A22993 · Issue 247098
Date format and alignment updated for Export to Excel
Resolved in Pega Version 7.2.1
When using Report Definition for a case search with the out-of-the-box excel export, formatting one of the DateTime type properties to display only the date portion in the exported report was not working as expected in the repeated-grid while it did work properly in report definition export function. The problem existed in the generation for the Report Definition itself due to the control formatting the data to be mm/dd/yyyy without the days even though the data type is a datetime, and the function has been updated to pass "date" as the datatype when a datetime is being formatted as a date.
SR-A23912 · Issue 246952
Custom filters won't display header container icons
Resolved in Pega Version 7.2.1
Unwanted icons were appearing when using a custom filter section that has a grid with a header/title, such as an 'X' close icon displaying next to an included section/repeat grid coupled to the filter section launched from the report browser for a report definition. The harness that displays the filter section has been modified to not include the icons that come with a container that has a header.