INC-195387 · Issue 681673
HandleResponses updated for use with optimized campaign
Resolved in Pega Version 8.7
After updating from Pega 8.4, responses were not processed in the pxHandleResponses Data flow if the "pyCampaignOptimization" flag was set to true. This was traced to a missed use case for an optimized campaign, and has been resolved by modifying the condition in HandleResponses.
INC-216490 · Issue 713633
pxIdentifier dynamically set for DecisionData while using GOS
Resolved in Pega Version 8.7.2
When using a Decision Data component in a strategy which was wrapped with Globally Optimized Strategy (GOS), no results were generated from the DataJoin shape under optimized execution. Investigation showed this was caused by a missing .pxIdentifier for the DecisionData shape during GOS execution. There was a workaround of unselecting the checkbox on the Advanced tab in the Decision Data component, but this has been resolved by updating the strategy kernel service so it will dynamically construct the pxIdentifier based on the skills assignment module (SSA).
INC-197530 · Issue 686027
Value Finder updated for use with external Cassandra nodes
Resolved in Pega Version 8.7
Attempting to use the Value Finder feature resulted in the error "Running Simulation is not possible because the required services are not available. Contact your System Administrator to enable the data flow and decisioning data store services." Analysis traced this to a check which identifies whether there is more than one internal node available for CDH/ DSS node. Since there were only external nodes available in this scenario and no internal nodes, the method returned false and returned the error when the CDH / VF page was launched. To resolve this, the check has been modified to allow for external Cassandra.
INC-174933 · Issue 651829
Special characters escaped for use in "is in List" lookups
Resolved in Pega Version 8.7
After creating a specific criterion on any proposition using a string property, the "Is In List" operator, and a customer list with one value containing a "$", clicking save or check in resulted in the exception error "Problem invoking function: pega_decisionengine_propositionfilterfua.pzPropositionFilterMethodBody--(PublicAPI,ClipboardPage) java.lang.IllegalArgumentException: Illegal group reference at java.util.regex.Matcher.appendReplacement(Matcher.java:857) ". This has been resolved by escaping regular expression control characters in string replacement, which will allow the use of characters such as the $ sign for "is in List" lookups.
SR-D37945 · Issue 506799
Server node cache refresh will use remote execution timeout
Resolved in Pega Version 8.2.4
A campaign was failing due to VBD remote ping timeout with a stacktrace that indicated a StageException. Investigation showed that when the cluster is heavily loaded, calls to the remote execution API could time out. If this occurred when the VBD client was refreshing its cache of VBD server nodes, then the insert failed and the error was propagated up the calling data flow. To resolve this, the system will use the remote execution timeout when refreshing node cache, extend the timeout to 60 seconds, and ensure timeouts are retried during inserts.
INC-176757 · Issue 657785
Interaction History properly saved when running strategy on a different data flow
Resolved in Pega Version 8.7
Customized Interaction History properties that had been added to pyInteractionHistoryConfiguration and pyDefaultWorkingSet and saved into the PR_DATA_IH_FACT table were not being saved properly after upgrading from 7.3 to 8.3. This was a missed use case and has been resolved.
INC-191356 · Issue 679163
External Input setting available on Strategy Batch Performance Test
Resolved in Pega Version 8.7
It was not possible to specify the External Input as part of a strategy when using a Batch Performance test. This has been resolved by updating the pzDisplayTestStrategyContext When condition to "true" the so external input selector is properly displayed.
INC-213217 · Issue 714192
Updated context handling for executing data transforms in dataflows
Resolved in Pega Version 8.7.2
When performing a sort operation in a data transform on a page list and invoking the Data transform through a Data flow, a java.lang.UnsupportedOperationException was generated on the sort step even though the data was correct. Investigation showed that the dataflows were using a different execution context than the context used for regular activity execution. An update has been made to ensure the correct context is being used while executing data transforms in dataflows.
INC-220642 · Issue 717033
Updated context handling for executing data transforms in dataflows
Resolved in Pega Version 8.7.2
When performing a sort operation in a data transform on a page list and invoking the Data transform through a Data flow, a java.lang.UnsupportedOperationException was generated on the sort step even though the data was correct. Investigation showed that the dataflows were using a different execution context than the context used for regular activity execution. An update has been made to ensure the correct context is being used while executing data transforms in dataflows.
INC-175707 · Issue 655347
Multi-level strategy gives correct rules during Batch run
Resolved in Pega Version 8.7
When using a nested page structure with multi-level strategies that loop through each page and process the customer, a customer with two linked customers A and B had the results of A overridden by B during Batch Processing while single case canvas testing showed the correct results. This was caused by the DSM clipboard page method of carrying the parent page info not supporting the re-use of pages, and has been resolved by adding an enhancement that will sanitize the strategy stage processor to ensure the correct page reference is used.