SR-A3914 · Issue 212709
Added null check to handle uninitialized object in prweb/PRServlet URL
Resolved in Pega Version 7.2
A NPE error was seen on the UI and in PegaRULES log when accessing PegaRULES URL when PRPC was deployed as an enterprise application and transaction type was "CMT" or "Container". This was found to be caused by the prthread object in EngineAPIclass not being initialized at the time the operation was called, and a null check has been added to handle such cases.
SR-A4720 · Issue 212436
Corrected focus for tabbing Ruleset inclusion data entry
Resolved in Pega Version 7.2
Data entry for "RuleSets To Include" was behaving unexpectedly when using keyboard-only input: when a value was entered in the "Minimum Version" text field, pressing TAB on the keyboard shifted focus from the next textbox to the top of the sheet due to a row-refresh added for app context. This has been corrected.
SR-A4078 · Issue 211396
Eliminated duplicate results from Pega Usage Validation Utility (UVU)
Resolved in Pega Version 7.2
The Pega Usage Validation Utility (UVU) is a legacy tool for collecting data from older PRPC systems during system usage audits. Due to system changes, the results on newer installations included duplicate record counts caused by case differences between work table names. These duplicate records had the same work object ID but were coming from tables whose names were similar but with varying capitalization (Example_Table, example_Table, example_table). To avoid this issue, the ClassUsageDetail.equals() implementation has been updated to be case insensitive. There is also a newer tool available in the system to retrieve this data.
SR-A5645 · Issue 213208
Resolved FirstLogCreationTime error
Resolved in Pega Version 7.2
When the file PegaRULES-FirstLogCreationTime.log existed in the log directory, the following exception was generated: Exception caught while initializing context ... PegaRULES-FirstLogCreationTime.log exists, server cannot start". The file FirstLogCreationTime.log is a temporary file that gets created and used to hold the creation time stamp of the first log of the day (and help in avoiding the deletion of log files created in the previous day). If it becomes corrupted and is not readable, this error occurs. To correct this, code changes were made to make MaxBackupIndex applicable to all log files instead of only to log files of the day.
SR-A8072 · Issue 221510
Node name handling smoothed for passivation restore
Resolved in Pega Version 7.2
During database migration, the error 'PRMissingContextError: Cannot restore passivated page.' could occur due to handling issues with PR_SYS_STATUSNODES related to upper and lower case IDs. This has been resolved.
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.