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-A14108 · Issue 242466

Better handling for rules considered duplicates

Resolved in Pega Version 7.2.1

A legacy API was not properly resolving rules present in an earlier ruleset version, leading to the creation of additional rules. The system will now consider rules already present in the earlier ruleset version and present the Other duplicate screen asking to skip, overwrite, or rename the rule.

SR-A14283 · Issue 232771

Service request retry works in async mode

Resolved in Pega Version 7.2.1

The Retry mechanism has been modified to correctly pass the child requestor's status when service is configured in async mode.

SR-A14781 · Issue 246050

Timeout value honored for ConnectSOAP using JMS Transport

Resolved in Pega Version 7.2.1

ConnectSOAP has a response timeout function, but this setting was not being honored when JMS transport was used. This has been corrected.

SR-A14826 · Issue 228519

Resolved IndexOutOfBounds extraction error for page list data

Resolved in Pega Version 7.2.1

When running BIX extract rules, it was failing to extract cases information for XML output formats containing data in Page Lists in the extract rule. Excluding the page lists from the extract rule would runs and extract the data successfully. To fix this, filter() in PropertyReferenceImpl will return unmatched strings.

SR-A14841 · Issue 234741

Multiple message deletion updated in MQ Server and MQ Explorer

Resolved in Pega Version 7.2.1

When multiple messages on the MQ Server and MQ Explorer queues were selected and deleted, only the first message was deleted. This has been corrected.

SR-A14841 · Issue 234742

Multiple message deletion updated in MQ Server and MQ Explorer

Resolved in Pega Version 7.2.1

When multiple messages on the MQ Server and MQ Explorer queues were selected and deleted, only the first message was deleted. This has been corrected.

SR-A14887 · Issue 230375

Support added for MSSQL datatype MONEY

Resolved in Pega Version 7.2.1

After upgrade, generating report definitions failed if the DB contained tables with columns that used the MSSQL-specific type MONEY, generating the error "No enum const class com.pega.pegarules.data.external.rd.constants.ColumnType.MONEY". Support has now been added for this datatype.

SR-A14892 · Issue 234201

Consistent Indexing initialization

Resolved in Pega Version 7.2.1

The first node in the cluster that was started was getting stuck at "Initializing Search Infrastructure." Elastic search was causing WAS7 to fail on startup due to the instances of indexerAgents (FTSindexerAgent, SystemIndexeragent) only being initialized in distributed mode, and an NPE was generated in non-distributed mode. This has been resolved by setting the indexerAgent instances to always initialize irrespective of the DASS indexing/distributed.

SR-A15083 · Issue 237798

Cursor leak issue resolved

Resolved in Pega Version 7.2.1

Cursor leaks were observed in the LockManagerImpl code, resulting in the error "Maximum number of open cursors exceeded". This has been resolved.

SR-A15388 · Issue 231184

Reordered email encryption logic

Resolved in Pega Version 7.2.1

Encrypted email sent using the out-of-the-box Activity "@baseclass.SendEmailNotification.Pega-EventProcessing:07-10-09" to send out encrypted (s/mime) emails generated emails that could not be decrypted on the receiving end. This was an error caused by the getCertificate activity not being able to read the certificate from keystore, and the logic of pyGetEmailCertificates had been reordered such that the encryption and signing params/logic in SendEmailMessage do not conflict with one another.

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