Skip to main content

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 Case ID number (SR or INC) in order to find the associated Support Request.

Please update your bookmarks. This site will be discontinued in Dec 2024.

Pega Platform Resolved Issues for 8.1 and newer are now available on the Support Center.

SR-A77119 · Issue 255525

Fixed attaching files to pre-existing inflight cases after upgrade

Resolved in Pega Version 7.2.2

After upgrade, loading pre-existing inflight cases and attaching a file generated the error "Trying to save an invalid page: Trying to save an invalid page: page is not valid ". This was caused by a missing check for LinkPage.pyMemo if LinkPage.pyCategory is not set, and has been fixed by setting pyMemo from LinkPage.pyMemo.

SR-A88588 · Issue 256536

TopCasePage reference retained in CreateTopCase

Resolved in Pega Version 7.2.2

After upgrade, the "pyTopCasePage" page reference was missing in the Clipboard after a new case was created using the "pxCreateTopCase" activity in utility shape in a flow. This was traced to a step in the function that removed the pyTopCase page reference unnecessarily, and the pxCreateTopCase activity has been modified to preserve this.

SR-A90516 · Issue 258175

Resolved App Express error for new operator groups

Resolved in Pega Version 7.2.2

An error was appearing while creating a operator access group via App Express. This was an error in the commit while saving process if the entry in pyObjectsToCreate was FrameWorkAssets, and has been fixed.

SR-A86964 · Issue 256956

Corrected date value created by ShowConflicts

Resolved in Pega Version 7.2.2

An invalid format date value was being created by the "pzShowConflicts" activity, causing problems when trying to submit an assignment updated by another agent. This has been fixed by setting the value with the PRDateFormat.DEFAULT_DATETIME_MEDIUM format instead of DD-MM-YYYY.

SR-A82879 · Issue 254116

FilterHistory WRITE_NONE correctly stops all audits

Resolved in Pega Version 7.2.2

Changing the system settings rule "FilterHistory" from WRITE_SOME to WRITE_NONE was still running an audit when the stage changed instead of completely stopping all auditing. This was due to an RUF call to ADDHISTORY without checking the DSS, and a check has been added to fix this.

SR-A87755 · Issue 256118

Fixed Dynamic Class Reference use for the workbasket name in Wait shape

Resolved in Pega Version 7.2.2

Error "Unable to open assigned's Data-Admin-WorkBasket record" was thrown when using a Dynamic Class Reference to refer the workbasket name in Wait shape. This was traced to the Workbasket in the Wait shape being quoted, leading to the property reference not being honored The quoting of the workbasket has been removed in the pzAfterWait.

SR-A25429 · Issue 252126

Count corrected for @getMessagesCount

Resolved in Pega Version 7.2.2

Flawed logic in the out-of-the-box activity restoreAssignment exposed a flaw in @getMessagesCount where the API used to copy error messages returned a string which is concatenation of all messages with \n delimiter, resulting in the count always being one. This has been corrected.

SR-A92563 · Issue 261301

removeDuplicatesFromList modified to remove duplicate rules based on resolution

Resolved in Pega Version 7.2.2

In DB2 zOS, the flow actions are retrieved in random order. Because of this, FixCorr was sometimes picked from Pega-ProcessEngine and sometimes picked from other rulesets such as Pega-IntegrationEngine. Since removeDuplicateFromList returns the flowaction which was last in the result set, inconsistent results were seen. There was a workaround to check the 'Disqualify this action from bulk processing' checkbox in Work-FixCorr in Pega-IntegrationEngine and Pega-Procom ruleset, but this has been resolved with an enhancement that modified removeDuplicatesFromList to remove duplicate rules based on rule resolution.

SR-A23564 · Issue 251378

pzGetAllCoveredAttachments activity tuned for better system performance

Resolved in Pega Version 7.2.2

In order to improve system performance, the pzGetAllCoveredAttachments activity has been modified to limit the scope of its SQL query to only open the cover and fetch the covered items instead of calling the generalized pzGetChildKeys function.

SR-A94678 · Issue 262223

pzGetAllCoveredAttachments activity tuned for better system performance

Resolved in Pega Version 7.2.2

In order to improve system performance, the pzGetAllCoveredAttachments activity has been modified to limit the scope of its SQL query to only open the cover and fetch the covered items instead of calling the generalized pzGetChildKeys function.

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

Pega.com is not optimized for Internet Explorer. For the optimal experience, please use:

Close Deprecation Notice
Contact us