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-A22147 · Issue 244096
Autogenerated prconfig sets v6 or v7 based on detection
Resolved in Pega Version 7.2.1
The autogenerated prpcUtils prconfig.xml file was setting the database/storageVersion to 6. In order to facilitate other setups, a flag has been provided in prpcUtils.properties as pega.storageVersion which will set the value in generated prconfig.xml to an empty string so the engine handles setting this to 6 or 7 in the same way that is possible when running the system.
SR-A22263 · Issue 242102
Improved error reporting for PE install
Resolved in Pega Version 7.2.1
In order to facilitate debugging, attempting to install Pega Express from a directory with a space in the name will generate an error on the screen reiterating the installation instructions requiring that the directory name not contain a space.
SR-A22354 · Issue 245861
prpcUtils honors 5.4 compatibility checkbox
Resolved in Pega Version 7.2.1
Pega deployment using prpcUtils was failing due to the 5.4 compatibility checkbox being ignored: the product rule being exported still included schema changes in the exported RAP file. This has been corrected.
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-A22672 · Issue 243213
Use Pega Log Analyzer in place of Alerts.xls Excel Template
Resolved in Pega Version 7.2.1
A documentation error incorrectly referred to the Alerts.xls Excel template as being available on the PDN. That file is no longer available, and the Pega Log Analyzer should be used instead: https://pdn.pega.com/community/pega-exchange/pegarules-log-analyzer
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-A23134 · Issue 243870
Resolved upgrade exception caused by non-standard requestor setting
Resolved in Pega Version 7.2.1
Upgrading to v7.2 was failing if the 'Requestor Types' (DATA-ADMIN-REQUESTOR instances) ACCESS GROUPs had been modified in the previous version for the System Name 'prpc'. This modification caused the PRPC requestors to not be replaced during upgrade. To address this issue, the installation will create a RAP to import into the SDE that will check for this condition, and the PRPC Requestors have been updated such that they cannot be modified. See also: Process Commander V6 help "About Requestor Type data instances" and "When and how to change a system name" for more background information about Requestor Types.
SR-A23339 · Issue 247921
Non-versioned class rule forms updated during upgrade
Resolved in Pega Version 7.2.1
The non-versioned class rules in an environment were skipped during upgrade due to an error in the RevalidateAndSave function. This has been corrected.
SR-A23457 · Issue 245079
Tab
Resolved in Pega Version 7.2.1
In a tabbed layout, opening a modal window resulted in the tab name being changed to that of any active window. This was an error in the drilldown window logic, and has been corrected.