SR-A3331 · Issue 208297
Enhanced added for non-logging config settings
Resolved in Pega Version 7.2
Both the upgrade process and Pega7 run-time make use of non-logged operations for major performance improvements. However, High Availability Disaster Recovery (HADR) database environments use database logs to replicate data from the primary database to the standby database. This caused a conflict that resulted in the unexpected termination of upgrade scripts. An enhancement has been added to make the logging function configurable (the default is No Logging = true), and tuning was done to make logged SQL generation faster to improve system performance when logging is enabled.
SR-A6523 · Issue 214991
Handling added for storing email addresses with special characters
Resolved in Pega Version 7.2
When attempting to store an encoded email address with special characters to the database, an exception was thrown and the process failed. This was found to be a database/data management issue related to executeRDB expression parsing the SQL query first, using "\" as an escape character. The subsequent JDBC driver execution also used ""\"" as an escape character
SR-A4488 · Issue 214464
Improved system performance for SQL using ReserveQueueItem
Resolved in Pega Version 7.2
The SQL generated using the stored procedure sppr_sys_reservequeueitem_b has been tuned to improve system performance for all database implementations; DB2, MS SQL Server, and Oracle.
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-A1999 · Issue 214345
"Edit in Excel" not supported in Microsoft Internet Explorer 11+
Resolved in Pega Version 7.2
Please note that due to code differences and rendering issues, the "Edit in Excel" option in Listview is not supported in Internet Explorer versions Microsoft Internet Explorer 11 and higher. Attempts to use Microsoft Internet Explorer 11+ for this will result in the messages "Error loading Transfer XML data" and "Error launching PegaRULES import manager". As an alternative, the Data tables landing page offers conversion of existing data tables to the new format.
SR-A1999 · Issue 214460
"Edit in Excel" not supported in Microsoft Internet Explorer 11+
Resolved in Pega Version 7.2
Please note that due to code differences and rendering issues, the "Edit in Excel" option in Listview is not supported in Internet Explorer versions Microsoft Internet Explorer 11 and higher. Attempts to use Microsoft Internet Explorer 11+ for this will result in the messages "Error loading Transfer XML data" and "Error launching PegaRULES import manager". As an alternative, the Data tables landing page offers conversion of existing data tables to the new format.