INC-209419 · Issue 704268
Email bot tags the incoming account correctly
Resolved in Pega Version 8.5.6
When an email bot was created and configured for two email accounts, for example [email protected] and [email protected], an incoming email that had both of the email addresses in the "TO" line correctly created two Work-Channel-Triage-Email cases, but the data on the triage case did not correctly mark the incoming email account in "pzIncomingEmailAccount" or "pyAccountId". This has been resolved with an update that will rely on pyListenerPage if pzIncomingEmailAccount is blank initially, and if pzIncomingEmailAccount is still blank the system will then iterate over the email address and fetch the email account from the channelconfig page.
INC-170458 · Issue 667371
Handling updated for queue processor locks
Resolved in Pega Version 8.5.6
The Final activity mentioned in the processing epilog of the Service File rule was not being consistently called from File Listener, causing some of the cases to become stuck and not continue to the next stage. Investigation showed that if the lock was held by the queue processor requestor, the system was unable to obtain the lock but still proceeded to update the LogServiceFile page and persist it. This resulted in overwriting changes made on the LogServiceFile page by the requestor, resetting the completed-batches-count set back to 0. To resolve this, RuleServiceFile -> updateLSFBatchCounts() will call the overloaded lockAndLoad() method in LogServiceFile that accepts a parameter called lockAttempts. This will attempt to obtain a lock for a given number of times before throwing an exception.
INC-172849 · Issue 665981
SortPageList method updated for Obj-Sort
Resolved in Pega Version 8.5.6
Sorting page lists backed by a node level datapage using Obj-Sort was causing a ConcurrentModificationException. This has been resolved by updating the SorterImpl.sortPageList method to use java7CollectionsSort instead of collectionsSortWithInferenceEngineDisabled.
INC-173434 · Issue 672674
Pushservlet cookie path updated to resolve error
Resolved in Pega Version 8.5.6
A very large number of exceptions were being logged indicating "Unhandled error in web.request.internal.URLComponentProcessorImpl.populateCSRFToken", impacting the ability to perform log analysis. This exception has been resolved by updating the pushservlet cookie path.
INC-176138 · Issue 668937
Decision table query performance improvements
Resolved in Pega Version 8.5.6
Work done previously to improve performance by preventing the decision rule from being treated as a custom rule has been further augmented by preventing the standard Declarative Rules from being treated as Custom Rules while building the Declarative Cache.
INC-180891 · Issue 663513
Zip compression added for tracer XML
Resolved in Pega Version 8.5.6
After upgrading from Pega 7 to Pega 8, attempting to save and download a trace session would run for a time before pausing and displaying the message "Operation failed. Network error". Investigation showed the tracer was generating a very large XML file which was consuming the heap and causing the issue. To resolve this, an update has been made that will reduce memory usage by using GZip compression on the file. The new behavior will be to always zip tracer XML by default.
INC-180901 · Issue 666445
Heap dump ability added for OpenJDK
Resolved in Pega Version 8.5.6
Support for OpenJDK has been added to the heap dump generation process.
INC-181773 · Issue 685435
Attached zip file has correct extension
Resolved in Pega Version 8.5.6
When using a custom function with the SendSimpleEmail activity, an attached .zip file was corrupted on receipt. The issue was not present with other mime types (ex. images, docs, pdf). Investigation traced this to the extension for the zip file being incorrectly set as xzip or multipart, and this has been resolved by adding a condition to set the extension correctly.
INC-182082 · Issue 694613
API added to handle digital signing from proxy layer
Resolved in Pega Version 8.5.6
When an email account was configured with a valid email account and keystore for message signing, it was possible to send emails with valid digital signatures. When the same email was used in case type email instantiation, no digital signatures were included in it. This was due to keyStoreInstance properties being read from the email account top level page when they need to be retrieved from pyEmbedSenderProtocol page when using SMTP. This has been resolved by adding an API to handle the signing logic from the JavaEmailClientProxy class.
INC-182148 · Issue 668007
Handling added for missing schema for persistClusterState
Resolved in Pega Version 8.5.6
The message "Error retrieving database indices java.lang.NullPointerException" was being logged repeatedly, indicating an issue with ClusterManagementAPI. Investigation showed there were missing default Schema values in the prconfig files, and this has been addressed by adding fallback scenarios for missing schema information during PersistClusterState.