SR-A10662 · Issue 220678
NVARCHAR2 support added for Oracle
Resolved in Pega Version 7.2
NVARCHAR2 support has been added for Oracle to handle Japanese and other special characters in Report Definition columns.
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-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.