SR-D85095 · Issue 546342
Updated COUNT logic for strategies with ssavm set to true
Resolved in Pega Version 8.4.1
An error was seen when attempting to save a strategy after setting ssavm to true, indicating an issue in the “COUNT” method in Group By shape. Since the source field is not used and does not need to be evaluated here, the system has been updated to ignore the source field if the operation is COUNT.
SR-D85558 · Issue 548287
Handling added for prolonged Heartbeat Update Queries
Resolved in Pega Version 8.4.1
After restart, the pyFTSIncrementalIndexer queue size had hundreds of thousands of entries even though it was empty prior to the restart.Investigation traced this to a job scheduler that checked all the database connections everyday at 1 EST by using a list that contained some connections which did not exist. Checking those invalid connections caused other update queries to queue and wait, resulting in the update heartbeat query taking longer than its default beat. This caused a Split Brain issue wherein other nodes considered the long-executing node to be dead and triggered a rebalance while the node itself continued to execute partitions thinking that it was healthy. This caused duplicate processing of records. To resolve this, a fail safe has been added: while updating heartbeat in Service Registry, nodes will enter safe mode when the update query is taking longer than the default beat.
SR-D89012 · Issue 550801
DelegatedRules refresh icon made accessible
Resolved in Pega Version 8.4.1
When using Accessibility, the refresh icon in pzDelegatedRules was being read as "Link". This has been corrected by adding text for the refresh icon.
SR-D89428 · Issue 550393
Data Flow StartTime uses locale timezone
Resolved in Pega Version 8.4.1
The start time of the dataflow was displayed in GMT instead of the operator locale timezone. This has been corrected.
SR-D89643 · Issue 548293
Old Tumbling Time data in event strategies given TTL for cleanup
Resolved in Pega Version 8.4.1
Old Tumbling Time data keys in event strategies were not being cleaned up, causing Cassandra timeouts after the dataflow run had been running for several months. The longer the dataflow was running using standard compaction, the more the data was potentially spread out across SSTables and the slower it became. This has been resolved by adding a 'time to live' value for tumbling time windows, and event strategies has been switched to use leveled compaction by default.
INC-179727 · Issue 704545
Modified batch requestor handling to ensure cleanup
Resolved in Pega Version 8.6.4
A large buildup of batch requestors was seen, and restarting the node did not clear it. Investigation showed that in the case of one class reading a DSS value, a Pega requestor was being created when it was unable to retrieve any Pega context, and this requestor was not cleaned up afterwards. To resolve this, an update has been made to the way the requestor and Pega context is being created along with ensuring it will be cleaned up properly after use.
INC-180246 · Issue 664947
Support for apostrophe added to keyword tokenization
Resolved in Pega Version 8.6.4
A keyword containing an apostrophe was not detected properly in Text extraction model. This has been resolved by updating the annotator used in the tokenization.
INC-192826 · Issue 685797
PMML updated for nested 'if'
Resolved in Pega Version 8.6.4
Running a model on the openscoring API and the Pega PMML model gave different results. This has been resolved by updating the handling for nested 'if' in PMML.
INC-194382 · Issue 697615
ADM Model management page updates
Resolved in Pega Version 8.6.4
When accessing the ADM model management landing page in an environment with a large number of nodes, an "UnresponsiveNodeException" error was thrown from the pylaststrategyresults activity by various nodes on different days. Investigation showed the ADM factory table was truncated, leading to inconsistent ADM data in the Last Responses Section. This has been resolved, and the ADM model management page has been made more resilient to node failures.
INC-196561 · Issue 688846
Natural Language Processing (NLP) topic categorization working consistently for German
Resolved in Pega Version 8.6.4
A few German words were not recognized by the Natural Language Processing (NLP) topic categorization if they were given in capital letters. This was traced to upper case keywords being lowercased during model creation time, but not during prediction time. To resolve this, all words will be lower-cased before the model analyzes the text.