SR-A34 · Issue 204505
Pega Lookup JSP tag correctly retrieves Chinese characters
Resolved in Pega Version 7.1.9
When the pega:lookup JSP tag did a field value lookup on pyCaption to retrieve the field value consistent with the locale, any Chinese characters embedded in the HTML pages used to generate the PDF rendered correctly but '?????' appeared in the PDF content instead of the Chinese characters configured in the Field-Value pair. This was caused by an issue in the code which caused the system to incorrectly identify NVARCHAR columns as being VARCHAR columns. This has been fixed., and the encoding for TestDatabaseNew has also been set to be UTF-8 to ensure the Non-ASCII characters in the tests are handled properly in all workspaces.
SR-A3428 · Issue 212424
Modified ClassName pass method for external DBs
Resolved in Pega Version 7.1.9
When DB2 is used as external DB (external table has a date column) and PRPC is hosted on a DB other than DB2, performing an obj-save into an external DB2 database failed with an SQL error. This issue occurred when a class was mapped to a table in an external DB which was not same as Pega hosting DB. In class PageDatabaseMapperImpl.java , function getDatabaseTypeFromEngine is used to check the database type when column type is Date, but the function was using a hardcoded value of class to determine the database type. This has been changed to pass className as parameter and use it to determine database type.
SR-A3744 · Issue 209253
Resolved Vtable NPE during engine start
Resolved in Pega Version 7.1.9
If a Rule-Access-When was defined on the class Data-Admin-System-Settings, search was initialized before the VTable is initialized. While initializing search, a DASS was set and a save operation was performed on the DASS which then tried to perform a security check and attempted to retrieve the Rule-Access-When from the unpopulated VTable cache. This led to an NPE. To resolve this, changes have been made so that search will be initialized after Vtable is populated.
SR-A940 · Issue 205402
Locking issue resolved for importing PUI jars
Resolved in Pega Version 7.1.9
Errors were being generated when importing PUI framework jars. This was an issue where the savepoints created in Saver.executeUpdate needed to be explicitly released on PostgreSQL to avoid locks from accumulating for each of the nested transactions, and the problem has been resolved.
SR-A990 · Issue 205075
Post-upgrade deferred list mapping reference inserted for new classes
Resolved in Pega Version 7.1.9
After migrating, the processing of the deferredlist while performing an updatestatus operation generated an exception from pzMapCases. This was caused by a class mapping issue where the new classes (InsertRuleSummary, UpdateRuleSummary, DeleteRuleSummary) added in DeferredOperationsImpl did not have interfaces in DeferredOperation. This has been corrected.
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.