SR-B69133 · Issue 317298
Carriage returns stripped from ExtractIdentifier value
Resolved in Pega Version 7.3.1
If the pzInskey value in the extract rule xml file had extra carriage returns, the pxExtractIdentifier was generated with extra carriage returns in the value. Downstream processing was failing because of these extra carriage returns. To correct this, all carriage returns will be stripped from the pxExtractIdentifier value.
SR-B70051 · Issue 324690
Enhanced Dnode Pulse logging
Resolved in Pega Version 7.3.1
Enhanced pulse logging has been added for DNode errors
SR-B76502 · Issue 325128
BIX extract exceptions and missing XML fixed
Resolved in Pega Version 7.3.1
StringIndexOutOfBoundsException and ClassCastException were being generated during BIX extract and some tags were missing in the extracted XML. This has been fixed.
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-B15150 · Issue 286741
Online help updated with current reindexing utility information
Resolved in Pega Version 7.3.1
The online help files have been updated to remove references to deprecated activities for reindexing declarative indexes. Information has been added for the currently supported utility, the column populator tool (prpcUtils or prpcServiceUtils) with expose option and 'expose.reindex=true', that specifically regenerates declarative index content.
INC-132590 · Issue 590491
Exported Excel from Decision Table wraps correctly
Resolved in Pega Version 8.4.4
After upgrade, entries were displayed in a single line on exporting a decision table to Excel despite WrapText cell formatting being set. This was traced to the WrapText cell formatting set under the UpdateGridCells() function being overridden inside an addDataFormat() function callas part of DecisionTableWorkBookConverter.java. This has been resolved by adding the new function "setWorkAreaCellStyles" and calling it after generateWorkbook() function call of super class (AbstractWorkBookConverter.java).
INC-140789 · Issue 597799
Added handling for validation after inactivity
Resolved in Pega Version 8.4.4
A Validate rule was configured to add an error to a field if MyPageList had any page where MyProperty was not empty. The rule worked correctly if there was no pause in using the UI, but if the UI was left for a few minutes and then the field was changed, the Validate rule always evaluated the expression to true. This has been resolved by adding a null check in Utilities.countInPageList() function.