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.
SR-A12287 · Issue 223279
Alter Script generates correct SQL for Oracle db
Resolved in Pega Version 7.2
During installation, an incorrect Alter Script was being generated while importing the JAR file due to a missing check on the 'required' XML attribute for dbtype Oracle to decide whether it should be null or not null. This has been corrected to honor the 'required' attribute and accordingly the generated SQL will be appended with null/not null string.
SR-A12687 · Issue 226506
Skimming logic corrected
Resolved in Pega Version 7.2
The skimming logic (PegaRULESMove_Skimming_Query) has been updated to correctly repopulate the query page in order to return a more accurate rules count.
SR-A2733 · Issue 220049
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.