INC-148544 · Issue 606250
Handling added for unclosed bracket in getLocalizedText
Resolved in Pega Version 8.6
A StringIndexOutOfBoundsException error was occurring when using the getLocalizedText method of ClipboardProperty class if the property's value included an unclosed bracket. E.g.: property value is "(123456". This has been resolved by adding handling in MessageEvaluator.java for this scenario.
INC-148582 · Issue 607073
Check added to minimize Obj-Open-By-Handle error logging
Resolved in Pega Version 8.6
When using a Data Type with the "Automatically generate a unique id " option, calling the Save-DataPage method by using the savable data page of the data type finished correctly but showed Obj-Open-By-Handle errors on PegaRules.log. Investigation showed the exception was thrown when running the save plan from DataPageSaverImpl: while attempting to run the save plan, the system does not know whether a parameter (pyGUID in this case) will be required to run the save plan or not, meaning that it can't detect any possible error in DataPageSaverImpl. The implementation instead makes a call to db.open to check if an instance exists and hence logs are thrown. To resolve the error logging, a check has been added: if the save-to class has an autogen key and the savable data page instance doesn't have the autogen key in it, the system will directly call pxCreateRecord. This will avoid a call to db.open to check if instance exists and hence no failed logs will be thrown. This partial change will work only for classes having an autogen key and in cases where the page is trying to create a record by intentionally not passing the key.
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.