SR-B71969 · Issue 326817
Date fixed for Export to Excel
Resolved in Pega Version 7.3.1
Dates were not being formatted correctly on Export to Excel of a report definition. This was due to an error in exporting just the date field that was not previously considered when repairing the date/time function. To fix this, Export_Date_RD has been updated to export the date in a consistent manner that Excel will understand (similar to how its being done in pzExport_Datetime_RD).
SR-B72892 · Issue 323517
Error message display fixed for RG read-only field
Resolved in Pega Version 7.3.1
Incorrect behaviors were seen with displaying errors when a field in a repeat grid table was configured as "Read-only (always)" and "Show validation messages in read-only mode" was on. In Google Chrome, the UI form did not contain the corresponding error image in the field due to the only error icon div getting hidden. In Microsoft Internet Explorer 11, the UI form contained the corresponding error image in the field, but only part of this image was visible due to changes of column/field width not being honored. These issues have been fixed by updating the CSS in the pzbase-grids.css file.
SR-B73126 · Issue 323350
Fixed autocomplete cell value disappearing on blur
Resolved in Pega Version 7.3.1
After upgrade, an autocomplete configured with data page "onChange - Post Value" had cells whose entered value disappeared onBlur of the autocomplete cell. The reported issue is a UI framework defect with templating enabled, and was traced to an issue with the change tracker data not getting merged properly to context data after the postvalue response is received. This has been fixed.
SR-B73478 · Issue 325315
Chart date column duplication resolved
Resolved in Pega Version 7.3.1
Report definition charts were displaying duplicate date columns when the operator time zone was set to "Europe/London". To correct this, the system will conditionally set the time zone only when it's a datetime when normalizing the data.
SR-B73514 · Issue 324049
Added new function to bypass URLScan MaxURLLength
Resolved in Pega Version 7.3.1
When Pega is fronted by Microsoft IIS WebServer with either a proxy or Web Application Server plugin, the IIS advanced security options, URLScan, are used to limit the size of URLs. When the URLScan MaxURLLength is set below about 600 characters a major static content request for core PRPC UI JavaScript files is blocked. This is a known issue when using IIS Web Server, but to enable expanded use, a 'when' function named pyIsForcedSplitJS has been added that allows overwrite as required by dividing pzHarnessStaticScripts into 4 chunks to decrease length. The format is
SR-B73531 · Issue 325518
Missing check added for "Column Command Menu" on summary type report
Resolved in Pega Version 7.3.1
For a summary type report, the column command menu was still displayed even though the "Enable Column Command Menu" was unchecked on the report definition Report Viewer tab. This was due to a missing check for "Enable column command menu" before adding the showReportRCMenu onclick event, and has been fixed.
SR-B73577 · Issue 322575
Localization added in Pega Express
Resolved in Pega Version 7.3.1
Localization has been added to the Pega express configuration channel and Interface display formats.
SR-B73599 · Issue 324612
Filtering fixed for properties defined by @@CaseWhen()
Resolved in Pega Version 7.3.1
Filtering was not applied for properties defined by @@CaseWhen() . This was due to some function alias calls needing double quotes for literal parameters. The double quotes are removed after section XML is submitted and hence the param available to the grid (via html attribute sortField) did not have the double quotes. To correct this, a function alias call in RD bound grid will set the pyColumnName to pyFieldName since the pyColumnName does not have the double quotes that are needed by some functions.
SR-B73664 · Issue 322173
Text area - Disable when fixed
Resolved in Pega Version 7.3.1
A Text Area control was not disabling with When conditions or expressions. The control was disabled correctly if set to "Always". This was due to an incorrect condition in pzpega_ui_template_textarea.js, and has been fixed.
SR-B74586 · Issue 325692
Fixed save-as for RD with sub-report and join
Resolved in Pega Version 7.3.1
A save-as for the existing Report Definition rule :USCANSaleEstimate was not working for a new ruleset version. This was an issue with an existing RD that had a sub-report and was joined by a column in the sub-report that was a function, and pzGenerateMsgForUderDefinedFunctions has been modified to correct this.