SR-D70768 · Issue 547016
Handling added for unavailable oWnd
Resolved in Pega Version 8.3.3
After using a Snap Start URL to open an assignment, terminating the requestor and hitting the URL again resulted in a blank screen. This was traced to the pzUnknownSessionAlert script throwing an error when oWnd.pega was not available, and has been resolved by adding the needed handling.
SR-D81651 · Issue 545236
Added check for signed-data in encrypted email
Resolved in Pega Version 8.3.3
Numerous java.lang.UnsupportedOperationException messages were seen in the logs. Investigation showed that signed email which arrived as encapsulated within another email with header content-type = "application/pkcs7-mime; smime-type=signed-data; name="smime.p7m" caused the exception. This was due to a missed check for 'signed-data' while parsing the email and checking for encryption, and has been resolved.
SR-D83329 · Issue 546657
AWS S3 client SDK upgraded
Resolved in Pega Version 8.3.3
The com.amazonaws group has been updated to version 1.11.740 .
SR-D74376 · Issue 552257
Check added for string vs boolean for pzscan JSON
Resolved in Pega Version 8.3.3
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-D81673 · Issue 546395
ClipboardToJSON Serializer enhanced
Resolved in Pega Version 8.3.3
After creating a JSON data transform with the top level structure set to Object and a step that mapped a Pagelist in clipboard to an Array of Objects in JSON, calling the data transform in Serialize mode resulted in a JSON mapping exception. This was a missed usecase for using the JSON serializer with nested pagelists in page, and has been resolved by adding pagegroup support for data transform serialization and skipping pagegroup serialization when automapped.
SR-D85699 · Issue 548662
DASS given for overriding boolean transformation to true/false
Resolved in Pega Version 8.3.3
In order to ensure greater backwards compatibility, support has been added for not converting boolean values in the DOM-based Parse XML assembler based on the DASS as below :Pega-IntegrationEngine • ParseXML/DOM/DoNotConvertBooleanValues This will maintain values as 0/1 and override the default of transforming them to true/false which was enabled as of v8.3.
SR-D67142 · Issue 548640
Enhanced CMIS connector logging
Resolved in Pega Version 8.3.3
Additional diagnostic logging has been added to enhance investigating CMIS connector health.
SR-D67308 · Issue 552343
fetchWSDLDocument rule withdrawn
Resolved in Pega Version 8.3.3
The fetchWSDLDocument rule has been marked as withdrawn.
SR-D65239 · Issue 547821
Handling added for encrypted messages using IMAP
Resolved in Pega Version 8.3.3
Log errors were seen related to Email Listeners while processing encrypted emails from specific mail IDs, including "Unable to determine DSN, EmailClientRuntimeException: Unable to load BODYSTRUCTURE" and "isMimeType(JavaMailMIMEMessage - Unable to determine partIsEncryptedMessage". This issue is related to how certain servers work with the IMAP protocol to parse messages, and has been handled by creating a new instance of MimeMessage from the original MimeMessage and working on it.
SR-D81659 · Issue 548899
Handling added for encrypted messages using IMAP
Resolved in Pega Version 8.3.3
Log errors were seen related to Email Listeners while processing encrypted emails from specific mail IDs, including "Unable to determine DSN, EmailClientRuntimeException: Unable to load BODYSTRUCTURE" and "isMimeType(JavaMailMIMEMessage - Unable to determine partIsEncryptedMessage". This issue is related to how certain servers work with the IMAP protocol to parse messages, and has been handled by creating a new instance of MimeMessage from the original MimeMessage and working on it.