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-A5351 · Issue 216605

Optimized Clipboard reference processing

Resolved in Pega Version 7.2

Enhancements have been made to optimize reference properties processing for the ClipboardPageImpl.expandAllIfUnexpandedReferenceProperties method.

SR-A7513 · Issue 218791

Corrected timing of OnMessage firing on restart

Resolved in Pega Version 7.2

MDB Listeners that have been processing incoming messages successfully were becoming problematic when the JVM was restarted. At that time, PRJMSListener's onMessage() started to process JMS messages from the queue even when the PegaRULES engine had not successfully initialized, resulting in large numbers of repeating error messages in the log file. In order to resolve this, the PRJMSListener.java has been updated to check the node initialization in OnMessage() itself instead of invoke() of JMSListenerServant.

SR-A6621 · Issue 221216

Fixed locking on node level declare pages

Resolved in Pega Version 7.2

In a scenario where data is being loaded from external system using an activity, the data page should be loaded only once for the first requester and all following requestors should refer to the loaded data page until it is expired. However, when multiple users accessed the data page simultaneously, the data page was being loaded for each one. This was traced to a timing issue with locking, and ReadOnlyDataPageHandler->loadDataPage() has been updated to insure node level data pages do the 'put' operation before releasing a lock.

SR-A4310 · Issue 212995

Fixed locking on node level declare pages

Resolved in Pega Version 7.2

In a scenario where data is being loaded from external system using an activity, the data page should be loaded only once for the first requester and all following requestors should refer to the loaded data page until it is expired. However, when multiple users accessed the data page simultaneously, the data page was being loaded for each one. This was traced to a timing issue with locking, and ReadOnlyDataPageHandler->loadDataPage() has been updated to insure node level data pages do the 'put' operation before releasing a lock.

SR-A11245 · Issue 222247

Designer Studio query/filter matching improved

Resolved in Pega Version 7.2

The activity to fetch instance lists in Designer Studio uses a query which performs an UPPER() operation against the pzInsKey column of the target rule table, but the Ignorecase option was being used for the pzInskey filter. The filter has been modified to use toUppercase edit input for filter value.

SR-A15878 · Issue 230806

Elastic Search updated for external tables

Resolved in Pega Version 7.2

Elastic Search on an external table was returning incorrectly limited results. This was an issue with passing more than one property set in the query to the external table, and has been resolved by updating AbstractIndexer to add additional properties.

SR-A11148 · Issue 222428

Elastic Search updated for external tables

Resolved in Pega Version 7.2

Elastic Search on an external table was returning incorrectly limited results. This was an issue with passing more than one property set in the query to the external table, and has been resolved by updating AbstractIndexer to add additional properties.

SR-A11148 · Issue 221666

Elastic Search updated for external tables

Resolved in Pega Version 7.2

Elastic Search on an external table was returning incorrectly limited results. This was an issue with passing more than one property set in the query to the external table, and has been resolved by updating AbstractIndexer to add additional properties.

SR-A11637 · Issue 228995

Newlines encoded for CSV import

Resolved in Pega Version 7.2

A new line character within the csv fields was treated incorrectly and parsed as an end of a row in csv during import. To avoid this, the parsing logic has been changed to handle new line characters within the fields.

SR-A6931 · Issue 219233

Improved rule SAVE AS performance

Resolved in Pega Version 7.2

In order to improve the performance of the SAVE AS of any rule type, a local cache will be created to better handle the isRuleSetInDependencyPath API.

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