SR-A4883 · Issue 216593
Updating caching to ensure proper rule resolution
Resolved in Pega Version 7.2
For performance reasons, a Requestor level is used to hold data page definitions. However, two data pages with the same name but in different rulesets caused Rule Resolution to not pick the datapage from correct RS Version consistently. This has been corrected by appending a personal ruleset hash name with data page name before putting the definition in cache.
SR-A5183 · Issue 213803
Added check to ensure all invalidated shortcuts are processed correctly
Resolved in Pega Version 7.2
When running SQL server version 2012 with a particular JDBC driver, executing a DML statement without setting the pyMaxResultCount caused the number of records returned to be limited by the default record size, and the system was not picking up the latest versions of all of the rules after shortcuts were invalidated. To resolve this, the method invalidateShortcuts(RACacheAppCentricImpl) has been modified to set pyMaxRecords to zero when calling executeRDB so that all the impacted rows are processed.
SR-A5233 · Issue 212884
Added external DB support for DB2 v.8
Resolved in Pega Version 7.2
After upgrade, trying to connect to DB2 ver 8 as an external database generated the error "SQLCODE: -4700 SQLSTATE: 56038 Cannot connect to DB2". This was due to Method getSchemaName(SQLGeneratorDB2) firing a query which is valid only on a higher/supported version of DB2. To accommodate other versions of the database, the system will fallback to the V8 syntax if the higher-level query fails.
SR-133085 · Issue 210184
DATE support added for SQL
Resolved in Pega Version 7.2
Support has been added for using the Date column type with SQL servers in cases where the DB supports the DATE type.
SR-A7048 · Issue 215222
DATE support added for SQL
Resolved in Pega Version 7.2
Support has been added for using the Date column type with SQL servers in cases where the DB supports the DATE type.
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.