INC-159836 · Issue 631206
Upgraded Apache UIMA Ruta libraries to resolve memory leak
Resolved in Pega Version 8.6.2
A memory leak issue that resulted in a reboot being needed every few days was traced to the class org.apache.uima.ruta.rule.RuleMatch. This has been resolved by upgrading the Apache UIMA Ruta libraries to v2.8.1.
INC-161829 · Issue 645206
Corrected merged rule checkout error
Resolved in Pega Version 8.6.1
A decision data rule that was created or updated in a branch and then merged to a ruleset version was failing a subsequent checkout from the same merged ruleset version. This was traced to recent work done to address an Indexoutofbound exception in pyEditElement related to java compilation exceeding the 65 000 byte limit, and has been resolved by updating the pzGetCircumstanceValue activity to exclude ruleset version from the circumstance value generated for pyEditElement section. The following activities in the Rule-Decision-DecisionParameters class have also been updated to replace the Obj-Open method with Obj-Open-By-Handle so that correct version of pyEditElement is referred - pzDeleteExistingLayout, OnBeforeDisplay and pzCheckIfRuleSyncWithLayout.
INC-164243 · Issue 656500
DateTime validation works correctly after importing invalid data
Resolved in Pega Version 8.6.1
After creating DecisionData (Dev studio) and adding a DateTime property to the form, importing records with invalid DateTime values failed with a validation error on the screen and the message "Error while converting format for data type DateTime property name Test_date_format with value scvf" was logged. Attempting to proceed by correcting the DateTime property and uploading worked, but any subsequent imports in the same session silently allowed invalid inputs to be passed without any validation errors and then showed blank date fields. This has been corrected.
INC-165704 · Issue 639505
VBD data flow timeout increased and made configurable
Resolved in Pega Version 8.6.1
Intermittent VBD timeouts were seen when writing records to MSK even though no errors were reported on the MSK side. Analysis showed that while batch data flows retry when a timeout occurs, real time data flows do not retry and the configuration to wait up to 10 seconds for an acknowledgement may not be sufficient depending on the system conditions. This has been resolved by increasing the default timeout to 20 seconds and adding a configurable timeout "vbd/streamPublishTimeoutMillis" to allow a customized setting.
INC-166561 · Issue 645650
ADM Models correctly updated
Resolved in Pega Version 8.6.1
The ADM models were not being updated when responses were processed either via the CaptureResponse API or when the time elapsed that should result in an update reflecting a non-response. This was traced to incomplete handling for a response coming for some other model which was converted to EMPTY, and has been resolved by modifying the logic so that the default responses and other responses are processed properly.
INC-167334 · Issue 639318
GRS support added for Kafka Key password
Resolved in Pega Version 8.6.1
An enhancement has been added to support using GRS to set values for the Kafka Key password dynamically.
INC-169125 · Issue 642401
Nodes resume correctly after DDS restart
Resolved in Pega Version 8.6.1
A corner case issue in VBD's code for handling a DDS session was preventing the nodes from recovering correctly after a system shutdown. As part of the process for an event which fires if all DDS nodes are taken down or as part of a switch from embedded to external Cassandra, VBD's cache is invalidated and then re-initialized once new VBD API calls are received or on the VBD service pulse. In this case, the invalidation of the cache did not complete due to logic in the VBD code that can lead to executing a Cassandra query that will not work in the case of all DDS nodes being down. This has been resolved by modifying the handling of a session change event to eliminate inadvertent Cassandra queries so the invalidation can complete correctly and continue the re-initialization process.
INC-169544 · Issue 649538
Enhancement for MaxEnt modeling data
Resolved in Pega Version 8.6.1
An enhancement has been added to create output for the model coefficients, the term frequency, and the inverse term frequency for use in maximum entropy modeling. For MRM processes, every Maximum Entropy (Maxent) based topic model will contain two additional stats resources. These resources can be used to validate and replicate running of topic model outside of Pega. The resources are: 1) Term Frequency file – A CSV file with all words used for training and their cumulative frequency across training set. File name format – TRAINING_DATA_TERM_FREQUENCY_< RandomNumber >.csv olumns – Word, Count 2) Coefficient file – A CSV file with all features (words, taxonomy matches and category matches) and model learnt weights for each topic across training set. File name format – MAXENT_COEFFICIENT_VALUE.csv Columns – Feature, < TopicName1 >, < TopicName2 > ,…, < TopicNameK >
INC-170721 · Issue 658962
Stricter criteria set for reusing an SSAExecutionContext
Resolved in Pega Version 8.6.1
After a Strategy was configured with an existing Proposition Filter and the Explain Results box was unchecked, executing the strategy resulted in the error "Stack is empty, cannot pop any more frames". Investigation showed that the SSAExecutionContext object was reused across the two criteria evaluation in Proposition Filter rule: this works well as long as the input is the same across the two evaluations. However, the SSAExecutionContext object also stashed a reference to a PublicAPI object which became stale in the second evaluation and caused the empty stack issue for the given scenario. This has been resolved by providing stricter criteria in deciding when an SSAExecutionContext can be reused or not in the case of Proposition Filter rule.
INC-171594 · Issue 656184
Spell check correctly applied to email body
Resolved in Pega Version 8.6.1
Spell check was not being applied to email body for text analysis in Email Channel. This has been resolved to work irrespective of case.