INC-194657 · Issue 682006
ADMinputsource field population updated to handle transactional decisions
Resolved in Pega Version 8.6.3
The CaptureResponse flow was failing while writing to AdaptiveAnalytics with the error "IllegalArgumentException - argument does not represent JSON object". This occurred while running an outbound campaign where a few decisions were treated as transactional and did not have Model executions. Attempting to set a response for these decisions resulted in a JSON parse exception being thrown due to pxADMInputs not being populated (no models executed). This occurred only when using transactional actions in CDH, and was caused by the system only including predictive models during the make decision flow due to common inputs not being stored. While there was a workaround of overriding the property pzADMInputSource to use modelReferences instead of admInputContainer, this has been resolved by correcting how the pzADMinputsource field is populated. When there is no modelInput, the system will not populate that field so the page is ignored.
INC-194810 · Issue 691885
Removed services check and added warnings for simulations
Resolved in Pega Version 8.6.3
Attempting to run an audience simulation resulted in the error "Running simulations is not possible, because the required services are not available. Contact your system administrator to enable the data flow and real-time data grid services". Investigation showed the @DsmServices.pxHasFunctionalNodes("DataFlow","Batch") function call contained in the 'when' rule pyUnavailableDecisionServices was returning false even if all the nodes were in the cluster and all the DSM Services were in NORMAL status. To resolve this, the services check has been disabled and the simulation run will show a warning or fail if a data flow run is queued for more than 30 secs or if there is an issue with querying the underlying metrics storage.
INC-195197 · Issue 692148
Warnings added to prevent empty StrategyResult page
Resolved in Pega Version 8.6.3
When a Proposition Filter rule refers to a When rule that has "StrategyResult" declared in Pages & Classes but no "Param.StrategyResult", a design time warning will appear to indicate that this might cause discrepancy in globally optimized strategy (GOS) execution. * The warning message for a When rule with StrategyResult in Pages & Classes but not in Parameters: When rule [WhenClass: WhenName] does not have proper mapping for [StrategyResult] page. This would result in an empty [StrategyResult] page being passed into the When rule during execution. Please go to [WhenClass: WhenName] and add [StrategyResult] in the Parameters list and configure the mapping properly on Proposition Filter rule. * The warning message when StrategyResult is not in Pages & Classes but in Parameters list: When rule [WhenClass: WhenName] declares [StrategyResult] in Parameters tab, but isn't used in the conditions. This would affect performance during execution. Please remove the parameter from When rule [WhenClass: WhenName], and remove the Parameter mapping from the corresponding Proposition Filter criteria.
INC-195346 · Issue 682715
Added parser retraining for intermittent email issue
Resolved in Pega Version 8.6.3
An email listener was intermittently failing to pull the data from the email subject into the required property in the email triage case. Investigation showed that the pxEmailParser was excluding the first line in the incoming text for some cases, and has been resolved by adding code to retrain the email parser.
INC-195387 · Issue 681674
HandleResponses updated for use with optimized campaign
Resolved in Pega Version 8.6.3
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-196452 · Issue 687463
Handling added for special characters in dataflow and mbean name
Resolved in Pega Version 8.6.3
Exception errors from deleted email listeners were seen after server start-up. Investigation showed that when a dataflow stage name had a special character and that name was then used in the mbean name, it was failing to register. This has been resolved by escaping JMX key values if they contain special characters.
INC-196822 · Issue 691104
Debugging enhancements for globally optimized strategies
Resolved in Pega Version 8.6.3
When a null pointer exception was encountered during globally optimized strategies (GOS), the logging included a long chain of exceptions and the most useful information was not easily visible. To improve troubleshooting, the error message has been modified to show the actual cause of the error first. A catch has also been added to better handle any null pointer error after db.open and db.opendefault.
INC-197530 · Issue 684716
Value Finder updated for use with external Cassandra nodes
Resolved in Pega Version 8.6.3
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-197730 · Issue 686236
Prediction outcome response timing updated
Resolved in Pega Version 8.6.3
Predictions using a response timeout were not emitting a negative response ('NoResponse') when the specified waiting time expired. This was traced to the the outcome and response timeout values being overridden while triggering responses for multi stage predictions along with chained predictions. This has been resolved by modifying the flow to emit each outcome as it is received and by adding the dataflow trigger in the function so that it does not override the values in case of chained predictions.
INC-198232 · Issue 685701
Tombstone cleanup modified to handle very large volume environments
Resolved in Pega Version 8.6.3
Cassandra nodes were periodically suffering from an out of memory condition. This was traced to tumbling windows creating too many tombstones for Cassandra to clean up effectively when running in a very high volume environment with a short tumbling time. This has been resolved by modifying the procedure away from using individual tombstones to instead use range tombstones which will continuously supersede the previous tombstone so there is never an opportunity for them to build up.