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-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-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-A9198 · Issue 218533
Text retrieval for deprecated "Query" button updated for universal browser support
Resolved in Pega Version 7.2
The Firefox popup window provided by the Product rule when querying "Individual Instances to Include" failed to transpose the selected rule information back into the Product ruleform when the OK button was clicked. This was due to the use of the deprecated "Query" button, which does not have support for all browsers, to launch the ListView. To handle this, the node text retrieval method in DataInstancesQueryScript has been updated to use the 'textContent' function (compatible with all browsers) instead of the previous 'innerText'.
SR-A10839 · Issue 222017
Added handling for null rollback info in hotfix autocommit
Resolved in Pega Version 7.2
If AutoCommit was selected while installing a hotfix, the auto-commit would fail and leave the hotfix in an Uncommitted state if there were dependent hotfixes where changes were covered by the parent and the child was superseded after installing the parent. Manual commitment of the hotfix worked as expected. This was an edge case where the older hotfix did not get rollback information saved since its components were already installed or superseded, and AutoCommit has been updated to handle this missing information.
SR-A10327 · Issue 222830
Upgrade Assistant enhanced to better resume interrupted process
Resolved in Pega Version 7.2
If the system suffered a crash during upgrade, IUA was incorrectly identifying the DB as having completed the upgrade and would import outstanding rules based on the perceived Database BLOB version. This led to a storage-type mismatch between Prod and all lower environments, and BIX jobs would fail due to not being upgraded. An enhancement has been added to the Upgrade Assistant to correctly resume an interrupted upgrade process.