INC-216380 · Issue 722700
Update impact for Pega Call
Resolved in Pega Version 8.8
Log4j-1.2.14.jar and Log4j-1.2.17.jar have been removed to address the security concerns with these versions, and logger jars have been upgraded to 12.7.2 version (from 12.7.1 version) to make Pega Call compatible. This change will impact Pega Call customer environments due to Avaya or Genesys, which are part of Pega Call, having an internal dependency on Log4j1.x version jars. As a result, the SDK logging for Avaya or Genesys will not be available in the 8.8 release unless the Log4j-1.x jar files are reimported locally. Please refer to https://docs.pega.com/pega-call-release-notes/87/changes-update-impact
INC-216381 · Issue 716614
BigDecimal handling updated for @ sum function
Resolved in Pega Version 8.8
The @ sum function was not behaving correctly. This was traced to the java code in the 'sum--(ClipboardPropertyCollection)' function which was not properly converting the double to Bigdecimal for some of the inputs like 500, 500, 600.11. This has been resolved by modifying the function to convert input properties to BigDecimal, add BigDecimal values, and return the result.
INC-216730 · Issue 716206
Updated handling for last_access to improve backwards compatibility
Resolved in Pega Version 8.8
After update from Pega 8.3 to Pega 8.6, many errors were seen in the logs regarding the call of the Pega API /api/v1/nodes/all/requestors. In 8.3, the API was responding with the field last_access populated properly, but this field was blank in the new version. This was an unintended consequence of work done to resolve inconsistencies with the date format in Admin Studio, and has been resolved.
INC-217029 · Issue 713143
Improved performance for Agile Studio web nodes
Resolved in Pega Version 8.8
Large data pages configured as queryable or searchable were unexpectedly getting added to the cache and not cleared, causing some performance issues. To resolve this, the caching logic has been modified to skip adding queryable and searchable data pages if they contain pyImplicitParameter.
INC-217159 · Issue 721071
German locale preserves semicolon as CSV separator
Resolved in Pega Version 8.8
When manually importing CSV files in the German locale which has special characters, special date format and the semicolon as a separator, the staging environment worked as usual and separated the imported records, but attempting to import the same CSV file to the staging clone did not split the records into the separated fields. This was traced to the pzGetLocaleListSeparator decision table returning a comma for the separator instead of semicolon for the de_DE locale, and has been corrected.
INC-217904 · Issue 730432
New prconfigs added to handle lob closed error
Resolved in Pega Version 8.8
BIX extraction was encountering the SQL error "Invalid operation: Lob is closed" while reading the BLOB, but the rest of the records were able to be extracted. This was traced to previous work done to resolve an issue where Oracle temporary space used to write the LOB was not freed up after writing records to Log-Service-File when using OJDBC8 or OJDBC10 versions. This change caused an issue for DB2 where the freed BLOB was still trying to be extracted. To address this, new prconfig settings have been introduced to control freeing BLOB memory. If the error is seen regarding the lob being closed, add and disable these settings (set value as false) in the pronfig.xml file. DATABASE_MANAGEMENT_FREELOB: settingName: database/management/freeLOB description: If this flag is set to false, it controls the free memory calls defaultValue: true DATABASE_MANAGEMENT_FREEPAGEDBMAPPERLOB: settingName: database/management/freePageDBMapperLOB description: If this flag is set to false, it controls the free memory calls. defaultValue: true Following this change, restart the server.
INC-218234 · Issue 734687
DSS added to skip 'Has Purge Happened Since Startup'
Resolved in Pega Version 8.8
The Purge Agent did not finish execution, exiting with the error "skipping purge because HasPurgeHappenedSinceStartup == false". This was traced to the local site policy of restarting their nodes every week, which was not aligned with the system default purge policy. To address this, a new DSS "skipHasPurgeHappenedSinceStartupCheck" has been added to the Pega-RulesEngine ruleset. When set to true, the check for 'Has Purge Happened Since Startup' will be skipped.
INC-218463 · Issue 726502
Common TransformerFactory method added for greater compatibility
Resolved in Pega Version 8.8
In Service-SOAP, mapping request headers and parameters to the clipboard (instead of mapping to a Parse XML rule) resulted in blank values on the primary page of the service activity when using the IBM WebSphere Liberty app server. In this case, instantiating the JAXP TransformerFactory object using the com.sun.org.apache.xalan.internal.xsltc.trax.TransformerFactoryImpl parameter resulted in a transformer that serialized the XML to an empty string instead of the correct XML. To resolve this, an update has been made to make a common TransformerFactory method to ensure IBM JDK in WAS deployments function as expected.
INC-218532 · Issue 742524
File listener error recovery resumes from failure point
Resolved in Pega Version 8.8
When file listeners were unable to parse a file due to exception, the automatic error recovery did not start parsing from the correct location. Investigation showed the segment was not tracked during file listener run, so during error recovery the file listener always started processing from the first segment instead of the segment from which it failed. This was a missed use case and has been resolved by tracking the active segment and utilizing it during the error recovery run of the file listener.
INC-218802 · Issue 736911
New prconfigs added to handle lob closed error
Resolved in Pega Version 8.8
BIX extraction was encountering the SQL error "Invalid operation: Lob is closed" while reading the BLOB, but the rest of the records were able to be extracted. This was traced to previous work done to resolve an issue where Oracle temporary space used to write the LOB was not freed up after writing records to Log-Service-File when using OJDBC8 or OJDBC10 versions. This change caused an issue for DB2 where the freed BLOB was still trying to be extracted. To address this, new prconfig settings have been introduced to control freeing BLOB memory. If the error is seen regarding the lob being closed, add and disable these settings (set value as false) in the pronfig.xml file. DATABASE_MANAGEMENT_FREELOB: settingName: database/management/freeLOB description: If this flag is set to false, it controls the free memory calls defaultValue: true DATABASE_MANAGEMENT_FREEPAGEDBMAPPERLOB: settingName: database/management/freePageDBMapperLOB description: If this flag is set to false, it controls the free memory calls. defaultValue: true Following this change, restart the server.