SR-B51825 · Issue 310042
Added handling for WO lock when OAuth2 token expires
Resolved in Pega Version 7.3.1
The expiration of the OAuth2 token committed the WOs in context and caused all WOs to lose their locks and eventually end up in the SLA broken queue. To fix this, code has been added to perform the commit on a new database thread so the commit operation will be independent from the actual thread context.
SR-B49520 · Issue 310724
Schema extraction over multiple DBs uses log table instead of class
Resolved in Pega Version 7.3.1
When running an extract, an Null Pointer Exception error was generated if the data being extracted was on a different schema / database than the Pega data schema. This has been resolved by reworking the sequence number generator to use a pr_log table connection of instead of using the class on which the extract was defined.
SR-B56540 · Issue 311961
Schema extraction over multiple DBs uses log table instead of class
Resolved in Pega Version 7.3.1
When running an extract, an Null Pointer Exception error was generated if the data being extracted was on a different schema / database than the Pega data schema. This has been resolved by reworking the sequence number generator to use a pr_log table connection of instead of using the class on which the extract was defined.
SR-B64125 · Issue 313855
Fixed SLA calculations with custom classes in Oracle
Resolved in Pega Version 7.3.1
For work classes, columns for pySLAGoal and pySLADeadLine are of type TIMESTAMP in Oracle DB. The Pega getContentItemsPastSLA activity uses the columns to find date differences with SYSDATE and then used a subtraction operation between columns of type TIMESTAMP and SYSDATE to calculate the SLA. However, an exception resulted when custom classes were used. To correct this, getContentItemsPastSLA has been updated to cast the columns of type TIMESTAMP to DATE type.
SR-B51989 · Issue 310393
TimeStamp column includes milliseconds in extract
Resolved in Pega Version 7.3.1
Extraction to database output format was not showing the millisecond part of the datetime column. This was a missed use case for BIX when the support of Datetime property mapping to timestamp column was introduced in Oracle, and has been fixed.
SR-B56367 · Issue 313698
Query updated for Oracle DDL generation
Resolved in Pega Version 7.3.1
When using a class mapped to an external database view, creating a RAP that included a Data-Admin-DB-Table instance in a lower environment for import into a higher environment resulted in invalid generated DDL for the view. This was due to a column alias list in the view definition not being included in the generated DDL, and has been fixed by using a different metadata query for Oracle to ensure the column list is returned if it was originally specified.
SR-B67316 · Issue 317299
Query updated for Oracle DDL generation
Resolved in Pega Version 7.3.1
When using a class mapped to an external database view, creating a RAP that included a Data-Admin-DB-Table instance in a lower environment for import into a higher environment resulted in invalid generated DDL for the view. This was due to a column alias list in the view definition not being included in the generated DDL, and has been fixed by using a different metadata query for Oracle to ensure the column list is returned if it was originally specified.
SR-B56437 · Issue 317515
Schema handling enhancement added for Alternate database option in list view
Resolved in Pega Version 7.3.1
A List view configured to use the Alternate Database setting generated an error when the report was run, due to the schema used by the Reporting Database (defined in the Sandbox-Work database table rule) having a different name than the default Pega database. The main Pega database schema is PEGA721, and the Reporting Database in this case was a schema called PEGA721REP in the same database, causing the table to not be found. As support for the reporting database being located on an alternate database with user specified schema is not available, an enhancement has been added to provide a prconfig that takes the schema for an alternate database and provides the support for ReportDefinition to use it.
SR-B49166 · Issue 309799
Removed unneeded timestamp on DADN rule connection test
Resolved in Pega Version 7.3.1
Test connections were failing for a Data-Admin-DB-Name rule when the connection type was "Use Configuration in Preferences". This failure was caused by "tmp" being appended to the DB name for the connection test, causing the DB name to be different in the prconfig file. Because a timestamp is not required, this has been fixed by not appending it to the DADN name.
SR-B66297 · Issue 314861
Instance insertion fixed for PostgreSQL partitioning
Resolved in Pega Version 7.3.1
Obj-Save was failing when trying to insert an instance in a partitioned PostgreSQL table with 'only if new' enabled. This record insertion failed because of a system check that is present when inserting an instance into the child table, and the issue has been resolved by reworking the code that was checking (assuming) if the insert was successful based on the returned inserted count.