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-A22547 · Issue 252633

Cookie handling added to CMIS

Resolved in Pega Version 7.2.2

Support has been added to use cookies with CMIS to allow connecting to FileNet via connect-cmis.

SR-A24408 · Issue 248682

Page clearing added for AuthReqContex

Resolved in Pega Version 7.2.2

The page "AuthReqContex" was loaded up during SAML authentication and then passivated, but the pages were retained in the clipboard and improperly activated by an unknown thread, causing an error. This has been resolved by adding Page-Remove steps wherever needed in auth activity and logout activity (AuthReqContext, LoginInfo, ReqInfo, RelayStateInfo, and SessionInfo) to remove the pages that are no longer needed.

SR-A22699 · Issue 248560

RuleServiceFile.parseRecordAtTime and RuleServiceFile.parseByRecordType Timer function corrected

Resolved in Pega Version 7.2.2

The Timer function used in the RuleServiceFile.parseRecordAtTime and RuleServiceFile.parseByRecordType functions was not properly halting when it encountered an exception, causing any subsequent invocation to these methods to start the Timer again. This created errors and incorrect results. The parseRecordAtTime and parseByRecordType methods have now been updated to enclose inbound mapping related stopTiming within a finally block for accuracy.

SR-A87711 · Issue 255629

REST query key maps invalid characters to underscore

Resolved in Pega Version 7.2.2

When creating a REST Service with query key=value pairs that contains keys with dots/periods, the inbound mapping could not handle the keys and failed with an HTTP 500 error. To resolve this, changes have been made in the service API to locate any invalid character (according to ParameterPages) in a key to be mapped and substitute an '_' (underscore) character.

SR-A76677 · Issue 253493

IDP SAML 2.0 schema validation error resolved

Resolved in Pega Version 7.2.2

When generating the Pega SP metadata after importing the Shibboleth IDP metadata, the error "The metadata does not pass the SAML 2.0 schema validation" appeared. This has been resolved by modifying the pzDownloadSPMetadata activity to generate a unique secure random ID prefixed with an underscore.

SR-A86387 · Issue 260734

Filename check updated for saving java sources to DB

Resolved in Pega Version 7.2.2

A "Problem saving Java sources to database" error was observed in the log intermittently in a system with java security enabled at web server level when there was an attempt to save assembled classes to the database with an incorrect package name (the full file path instead of com.pegarules.generated...). Before the save is done, there is a check on the package name to see whether it starts with "com.pegarules.generated" to ensure that only generated classes are saved to the database. With Java Security enabled, the system specified the entire file path as the package name and the check failed. To resolve this, the existing function has been modified to use the package name instead of the full file path.

SR-A91341 · Issue 259908

Resolved thread deadlock for AsysncServiceManager and PRHazelcastPublishService

Resolved in Pega Version 7.2.2

A deadlock was found with the locks in AsysncServiceManager and PRHazelcastPublishService where the node would receive a new message on a channel which was currently being removed. This has been fixed by updating the logic to detect and avoid locks in situations where the channel is being removed.

SR-A90203 · Issue 258113

Rule caching not disabled with BIX

Resolved in Pega Version 7.2.2

After installing AES, it was noticed that the rule cache was being disabled on any nodes running BIX. Analysis determined that the BIX extract rule was being run by an agent that calls pxExtractDataWithArgs which was turning off Rule Caching (SMA > Advanced > Rule Cache Management), and this has been fixed by modifying the BIX code to enable rule caching in this case.

SR-A92845 · Issue 260275

Rule caching not disabled with BIX

Resolved in Pega Version 7.2.2

After installing AES, it was noticed that the rule cache was being disabled on any nodes running BIX. Analysis determined that the BIX extract rule was being run by an agent that calls pxExtractDataWithArgs which was turning off Rule Caching (SMA > Advanced > Rule Cache Management), and this has been fixed by modifying the BIX code to enable rule caching in this case.

SR-A76604 · Issue 261706

Fixed corrupted reference property in column population

Resolved in Pega Version 7.2.2

After running the column population utility, the reference property information was getting corrupted. This was traced to a missing use case in the reuse and wrapping of data structures in targeted encoding, and has been fixed with improved handling for the reference marker information.

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