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-A9129 · Issue 220717

Report Definition error message localized

Resolved in Pega Version 7.2

Localization/customization has been added for the Report Definition error message : "Retrieving the report data exceeded the limit of * seconds. Please try making the report more specific by further limiting which rows to include".

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-A11421 · Issue 223667

nvarchar support corrected for MS/SQL

Resolved in Pega Version 7.2

The datatype nvarchar (used for Unicode encoded strings) in MS/SQL was incorrectly reported as unsupported. The data type mapping has been reviewed and updated to correct this.

SR-A12941 · Issue 224444

NCHAR column type added to RD supported column types

Resolved in Pega Version 7.2

After upgrade, "No enum constant com.pega.pegarules.data.external.rd.constants.ColumnType.NCHAR " exceptions were being thrown for most access to external database tables. These tables are accessed with internal methods (obj-save, obj-open, etc.). As part of refactoring the Report Definition code, explicit references were needed for external column types and only types given were supported. The NCHAR column type has now been added to the list of supported column types in ColumnType.java

SR-A12941 · Issue 230561

NCHAR column type added to RD supported column types

Resolved in Pega Version 7.2

After upgrade, "No enum constant com.pega.pegarules.data.external.rd.constants.ColumnType.NCHAR " exceptions were being thrown for most access to external database tables. These tables are accessed with internal methods (obj-save, obj-open, etc.). As part of refactoring the Report Definition code, explicit references were needed for external column types and only types given were supported. The NCHAR column type has now been added to the list of supported column types in ColumnType.java

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

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