SR-B36794 · Issue 322533
Added reindex check to RuleCheckin
Resolved in Pega Version 7.3.1
After creating new proposition data and saving it, pyPropertyReferences were changing on save of the Decision Data rule. Analysis identified the issue as happening when a rule was privately edited from a locked ruleset version and then checked in into another ruleset/version: rule references were created for the privately edited copy but when the privately edited copy was deleted at step 29, the references were also deleted and since the item being checked in was deleted in the same transaction the commit did not trigger reindexing and the references were not created again. To handle this edge case, a step has been added to the RuleCheckIn activity to reindex if .pzIsPrivateCheckOut == "true" && .
SR-B51112 · Issue 307512
Silverlight MSI file rebuilt without registry keys for bulk installation use
Resolved in Pega Version 7.3.1
MS Word Compatibility for 2016 Office 365 was generating messages like "Error in updating the Registry Key of (AllowLaunchOfElevatedTrustApps): Object reference not set to an instance of an object." This was due to a newly-added registry keys inclusion feature on Silverlight prerequisites that not supported for installing multiple systems. To address this, the Silverlight prerequisites MSI file has been re-built without the inclusion of registry keys
SR-B70379 · Issue 326388
Post-printing screenshot window freeze fixed
Resolved in Pega Version 7.3.1
When an attached screenshot was clicked open and displayed in a pop-up window, the window was freezing after a print operation was performed. This was an issue with closing the ActiveX control through Microsoft Internet Explorer. To resolve this, the ActiveX control previously used has been changed to Silverlight.
SR-B77020 · Issue 326989
Help file update to clarify Precondition exceptions do not have error handling
Resolved in Pega Version 7.3.1
The rule-/rule-obj-/rule-obj-activity/stepstransition help file documentation has been corrected to indicate the Exception handling does not cover any conditions that might occur in the precondition.
SR-B66139 · Issue 316025
Localization fixed for report name place holders
Resolved in Pega Version 7.3.1
The Report Category Name Place holder was not being localized if it contained special characters. Handling has been added to correct this.
SR-B66454 · Issue 316846
Support added for filtering labels in Join
Resolved in Pega Version 7.3.1
When class join was used in a report and the property used for filtering was a SinglePage property of the join class, then the label was not coming up in the Report Filter section. This was due to filtering labels not being shown when Join is used, and support for this has been added.
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-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-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-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.