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-B95191 · Issue 341933

Conditional Required fields fixed when working with accessibility

Resolved in Pega Version 7.4

When Accessibility is in place, the Conditional Required for fields was not working as expected, instead making the fields always required. To correct this, the tag will be generated conditionally after evaluation of required configuration.

INC-185847 · Issue 669526

Handling added for disabling weekends when no weekends are available

Resolved in Pega Version 8.7

A browser exception was generated while selecting the option “Disable weekends”. This was traced to a malformed array of weekends in a scenario where the Data-Admin-Calendar instance had all business days checked (i.e., no weekends). To resolve this, DatePickerAssembly and pzGenerateDatePicker have been updated to handle the case when there are no weekends available in the Data-Admin-Calendar instance.

SR-B75373 · Issue 328291

Fixed error when updating change tracking in declare expressions

Resolved in Pega Version 7.4

An error occurred when trying to update the change tracking in a declare expression rule. This was caused by ACR using a reference to an old expression rule cache, and has been corrected by updating the code.

INC-127891 · Issue 564726

Added check for redirects when getting images from S3

Resolved in Pega Version 8.2.7

When retrieving images from S3 storage, a 303 redirect status response code was shown. Investigation showed that using a public URL caused the redirects, and this has been resolved by adding an AG hash while fetching images via an activity.

SR-B94506 · Issue 341185

Unneeded clipboard use cleared during sync

Resolved in Pega Version 7.4

During the "delta sync" process, a very large clipboard size (96 MB) was observed for offline sync service requestors. Further analysis showed that the application page contained a property pyOfflineCases which increased the application page size from 28K to 679K. Since the property isn't present in the saved application rule model, the pzDataSyncPackager rule will clear it from the clipboard to improve performance.

SR-D81659 · Issue 548900

Handling added for encrypted messages using IMAP

Resolved in Pega Version 8.2.7

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-D68328 · Issue 557749

Unload handler added for use with custom popups

Resolved in Pega Version 8.2.7

A memory leak seen in Microsoft Internet Explorer was traced to a custom script to close windows which bypassed window unload and continued to hold some objects in memory. This has been resolved by introducing a new file which will load only for popup harnesses and which registers the unload handler to remove the popup window references.

INC-177323 · Issue 672420

Search string wildcard use documentation updated

Resolved in Pega Version 8.7

The support article for the search API has been updated to clarify the ability to use the wildcard character "*" by manually adding it to the prefix of each term in the search string.

INC-173162 · Issue 650795

Certificate match will use Subject Distinguished Name

Resolved in Pega Version 8.7

Signature verification was failing due to the system not finding the matching root certificate for the chain. The root certificate was in the trust store, but the system found a different certificate first and that other certificate (an intermediate certificate) was not considered a valid certificate for validating the whole certificate chain. This was traced to filtering on the Issuer Distinguished Name (DN) instead of the Subject DN and was due to intermediate certificates potentially having the same Issuer as a root certificate (e.g. if that root certificate was used to create the intermediate certificate). To resolve this, an update has been made to check the Subject DN instead of Issuer DN.

INC-189047 · Issue 674759

Session timeout adjusted for use with Apple Safari

Resolved in Pega Version 8.7

A configured browser session logout timer was not working with the Apple Safari browser. This was traced to browser-specific handling for self.location.href and has been resolved by adjusting the logic and moving it inside a setTimeout to improve cross-browser compatibility.

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