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