INC-155624 · Issue 627233
Added check for .eml /.msg extension
Resolved in Pega Version 8.6
Attachments with .eml /.msg extensions were treated as FileAttachments by the MS Graph API and generating a classcastexception. To resolve this, a check has been added to identify the attachment along with content type so .eml will be correctly recognized.
INC-155851 · Issue 626046
REST connector creation errors resolved
Resolved in Pega Version 8.6
Attempting to create REST Connectors via the dev studio wizard using live endpoint invocation as "Add a REST response" was failing with a java.util.LinkedList error. This had a workaround of either running the REST wizard with file upload samples or configuring them directly on the rule form. In addition, REST Connectors were not executing if both the DEBUG level logging was turned on and the request had no headers, which had a workaround of using any other logging level (INFO, ERROR). These issues have been resolved by updating the system such that pyResponseHeaders are populated appropriately, and if there are no headers in the request, the system will not try to remove the trailing comma that would have been introduced in the oLog message.
INC-156588 · Issue 621968
File Listener creates pegaAPI reference for indirect reference
Resolved in Pega Version 8.6
When using a constant for the source location of a file, the listener had no problems starting but a severe guardrail warning appeared indicating "Source location should use D_pxGetApplicationSettingValue instead of a constant value". When the source location was changed to point to a data page as suggested, the file listener would not start. This was traced to a null pointer exception caused by the listener running on a thread that did have a reference to publicAPI as required to get the indirect reference to the property, and has been resolved by adding code to create pegaAPI (if not present) when an indirect reference is present.
INC-156674 · Issue 632661
Added handling to avoid class cast exception
Resolved in Pega Version 8.6
The error "doMaintain errorjava.lang.ClassCastException: java.util.HashMap cannot be cast to com.pega.pegarules.priv.factory.SequencedEntry" appeared in production numerous times per day, leading to exceptions. Investigation showed this was being triggered from the activity Show-harness, and was traced to the ConcurrentMostRecentlyUsedMap eviction method casting entries to Sequenced entries. There is no such check while putting entries. To resolve this, a wrapper has been added over the ConcurrentMostRecentlyUsedMap object to avoid a class cast exception.
INC-156765 · Issue 622027
Cross site scripting updates
Resolved in Pega Version 8.6
dditional cross site scripting protections have been added to pyActivity processing and pzTransformAndRun.
INC-157081 · Issue 623807
Email Listener auto-reply evaluation updated
Resolved in Pega Version 8.6
After upgrade, messages were being read but not getting processed for a specific Email listener (RCEmailListerner). The error "Email flagged as an autoreply email and will not be processed" appeared in the logs. Previously, an email was not considered to be an auto-reply only when the 'auto-submitted' header didn't exist or existed with value 'no'. This caused issues with auto-forward or auto-redirect emails where 'auto-submitted:auto-generated' could be in the header. Due to this, email was marked as auto-reply and email listener stopped processing it. To resolve this, the system has been modified to mark the message as auto-reply if it finds 'auto-submitted: auto-replied' in the header, but not 'auto-submitted:auto-generated'.
INC-157864 · Issue 630702
Compiler jars load as expected
Resolved in Pega Version 8.6
The system was not able to pick up the Default Paths and Default Classes arguments in Configure->System->Settings->Compiler tab when attempting to use a third-party custom jar file. This was an unintended consequence of work done to address performance issues when a requested DASS instance was missing, and has been resolved by ensuring that null values are not cached where are are lookup failures. In addition, enhanced logging has been added to SystemSettingsImpl.
INC-158159 · Issue 622630
JobScheduler initialization timing adjusted
Resolved in Pega Version 8.6
DDS nodes were ending up in a deadlock condition on restart, preventing them from joining the cluster. This has been resolved by ensuring the JobScheduler initialization task waits for Search to start up.
INC-158308 · Issue 624368
Cleaned up tracer exceptions for requestor inactivity
Resolved in Pega Version 8.6
After upgrade, the exception "No records were found for the lookup with keys : pyEventType=REQUESTOR-INACTIVITY" was appearing multiple times in tracer for Data-UsageEventType class. This has been resolved by changing the conditions order to decrease the number of data page loads.
INC-158314 · Issue 630718
Listener with MSGraph reads all subfolders
Resolved in Pega Version 8.6
When an email account had more than 10 subfolders, configuring an email listener with MSGraph to read subfolders 11+ was not working. This was traced to the MSGraph API displaying only the top 10 folders under one parent folder by default, preventing the Email Listener from reading folders beyond that when a MSGraph configuration was used for inbound email. To resolve this, a filter has been implemented across all the pages to read all of the folders.