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-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-A2733 · Issue 221219

Migration process handles underlying varchar CHAR

Resolved in Pega Version 7.2

Handling for CHAR length semantics has been added for imports of rule schema to support Oracle varchar2 columns, and the import/export will correctly deal with the circumstanced columns of CASETYPEVERSION and PXREFOBJECTCLASS.

SR-A11286 · Issue 224545

Drop Index SQL updated to remove duplicates

Resolved in Pega Version 7.2

If a query was used in SchemaManager to get all of the covered indexes for the table, firing the same query in the DB to generate XML resulted in duplicate indexes and column names. This was traced to the Drop Index SQL being generated twice, and the query to get the covered index columns from the DB has been changed to remove the duplicates.

SR-A11286 · Issue 223221

Drop Index SQL updated to remove duplicates

Resolved in Pega Version 7.2

If a query was used in SchemaManager to get all of the covered indexes for the table, firing the same query in the DB to generate XML resulted in duplicate indexes and column names. This was traced to the Drop Index SQL being generated twice, and the query to get the covered index columns from the DB has been changed to remove the duplicates.

SR-A8506 · Issue 217725

Data types pagination limit removed from Application Wizard

Resolved in Pega Version 7.2

When building a new FW application using the Application Wizard, the wizard only displayed the first 50 data types when there were more available. This was due to the source report definition used to obtain the list of Data types having a page limit of 50, and has been resolved by disabling pagination and setting "Maximum number of rows to retrieve" to "0" so all available data types will be retrieved at once.

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.

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