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.

INC-167606 · Issue 657153

Optimization prconfig check added for TableInformationMap

Resolved in Pega Version 8.5.5

A prconfig setting check has been added to the TableInformationMap use of OPTIMIZE_SMA_QUERY during its foreign key lookup.

INC-185758 · Issue 668961

Optimized GenerateID feature for case creation

Resolved in Pega Version 8.5.5

Enhancements have been added to support high-performance high-volume case ID generation on multiple databases including Oracle , MS-SQL, and Azure.

INC-176138 · Issue 723082

Performance improvements for save-as

Resolved in Pega Version 8.6.5

Performance issues were seen when using save-as for rules such as Declare expression, When rules, activity, etc. This was traced to a very large number of extra database queries that were being executed while building the Declarative Cache. To resolve this, an update has been made so the queries used for the Declarative Cache will only be executed when required.

INC-186904 · Issue 669744

Removed duplicate alert events

Resolved in Pega Version 8.6.5

Duplicate applications were seen in the PDC Event Viewer, e.g. ‘Adviser 01.01’ and ‘Adviser:01.01' - one without a colon and one with a colon. Investigation showed that alert events logged via AsyncServices were being logged as "ApplicationName Version" instead of "ApplicationName:Version", and this has been resolved by updating AsyncServiceBatchTask.java to use the expected application name while logging alert events.

INC-193485 · Issue 695641

REST authentication settings use fully qualified name for resolution

Resolved in Pega Version 8.6.5

The application setting used in REST connectors for authentication was resolving to similarly-named rules instead of matching the exact name of the rule. This has been resolved by enhancing pzGetSettingID to use both parts of the fully qualified name (name and category) provided by the pzSettingsORA control when determining which setting from the report to return.

INC-198555 · Issue 720901

Performance improvements for save-as

Resolved in Pega Version 8.6.5

Performance issues were seen when using save-as for rules such as Declare expression, When rules, activity, etc. This was traced to a very large number of extra database queries that were being executed while building the Declarative Cache. To resolve this, an update has been made so the queries used for the Declarative Cache will only be executed when required.

INC-203040 · Issue 721057

Null value handling added for CBU

Resolved in Pega Version 8.6.5

After update, changes made to the Operator record were not reflected and the Actions menu in Operator record did not show all available actions after the Operator was saved. This has been resolved by adding handling for null values passed as String for arguments from cbu.xml for the PegaCBU utility.

INC-207159 · Issue 707617

Localization added for delegated datatype tab

Resolved in Pega Version 8.6.5

Localization was not working for the title of a thread which opened when attempting to edit the delegated datatype. This has been corrected.

INC-210855 · Issue 715822

BigDecimal handling updated for @sum function

Resolved in Pega Version 8.6.5

The @sum function was not behaving correctly. This was traced to the java code in the 'sum--(ClipboardPropertyCollection)' function which was not properly converting the double to Bigdecimal for some of the inputs like 500, 500, 600.11. This has been resolved by modifying the function to convert input properties to BigDecimal, add BigDecimal values, and return the result.

INC-211655 · Issue 714061

Removed extra space in Malaysian locale

Resolved in Pega Version 8.6.5

For the ms_MY locale, an extra space was being appended to Number formats, such as " 0", " 1". This has been corrected.

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