SR-B49995 · Issue 308428
Proposition filter rule description updated to match decision data description changes
Resolved in Pega Version 7.3.1
Updating the description field of a proposition in the decision data did not update the description in the proposition filter rule involving that proposition as expected. This has been resolved by updating the rule which is refreshing proposition name changes to handle description change as well.
SR-B56530 · Issue 316311
Reworked destination assumptions for child dataflows
Resolved in Pega Version 7.3.1
When activating a Real time data flow run containing a Stream dataset as input which was then output to two child dataflows containing different event strategies, an IllegalArgumentException error appeared. This was traced to the pzDataFlowContainsEventStrategy activity assuming that the last shape had "Destination" in the ID in addition to an error obtaining the class. This has been fixed by properly setting the KVS type: the DataFlowRunConfig.getKeyValueStoreType() will not return NONE but default instead, and the pzDataFlowContainsEventStrategy now Iterates through all subflows and fixed secondary destination name.
SR-B69595 · Issue 317880
Fixed UnsupportedOperationException from decision table
Resolved in Pega Version 7.3.1
When using embedded properties (e.g. .OfferData.Action) within a decision table, an UnsupportedOperationException appeared on the DSMClipboardProperty if it was executed via a Strategy rule. The issue was with a function being not implemented within DSMClipboardPage, and has been fixed.
SR-B49696 · Issue 310805
Enhanced decision tree config using symbols
Resolved in Pega Version 7.3.1
A decision tree with multiple conditions configured using "||" and "&&" symbols resulted in the wrong outputs being returned at run time. Handling has been added to support these symbols in this use.
SR-B49022 · Issue 306907
OOM error fixed for testing large decision tables
Resolved in Pega Version 7.3.1
The Pega server was crashing with an out of memory error when the "Show Conflicts" button in a decision table with >20 rows and >20 columns was clicked. This was traced to an infinite loop caused by inadequate handling for a decision tree of that size, and the testConsistency activity has been updated to overcome an OutOfMemoryError in cases of huge decision trees submitted to the show conflicts functionality. The same update has been made to the similar 'Show Completeness' button/function.
SR-B49022 · Issue 312820
OOM error fixed for testing large decision tables
Resolved in Pega Version 7.3.1
The Pega server was crashing with an out of memory error when the "Show Conflicts" button in a decision table with >20 rows and >20 columns was clicked. This was traced to an infinite loop caused by inadequate handling for a decision tree of that size, and the testConsistency activity has been updated to overcome an OutOfMemoryError in cases of huge decision trees submitted to the show conflicts functionality. The same update has been made to the similar 'Show Completeness' button/function.
SR-B54950 · Issue 315082
Tightened application of Rule Approval for bulk check-in
Resolved in Pega Version 7.3.1
When rule check in approval was enabled, the following scenarios bypassed the approval process: -Creating a new rule. -Performing a Save-As of a rule (either under a new name or to a different ruleset). -Performing a bulk check in. This has been fixed by modifying WBCheckinByKey to ensure the WBApproval_CheckIn activity will be called in cases where a checkmark present on the Rule-Set indicates Approval is required The approval check-in process will also be called in the Bulk Check-in feature.
SR-B54950 · Issue 316112
Tightened application of Rule Approval for bulk check-in
Resolved in Pega Version 7.3.1
When rule check in approval was enabled, the following scenarios bypassed the approval process: -Creating a new rule. -Performing a Save-As of a rule (either under a new name or to a different ruleset). -Performing a bulk check in. This has been fixed by modifying WBCheckinByKey to ensure the WBApproval_CheckIn activity will be called in cases where a checkmark present on the Rule-Set indicates Approval is required The approval check-in process will also be called in the Bulk Check-in feature.
SR-B51449 · Issue 308503
Property Record localization added for Pega Marketing
Resolved in Pega Version 7.3.1
Localization has been added for Property Record Configuration text in the Pega Marketing application.
SR-B51450 · Issue 308504
Property Record localization added for Pega Marketing
Resolved in Pega Version 7.3.1
Localization has been added for Property Record Configuration text in the Pega Marketing application.