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.
SR-D72389 · Issue 541945
Handling added for JSON with top level array
Resolved in Pega Version 8.3.3
When using serialize mode in a JSON data transform where the Top element structure was Array and the “For JSON only” relation was selected for relation mode, the result had an incorrect JSON structure. In order to support this configuration, generatePropertyAsJSON has been amended to set isTopLevelPageList to true in instances where automap is off, the top level is an array, and the JSON context is updated within the first step. In addition, generatePageAsJSON has been updated to check this flag when processing mappings in order to ensure these context changes are processed, and updates have been made to generatePropertyAsJSON to ensure that the context is popped when appropriate.
SR-D88997 · Issue 548895
Improved accessibility for labels and instructions
Resolved in Pega Version 8.3.3
In order to improve accessibility, a label has been added to the delegation filter input and a search input box has been added to pzRecordsEditorWrapper along with the ability to use the 'Cell read-write classes' option to hide it in the UI.
SR-D82490 · Issue 547364
Invoke Connect-SAP method of IDoc type repaired
Resolved in Pega Version 8.3.3
Attempting to implement SAP connection via IDoc type connector failed and an empty error message was shown. This has been resolved with modifications to the SAP Connector functionality.
SR-D90311 · Issue 549726
Parse Delimiter rule updated for special character handling
Resolved in Pega Version 8.3.3
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.