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-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-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.

SR-A7996 · Issue 219733

Fixed handling for updating decision trees

Resolved in Pega Version 7.2

A Decision Table was inconsistently updated when adding or deleting columns due to an error in the conditional handling for the decision tree that fetched the list of function aliases. This has been fixed.

SR-A10464 · Issue 221099

Functions properly restricted with Decision Tree SaveAs

Resolved in Pega Version 7.2

A Decision Tree configured with with 'Allow changes to function lists' and 'Allow Selection of Additional Return Actions' checked in the 'Configuration' Tab was allowing unrestricted functions if SaveAs was used instead of saving and reopening the rule. The rule save handling has been updated to resolve this issue.

SR-A11435 · Issue 222552

Compare with Checked Out working in Google Chrome

Resolved in Pega Version 7.2

Attempting to compare a rule via 'Compare With Checked Out' using an object's History >Full history > History for All Versions > version selection option was not working as expected in Google Chrome. This was an issue with obtaining the value of the input element with ID when the ID of the element was not specified, and the system has been updated to correct this.

SR-A7750 · Issue 220071

Decision Tree Rule Form shows custom actions

Resolved in Pega Version 7.2

In some installations, values configured in the "Take Actions" or "Actions" dialog were not visible even though they had been configured. The values could be seen in the rule XML and the rules worked as expected. This was traced to the configuration using a custom Function "AddActionRecord" Alias, and a new step has been added to make such values visible.

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