SR-B66457 · Issue 315578
Date time values corrected for data loader uploads
Resolved in Pega Version 7.3.1
Using data loaders to upload a work object which contained date fields was resulting the the fields taking the wrong dates. To correct this, from the second record onwards the system will use the parseDateTimeWithISO method in order to consider both basic date time and XSD date time instead of only XSD date time
SR-B66457 · Issue 315580
Date time values corrected for data loader uploads
Resolved in Pega Version 7.3.1
Using data loaders to upload a work object which contained date fields was resulting the the fields taking the wrong dates. To correct this, from the second record onwards the system will use the parseDateTimeWithISO method in order to consider both basic date time and XSD date time instead of only XSD date time
SR-B49479 · Issue 305656
Values localized in Data Migration Wizard final review
Resolved in Pega Version 7.3.1
Values were not getting translated in Data Migration Wizard in the final review screen. This has been fixed.
SR-B69082 · Issue 317647
Support added to data import wizard for Enhanced Work ID prefix/suffix
Resolved in Pega Version 7.3.1
While creating work objects using the data import wizard, the pyID did not include a suffix that had been added to the work object ID. This was due to custom logic for generating workId being called in DataImportUtilsImpl rather than reusing the existing activity GenerateID in Work- class. In the custom logic, suffixId is not used and therefore was not passed. To improve flexibility, changes have been made in the import code to call the activity GenerateID for generating the WorkID using both the prefix and the suffix ID.
SR-B64134 · Issue 313542
Workaround added for Oracle 4000 character column value max
Resolved in Pega Version 7.3.1
Due to an Oracle limitation, RD on a clob column fails if the column value is of length greater than 4000. To work around this, support has been added to retrieve data from a clob column of length greater than 4000 characters using report definition based on DASS setting "reporting/retrieveFullClobContent" defined on "Pega-RULES".
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-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-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.
SR-B66297 · Issue 299892
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.
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.