SR-A4589 · Issue 214117
Obj-Browse reads external mapping with external schema
Resolved in Pega Version 7.2
An Obj-Browse function missing the definition for the property/column lists was not reading the column-property mapping from the Class definition when using external schema. To correct this, getListSelectClause has been modified to use the property name as alias when external mapping is defined and a passed field value is a column name for classes mapped to an external table.
SR-A6172 · Issue 214153
obj-delete and obj-open now working with external DB
Resolved in Pega Version 7.2
An activity was failing when trying to perform an obj-open or an obj-delete or Obj-Open-By-Handle or Obj-Refresh-And-Lock or Obj-save on an external DB2 database with column type as Date. This issue occurred when a class was mapped to a table in an external DB which was not the same as the Pega hosting DB. This was caused by incomplete handling of a null classname in the platform check, and has been resolved.
SR-A6172 · Issue 208100
obj-delete and obj-open now working with external DB
Resolved in Pega Version 7.2
An activity was failing when trying to perform an obj-open or an obj-delete or Obj-Open-By-Handle or Obj-Refresh-And-Lock or Obj-save on an external DB2 database with column type as Date. This issue occurred when a class was mapped to a table in an external DB which was not the same as the Pega hosting DB. This was caused by incomplete handling of a null classname in the platform check, and has been resolved.
SR-A1803 · Issue 206925
Support added for Virtual Private Databases (VPDs)
Resolved in Pega Version 7.2
An enhancement has been added to allow an application developer to pass a customizable set of property values to an Oracle or Enterprise DB when a connection is established to the DB to run SQL statements. The primary use case for this feature is the ability for Pega DBMS that support Virtual Private Databases (VPDs) to implement unbreakable object-level security for all data access from a Pega application by defining on class tables that reference this information.
SR-A5100 · Issue 212794
Support added for Virtual Private Databases (VPDs)
Resolved in Pega Version 7.2
An enhancement has been added to allow an application developer to pass a customizable set of property values to an Oracle or Enterprise DB when a connection is established to the DB to run SQL statements. The primary use case for this feature is the ability for Pega DBMS that support Virtual Private Databases (VPDs) to implement unbreakable object-level security for all data access from a Pega application by defining on class tables that reference this information.
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.