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-A392 · Issue 204598

Updated SQLgenerator to avoid creating unneeded implicit DBs

Resolved in Pega Version 7.2

There is a known bug with Oracle JDBC drivers with handling synonyms when using getMetaData to get the database table details. For 7.1 installations/upgrades to split schema, if the customer has synonyms on the database for totally unrelated PRPC schemas it can cause issues with the upgrade. There were various ways to work around the issues (creating private synonyms for all of the tables in the new schema, upgrading to a single schema and then splitting, etc.) but to ease this process the system's SQLGenerator now has a check for zOS specific logic in order to ensure the generic table creation ddl will not be generated when it's not needed, as this was causing unnecessary implicit databases to be created.

SR-A9070 · Issue 221177

Updated caches for Data-Admin-DB class groups

Resolved in Pega Version 7.2

Data-Admin-DB-Table, Data-Admin-DB-Name, and Data-Admin-DB-Class Group were not receiving updated cache entries for newly exposed columns. This was an error in the updated database triggers engine code, and has been corrected.

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

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-A10518 · Issue 220215

Resolved exception for processing blank email body

Resolved in Pega Version 7.2

Processing was failing when the body of an email message was blank. In addition, the auto-reply header was being processed unnecessarily. Changes have been made to EmailListener.java to handle these scenarios.

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