INC-144917 · Issue 598199
Healthcheck will only initialize after successful node startup
Resolved in Pega Version 8.6
Nodes were not starting up, but because the Healthcheck service was initialized even though the node was not started properly, errors related to that were overriding the actual exception causing the node startup to fail and it was not possible to diagnose the startup issue. To resolve this, an update has been made that will ensure the Healthcheck service is only initialized when the node is initialized successfully.
INC-144978 · Issue 600589
Updated JSON DT nested page property handling
Resolved in Pega Version 8.6
In a JSON data transform, when using an "Update page" step on a single-page property, as a child step of an "Append and map to" step where a page list property is given, the page list was populated with only one result but the single-page property was treated like a page list and received multiple results. This has been resolved by updating the ClipboardJSONDeserializer implementation and downstream abstractions to support "clipboard only" relations as properties in nested Page Lists.
INC-144982 · Issue 615338
Log-Service-File persistence logic updated
Resolved in Pega Version 8.6
When "Persist Log-Service-File instances" was unchecked and set to false, the process was still writing and committing the Log-Service-File table for every record processed from the file. This was traced to logic that always overrode the setting, and has been resolved by updating the system so the Log-Service-File will only be saved if it meets the conditions check of the setting. If the File Listener is recovering and "Persist Log-Service-File instances" is false/unchecked, the old and the current Log-Service-Files will be deleted.
INC-145255 · Issue 600273
EmailListener restart correctly reflects Inbox folder change
Resolved in Pega Version 8.6
The Email Listener did not pick up a change in the INBOX folder name when the listener was restarted, but did when the server itself was restarted. This was due to the folder name being cached but not being included in the cache key: a cache change only occurs when the key of the cache changes. This meant that even after changing the folder name, the object was treated as 'not changed' and returned the older connection with older folderName. This has been resolved by adding the foldername to the cache key.
INC-145756 · Issue 619295
Logging for MultiNodeSynchronize lock attempts changed from error to warn
Resolved in Pega Version 8.6
The File Listener was logging numerous errors stating "Unable to establish MultiNodeSynchronize lock while trying to determine if listener is enabled for this node". Handling has been previously established for error cases when the Listener is unable to establish a MultiNodeSynchronize lock, but this condition continued to be logged as an error even though it was not related to any failures in functionality. To resolve the logging issue, the logger level has been changed from ERROR to WARN.
INC-146030 · Issue 602604
Added queue process tracer cleanup on node restart
Resolved in Pega Version 8.6
If a node restart occurred while a queue process trace was in progress, some entries in the tracer distributed map were not cleared properly and a subsequent tracer failure was encountered indicating a current trace by a requestor on same operator Id was already running. This has been resolved by clearing the tracer distributed map on node startup for stale entries associated with this node.
INC-146057 · Issue 599806
Secure access for Activities
Resolved in Pega Version 8.6
Authentication requirements have been added to Standard activities.
INC-146123 · Issue 601119
SOAP service exception resolved
Resolved in Pega Version 8.6
A SOAP service created using the Service wizard resulted in a "Caught exception building SOAP request envelope" error when attempting to invoke the generated service/WSDL from the Soap integration wizard or SOAPUI. This was traced to an unexpected conflict with work done earlier in XSDConstants.java around name case matching and certain methods in XSDTreeViewUtils used to generate the attribute text "name" during SOAP service WSDL generation, and has been resolved.
INC-146610 · Issue 614423
MimeTypeHandler added for cloud downloads on mobile
Resolved in Pega Version 8.6
When using the Pega cloud storage repository (Application -> Integration -> Content Storage) with the Google Chrome browser on an android device, it was possible to upload attachments but re-downloading the attachments failed. Investigation showed that this was due to the content-type appearing as application/* so Google Chrome on mobile was not able to identify the file type. This was a missed use-case for returnFileForDownload(), and has been resolved by setting the system to use MimeTypeHandler for getting the content type.
INC-146752 · Issue 602934
File Listener made more resilient
Resolved in Pega Version 8.6
When file listener encountered a FileNotFoundException as a consequence of sporadic AmazonS3Exceptions, the listener was disabled and no retries were made. In order to make the file listener more resilient, FileMatchConcentrator has been updated. While file listener is running and trying to get the next set of files, if the isDirectory() method returns false due to a non-existent directory or some other intermittent issues, instead of throwing an exception and shutting down the file listener, the system will now log the exception and continue.