INC-148944 · Issue 604101
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-149171 · Issue 604558
Improved privacy for email listener alerts
Resolved in Pega Version 8.6
To improve privacy, the customer 'from' address will be removed from PEGA0011 alerts for email listener processing.
INC-149187 · Issue 622486
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-149370 · Issue 619992
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-149375 · Issue 607830
Adjusted email listener behavior for authentication failures
Resolved in Pega Version 8.6
After upgrade, email listeners were not staying up during connection outages. This was traced to the handling of authentication failures when trying to reconnect, and has been resolved by changing the disconnected listener state to sleeping and raising an alert for authentication failures.
INC-149382 · Issue 612426
Loading timing updated for openAPI content
Resolved in Pega Version 8.6
Open API content loading was taking too much time and interfering with working on other REST rule configurations. To resolve this, the loading of openAPI contents has been removed from the opening or saving of REST rule and shifted to lazy loading. Clicking on the openAPI tab will load the contents, and any modification in REST rule or service package rule will update the contents of openAPI when "Action->Refresh" is clicked.
INC-149466 · Issue 607611
Fixed alias assigned to custom categories to handle Oracle limitations
Resolved in Pega Version 8.6
When trying to access CHAT via interaction portal, Oracle SQL was fired with incorrect syntax. This was traced to an Oracle limitation of 30 characters on the length of the table name, table alias name, or column name in database versions prior to 12.2. This is caused an SQL exception if the Pega class name was more than 30 characters. To prevent this, a fixed alias has been assigned to the custom category table.
INC-149517 · Issue 609474
Secure access for Activities
Resolved in Pega Version 8.6
Authentication requirements have been added to Standard activities.
INC-149849 · Issue 612261
DSN message mapping corrected
Resolved in Pega Version 8.6
Original-text-html was not correctly mapped to .pyInboundEmail.pyOriginalTextHtml . This has been resolved by removing an incorrect null check encountered while setting original-text-plain mapping for the DSN message while handling a DSN ReturnedMessagePart of type message/rfc822 and updating the handling for text parts which are not null.
INC-150038 · Issue 614826
Data Type local data storage snapshot history updated
Resolved in Pega Version 8.6
When a History Class Data object was created, two snapshots were made - one with value and another with no value. This was traced to a 'when' condition that evaluated whether to add history when deleting a record from records editor, and this issue has been addressed by removing the condition as the history-add step takes care of checking if there is a dedicated table or not.