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 note: beginning with the Pega Platform 8.7.4 Patch, the Resolved Issues have moved to the Support Center.

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-D89428 · Issue 550391

Data Flow StartTime uses locale timezone

Resolved in Pega Version 8.3.3

The start time of the dataflow was displayed in GMT instead of the operator locale timezone. This has been corrected.

SR-D77157 · Issue 544471

DataSet preview will use date instead of datetime

Resolved in Pega Version 8.3.3

While using a DataSet preview functionality, the date appeared as reduced by one day. This has been resolved by parsing date as 'date' instead of 'datetime' to avoid issues with timezone interactions.

SR-D21808 · Issue 490282

Filter values retained when editing a report with custom filters

Resolved in Pega Version 8.1.6

After running a report, if some filter values were selected and then the Edit Report button was clicked and simulated data and actual data fields were toggled, the filter values were lost when exiting the report editor. In the Edit Report Page, trying to drag a new filter condition was not working and the Change logic buttons were not visible. These functions worked as expected when a custom Filter section was not used. This was traced to the custom filter page being cleared in the pzCreateCustomFilterPage activity where the step for creating new page should be skipped if it already exists. To resolve this, a parameter will be set to show if the report was rerun in "reRunReport", and a check has been added in pzCreateCustomFilterPage to see if the report was rerun before running the other 'when' conditions.

SR-D20817 · Issue 499921

Async cache checking updated for interaction reload use

Resolved in Pega Version 8.1.6

A thread level data page using connect REST to get data from an external system with the "Reload once per interaction" checkbox ticked was being loaded asynchronously from the activity when by default the data page it was supplying needed to be loaded synchronously. Due to this, changes to the data in the external database were not reflected in the data page. This was caused when an async cache was referred and the freshness check for the data page instance did not consider the 'reload once per interaction' flag because it would cause the data page to load twice. The cache checking has been updated to resolve this.

SR-D84480 · Issue 546187

FilterHistory decision tree used for audit log status

Resolved in Pega Version 8.3.3

Attempting to use the “FilterHistory” decision tree in the work class to return value “false” for “pyCloseOpenAssignmentsOnResolution” to hide the “pyCloseOpenAssignmentsOnResolution” field value (“Unfinished assignments were cleaned up by the system after the completion.. ”) from history was not working as expected, and still returned the audit message. This was due to the system setting this AuditNote parameter within the “pzProcessResolutionStage” activity, where Param.UpdateHistory was set to true always. In order to support more flexibility, the Param.updateHistory paramter in step3 of the pzProcessResolutionStage activity will be set based on the FilterHistory decision tree. When set to false in FilterHistory decision tree, pyCloseOpenAssignmentsOnResolution will be set as false and audit will not be logged.

SR-D18217 · Issue 489811

Corrected PDF generation when an image filename has special characters

Resolved in Pega Version 8.1.6

When using Export to PDF with an uploaded image file that had special characters in its name, the images were missing from the generated document. This has been corrected by updating the decoding of the URL to not remove the checksum when using RTE.

SR-D12511 · Issue 484664

Corrected error when resolving subcase from Review harness

Resolved in Pega Version 8.1.6

An error occurred when resolving a subcase if it was opened from the review harness. It was possible to resolve the subcase successfully if the local action was invoked from the Perform harness. Investigation showed that the update status was called twice, once from pyForcecaseclose and again from the update status of the activity. This has been resolved.

SR-D15275 · Issue 490025

Report title displayed properly when prompting for filter changes

Resolved in Pega Version 8.1.6

Launching a report from the report browser showed a blank for "Report tab title" if the option "Prompt for filter changes before displaying report" was checked. This has been corrected by adding pzRDWinTitle to the harness Code-Pega-List.pzRRDisplaySection so it will display the name of the report when prompting for filter changes.

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