SR-D67142 · Issue 548643
Enhanced CMIS connector logging
Resolved in Pega Version 8.4.2
Additional diagnostic logging has been added to enhance investigating CMIS connector health.
SR-D67308 · Issue 552345
fetchWSDLDocument rule withdrawn
Resolved in Pega Version 8.4.2
The fetchWSDLDocument rule has been marked as withdrawn.
SR-D74376 · Issue 552261
Check added for string vs boolean for pzscan JSON
Resolved in Pega Version 8.4.2
When calling the CloudRemoteMaintenance/Work-/pzscan API, the response JSON had boolean values in the form of String which caused the JSON parsing to fail. The system was using ClipboardProperty.toStringValue() while generating outbound JSON from the clipboard page, which did not correctly interpret a boolean value. To resolve this, a check has been added that will assess the value and invoke ClipboardPage.toBoolean() when needed so that the value is converted as per type before generating the JSON.
SR-D83329 · Issue 546660
AWS S3 client SDK upgraded
Resolved in Pega Version 8.4.2
The com.amazonaws group has been updated to version 1.11.740 .
SR-D85940 · Issue 548334
AWS S3 client SDK upgraded
Resolved in Pega Version 8.4.2
The com.amazonaws group has been updated to version 1.11.740 .
SR-D87671 · Issue 551411
PegaCESvcsIntegrator security updated
Resolved in Pega Version 8.4.2
Security updates have been made which now require authentication to consume the services from the PegaCESvcsIntegrator package.
SR-D87673 · Issue 552487
IACservice security updated
Resolved in Pega Version 8.4.2
Security updates have been made which now require authentication to consume the services from IACservice packages.
SR-D88499 · Issue 551189
Check added to minimize Obj-Open-By-Handle error logging
Resolved in Pega Version 8.4.2
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.
SR-D89144 · Issue 565220
Email attachment linefeed formats preserved between Oss
Resolved in Pega Version 8.4.2
When MIME attachments were stored in Data-WorkAttach-File instances and then later attached to outgoing email sent by Outlook, text files that originally had the Unix linefeeds (LF) had those changed to the Windows CRLF line endings when the Content-Transfer-Encoding is set to 7bit. To resolve this, the java mail DSS email/encodeEolStrict now defaults to true to preserve line endings in outbound email.
SR-D90311 · Issue 549729
Parse Delimiter rule updated for special character handling
Resolved in Pega Version 8.4.2
Attempting to run a Parse Delimiter rule with a CSV file was failing with a 400 bad request and the message "Invalid character found in the request target. The valid characters are defined in RFC 7230 and RFC 3986." Inspecting the HTTP request showed this was an issue with the \ character value being present in the FilePath property. To resolve this, encodeURIComponent() has been implemented to ensure the FilePath parameter of the HTTP Request meets Tomcat restrictions.