Skip to main content

Resolved Issues

View the resolved issues for a specific Platform release.

Go to download resolved issues by patch release.

Browse release notes for a selected Pega Version.

NOTE: Enter just the Case ID number (SR or INC) in order to find the associated Support Request.

Please update your bookmarks. This site will be discontinued in Dec 2024.

Pega Platform Resolved Issues for 8.1 and newer are now available on the Support Center.

SR-D72886 · Issue 543756

Check added for Repositories before saving attachment

Resolved in Pega Version 8.4.1

When creating or updating a case through email listener, the Link-Attachment defaulted the pxStorageType to 'WebStorage'. This caused an issue when using PegaS3, which needs pxStorageType 'Repository'. To resolve this, a check has been added to see if Repositories are enabled, and if they are the storageType will be set accordingly.

SR-D75945 · Issue 541084

Data transform updated to remove @java references

Resolved in Pega Version 8.4.1

The usage of @java expressions in data transform rules has been deprecated. The pyProcessDocumentCompletedEvent data transform was given as an extensible data transform intended to be overridden by customers to have their own processing logic of document completion event, however this caused confusion and when used in the out-of-the-box form it resulted in an error when saved at design time. To resolve this, the shipped data transform has been updated to call to a Rule-Utility-Function to return the file's base name, and the @java references have been removed.

SR-D76291 · Issue 541016

Check added for Repositories before saving attachment

Resolved in Pega Version 8.4.1

When creating or updating a case through email listener, the Link-Attachment defaulted the pxStorageType to 'WebStorage'. This caused an issue when using PegaS3, which needs pxStorageType 'Repository'. To resolve this, a check has been added to see if Repositories are enabled, and if they are the storageType will be set accordingly.

SR-D78531 · Issue 542002

Encoding added for special characters in JFROG filenames

Resolved in Pega Version 8.4.1

A blank screen or the error "Unable to get the file from Repository" appeared when attempting to attach a file from JFROG Repository if the file name contained special characters. This has been resolved by modifying the artificatory URL generation to properly encode special characters during file download.

SR-D81651 · Issue 545239

Added check for signed-data in encrypted email

Resolved in Pega Version 8.4.1

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-D81673 · Issue 546397

ClipboardToJSON Serializer enhanced

Resolved in Pega Version 8.4.1

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-D82490 · Issue 547366

Invoke Connect-SAP method of IDoc type repaired

Resolved in Pega Version 8.4.1

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-D85699 · Issue 548664

DASS given for overriding boolean transformation to true/false

Resolved in Pega Version 8.4.1

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-D87870 · Issue 548774

Resolved putting JMS Message through JMS Listener interface

Resolved in Pega Version 8.4.1

When using MS Listener integrated into Pega running on WebSphere Liberty, the listener was running correctly and able to consume JMS Messages. The JMS Listener ruleform provided options to browse and put JMS messages. However, when attempting to put a message into the destination queue, an error occurred. Investigation showed that if the resource lookup was using 'Resource references' on JMS Listener, the naming context was initialized with a null hashtable. This has been corrected by modifying AddJMSMessage and GenericViewJMSMessage to initialize the naming context with the default constructor RefreshJMSMessages to set JNDIServerName and pass the current parameter page when calling GenericViewJMSMessage.

SR-D88376 · Issue 548336

SQL query handling added for case-sensitive DBs

Resolved in Pega Version 8.4.1

An Email Listener in RUNNING state was not picking up the emails as expected. This was traced to the column names (pr_log_service_email) being defined in lower case for native SQL queries: since MS SQL server db is case sensitive, it was not able to detect these column names and therefore failed to save the message stub. This has been resolved by adding the necessary handling.

We'd prefer it if you saw us at our best.

Pega.com is not optimized for Internet Explorer. For the optimal experience, please use:

Close Deprecation Notice
Contact us