SR-B50727 · Issue 310068
Repaired checking for forward links on cached references
Resolved in Pega Version 7.3.1
After upgrade, a Null Pointer Exception was thrown when updating a case due to missing handling for forward links on cached references. To correct this, a check has been added when trying to regenerate missing back links to verify whether the forward link is valid or not; if it is valid, only then will the system try to regenerate the back link. Otherwise it will pass back the old link itself.
SR-B51848 · Issue 308211
PrepareRDFilters repaired to preserve BIX extract rule filter conditions
Resolved in Pega Version 7.3.1
After upgrade, BIX extract rule filter conditions were missing. This was an issue with the activity pzPrepareRDFilters, which has been corrected.
SR-B54923 · Issue 312483
TrimLog regression for BIX extract purge fixed
Resolved in Pega Version 7.3.1
After upgrade, it was noted that execution history BIX extracts were unexpectedly only kept for 30 days. SystemCleaner calls TrimLog for specific sub-classes of Log- (i.e., Log-UndefinedMessage, Log-Operator-Session, etc.) and a daysAgo parameter to specify the number of retention days to keep. Previously, TrimLog would select up to 200 of whatever Log- subclass that were older than the retention days and delete them. As an unintended consequence of performance improvements, a modification to TrimLog to call purgeTableContainingClass meant that while this activity does use daysAgo to delete only rows older than this many days, this method did not take subclass into account. This resulted in the API purgeTableContainingClass() truncating the entire table without adding pxObjClass filter. This regression in behavior has been resolved by modifying the TrimLog activity to do an executeRDB query instead of calling purgeTableContainingClass().
SR-B46023 · Issue 307192
Page copy/merge clipboard call adjusted to resolve exception
Resolved in Pega Version 7.3.1
An UnmodifiablePropertyException appeared while doing Page copy from a source page with properties to a target page which contained an Autopopulate property. This was caused by an inconsistency in the Clipboard wrapper call that was trying to copy pxObjClass on a Page property when it was already populated inside the target page's Page property, and has been resolved.
SR-B46023 · Issue 311181
Page copy/merge clipboard call adjusted to resolve exception
Resolved in Pega Version 7.3.1
An UnmodifiablePropertyException appeared while doing Page copy from a source page with properties to a target page which contained an Autopopulate property. This was caused by an inconsistency in the Clipboard wrapper call that was trying to copy pxObjClass on a Page property when it was already populated inside the target page's Page property, and has been resolved.
SR-B46023 · Issue 312522
Page copy/merge clipboard call adjusted to resolve exception
Resolved in Pega Version 7.3.1
An UnmodifiablePropertyException appeared while doing Page copy from a source page with properties to a target page which contained an Autopopulate property. This was caused by an inconsistency in the Clipboard wrapper call that was trying to copy pxObjClass on a Page property when it was already populated inside the target page's Page property, and has been resolved.
SR-B51792 · Issue 308109
System Pulse enhanced to support Data-Admin-Requestor instances
Resolved in Pega Version 7.3.1
Changes in the Data-Admin-Requestor instances were not consistently getting propagated to other nodes in a cluster due to System Pulse not being supported for the Data-Admin-Requestor instances. An enhancement has been added to support this use.
SR-B77464 · Issue 327643
Clean up corrected for MultiChannel indexes
Resolved in Pega Version 7.3.1
Due to a capitalization change from 'Pega-Multichannel' to 'Pega-MultiChannel', indexes were not being cleaned up properly. This has been corrected.
SR-B77464 · Issue 328021
Clean up corrected for MultiChannel indexes
Resolved in Pega Version 7.3.1
Due to a capitalization change from 'Pega-Multichannel' to 'Pega-MultiChannel', indexes were not being cleaned up properly. This has been corrected.
SR-B49994 · Issue 312887
Pulse agent updated to handle Linux mixed case names
Resolved in Pega Version 7.3.1
Files were not getting deleted by the pulse agent in Linux-based multi-node environments if the Image Content had a path and name defined with a mix of upper case/lower case and the image was updated on a different node. This occurred because Linux-based environment file handles are case sensitive and the pulse message was not sanitized to be in lower case. To resolve this, the system will honor the lowerCase matching for filePath processing on pulse messages for Data-Content-Image files.