SR-C32033 · Issue 371520
Locking modifications and Hazelcast upgrade added to remove OOM error for advanced agents
Resolved in Pega Version 8.1
Using advanced agents which have the option "Run this agent on only one node at a time" caused the system to take a key-based cluster-wide distributed lock on a distributed map, causing the node which had the distributed map to become unresponsive due to OOM. The subsequent OperationTimeoutException caused the agent to be terminated as per the functionality of agents. The resolution for this is in two parts: a tryLock() has been added to the Distributed Map Layer, and support has been added for Hazelcast enterprise edition EE 3.10 in place of v.3.8.
INC-140739 · Issue 592830
UniqueID enhancement for attached files
Resolved in Pega Version 8.1.9
When two files with the same name were uploaded by different users simultaneously through Pulse or if a user uploaded two files with the same name across two sessions, whichever file arrived later was overriding the previous one in the system. As a result, the first pulse post ended up with an incorrect file attached. This has been resolved with an enhancement to add an API that appends a uniqueID to the file before uploading to ServiceExport directory.
SR-C40603 · Issue 383184
Europe/Ulyanovsk time zone will be handled as Europe/Samara to maintain local datetime values
Resolved in Pega Version 8.1
For some time zones, when a datetime value was provided it was changed to a default GMT value after a section refresh. This was caused by the Moment APIs utilized by Pega for time zone-based conversion on the client not including support for "Europe/Ulyanovsk". In order to work around this, if the operator time zone is "Europe/Ulyanovsk" it will be handled as "Europe/Samara" in the pzpega_ui_formatDateTime.js file.
SR-C42418 · Issue 385133
Enhancement added to allow multiselect input by clicking outside the area
Resolved in Pega Version 8.1
Previously, the multi-select control would process, add, and set the value on 'enter key'. An enhancement has been added to allow setting the value in multi-select input even when the users click outside after entering a value, allowing multi-select to also work like a normal input text box. To do this, a flag has been added to not clear the multiselect value on blur.
INC-183947 · Issue 673733
Query split added to handle Oracle expressions limit
Resolved in Pega Version 8.7
The PXCHECKFLOWDEPENDENCIES activity was throwing the Oracle error message "ORA-01795: maximum number of expressions in a list is 1000" when a case had a very large number of sub-cases, causing a failure in trying to submit additional child cases which sent them into the broken process. This has been resolved by updating the pxCheckFlowDependencies rule to break down the query parameter into batches of 999 so they can be handled by Oracle.
INC-184155 · Issue 673072
Entity Detection prefers first detected entity
Resolved in Pega Version 8.7
Entity detection shown in the "Training data" tab of the email channel did not match with the results of running the corresponding text analyzer rule. This occurred when a single piece of text was detected as multiple entity values, which led to the last entity detected being picked for case mapping because of the unclear scenario of duplicate entities. To resolve this, pxmapresponseentities has been updated to prefer the first detected entity.
INC-184834 · Issue 669458
Channel copy text analyzer detection updated
Resolved in Pega Version 8.7
The error message "No unlocked Ruleset versions are available. Please add or unlock a ruleset to create a new channel." was displayed when trying to save a new interface. This was traced to the system copying the channel to incorrect classes/names due to detecting an incorrect type of text analyzer and copying the wrong rules. To resolve this, the method of detecting the text analyzer type on channel copy has been updated.
INC-176173 · Issue 654726
Re-indexing correctly triggers old index deletion
Resolved in Pega Version 8.7
There was no request to delete the old index when a new reindexing process was started, resulting in the new data being put into the already existing index. This was traced to a logic flaw which evaluated a condition as false under certain conditions. This 'If' condition has been fixed and simplified so the process responsible for recreating the ElasticSearch index is accessible for the scenario of reindexing an entire index without specifying include or exclude classes.
INC-178663 · Issue 659805
Updated handling for batch indexing cancellation
Resolved in Pega Version 8.7
Entries were seen in the pyBatchindex QP even when indexing was not in progress. Investigation showed that if an exception occurred during the cancel process, the pyStatusWork property in Log-Cluster-FTSIndex instance was not correctly updated and the value remained as CancelInProgress. As a result, SLP silently remained in the state of waiting for the completion of cancel operation. This has been resolved by updating the handling of the cancellation process to ensure the queue is correctly cleared and email notifications are sent as expected.
INC-186782 · Issue 674952
Re-indexing correctly triggers old index deletion
Resolved in Pega Version 8.7
There was no request to delete the old index when a new reindexing process was started, resulting in the new data being put into the already existing index. This was traced to a logic flaw which evaluated a condition as false under certain conditions. This 'If' condition has been fixed and simplified so the process responsible for recreating the ElasticSearch index is accessible for the scenario of reindexing an entire index without specifying include or exclude classes.