Skip to main content
circle-square
Outline Circle
square-square
Little Circle
square-square
Little Circle

Resolved Issues

View the resolved issues for a specific Platform release.

Go to download resolved issues by patch release.

Browse release notes for a selected Pega Version.

NOTE: Enter just the SR ID number in order to find the associated Support Request.

SR-B45232 · Issue 306137

Serialized passivation exception fixed

Resolved in Pega Version 7.3.1

A passivation exception was being logged due to a temporary page not being properly cleared after use with serialized properties. The ActivityStatusExceptionHandler activity has been changed to remove the temp page at the end.

SR-B64471 · Issue 315890

PegaCALL Null Pointer Exception fixed

Resolved in Pega Version 7.3.1

After a successful PegaCALL login was initiated and events were populated to the desktop, setting the phone status to Ready then caused some sites to experience sporadic errors that resulted in CTI login problems and events not reaching the desktop. When the issue occurred, it affected an entire instance at a time but cleared on its own after several hours. This was due to missing null handling in the code used for event delivery, and has been fixed.

SR-B65837 · Issue 317187

Handling added for blanks when copying parameter pages

Resolved in Pega Version 7.3.1

After Configuring a Call-Asynch-Activity method step on an activity and refreshing the ruleform, the name of the activity being called in the method was no longer shown. To correct this, a 'when' condition has been added to the pzAddAdditionalMethodParameter activity to handle blank pages when copying parameter pages to pyStepsParamUI pages.

SR-B67171 · Issue 317155

Handling added for blanks when copying parameter pages

Resolved in Pega Version 7.3.1

After Configuring a Call-Asynch-Activity method step on an activity and refreshing the ruleform, the name of the activity being called in the method was no longer shown. To correct this, a 'when' condition has been added to the pzAddAdditionalMethodParameter activity to handle blank pages when copying parameter pages to pyStepsParamUI pages.

SR-B41213 · Issue 310710

Ruleset sorting/comparison updated for DB2/zOS EBCIDIC

Resolved in Pega Version 7.3.1

After upgrade to a DB2/zOS split schema, accessing the UI Gallery landing page (DS -> User Interface -> UI Gallery) did not show any results. It was possible to search for rules and open them without issue, and altering the query to use a wildcard for pzRuleSetListHash found the rules as expected. The problem was traced to EBCIDIC character set ordering being different than ASCII & UTF-x based char ordering. UTF-based character encodings hold that A is greater than 9 when being used for comparison, but in an EBCIDIC sort, A's value is less than 0. Due to IBM DB2 on zOS using EBCIDIC ordering for character string comparisons (e.g. greater than, less than), the pzRuleSetVersionMinorPatch column that contains the String for the Minor and Patch versions was not ordering the needed rulesets as expected. To resolve this, the code has been updated to rarely use character string comparisons (greater than) in DB queries for greater compatibility.

SR-B43868 · Issue 310711

Ruleset sorting/comparison updated for DB2/zOS EBCIDIC

Resolved in Pega Version 7.3.1

After upgrade to a DB2/zOS split schema, accessing the UI Gallery landing page (DS -> User Interface -> UI Gallery) did not show any results. It was possible to search for rules and open them without issue, and altering the query to use a wildcard for pzRuleSetListHash found the rules as expected. The problem was traced to EBCIDIC character set ordering being different than ASCII & UTF-x based char ordering. UTF-based character encodings hold that A is greater than 9 when being used for comparison, but in an EBCIDIC sort, A's value is less than 0. Due to IBM DB2 on zOS using EBCIDIC ordering for character string comparisons (e.g. greater than, less than), the pzRuleSetVersionMinorPatch column that contains the String for the Minor and Patch versions was not ordering the needed rulesets as expected. To resolve this, the code has been updated to rarely use character string comparisons (greater than) in DB queries for greater compatibility.

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.

Ready to crush complexity?

Experience the benefits of Pega Community when you log in.

We'd prefer it if you saw us at our best.

Pega Community has detected you are using a browser which may prevent you from experiencing the site as intended. To improve your experience, please update your browser.

Close Deprecation Notice
Contact us