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 note: beginning with the Pega Platform 8.7.4 Patch, the Resolved Issues have moved to the Support Center.

INC-201981 · Issue 697634

Added check for StageHistory page

Resolved in Pega Version 8.6.3

After update, the pyDisplayStages section was not visible in pyCaseMainInner due to the 'when' condition pxHasStages not being satisfied. This was traced to a customization for the pyStartCase flow in one of the case types which resulted in a blank pxStageHistory page being set under pyWorkPage, and has been resolved by adding a 'when' condition to check whether pxStageHistory page exists so the step will only execute if the pxStageHistory page is present.

SR-A91680 · Issue 259008

Resolved Null Pointer Error for resubmit of a corrected case with optimistic locking

Resolved in Pega Version 7.2.2

Work order case creation was throwing a null pointer exception in logs if optimistic locking was enabled on the case type and the case was resubmitted after correcting a validation error. This has been fixed with the addition of a null check for a clipboard page in use.

INC-196961 · Issue 693474

Iteration method updated for SetRequiredSkillsCountColumn

Resolved in Pega Version 8.6.3

After update, database utilization spiked and did not drop. Investigation traced this to the use of Local.totalCount in pzSetRequiredSkillsCountColumn, which caused the iteration loop to run more times than necessary. This has been resolved by replacing Local.totalCount with Local.iterationsCount in the iteration.

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-A76390 · Issue 253683

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-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-D33966 · Issue 504607

Corrected accessibility error after resize

Resolved in Pega Version 8.2.4

From within a Case and on a screen displaying the Information and Audit tabs in a Layout group, it was possible to use a series of sequences that included resizing the browser and opening Audit to cause the information tab to no longer be accessible. This has been resolved by setting the transform value to 0 after completing the resize.

SR-D29832 · Issue 503225

Corrected image alignment for email case creation

Resolved in Pega Version 8.2.4

An issue with missing image styling when an email was sent to create a case was traced to the Owasp library stripping align attributes from the img tag. This has been fixed.

SR-A76776 · Issue 254774

Pega Pulse Link Description text box handled dynamically

Resolved in Pega Version 7.2.2

To correct an issue where the Pega Pulse Link Description text box was not visible due to screen size (i.e., the Pega Pulse fields were not getting wrapped on the screen, the container for the pzLinkDescription section has been changed to use dynamic layout so it correctly adjusts according to the width.

SR-A96203 · Issue 270094

CreateCase rollback corrected

Resolved in Pega Version 7.2.2

While creating a sub-case and getting an error on any end-step of flow, Pega starts the rollback of the process, but was saving pxCoveredInsKeys in the Clipboard page of Case. This was a missing use case in AddCoveredWork to call RemoveFromCover if an error was thrown while creating a child case along with copying page pages from cover to primary, and has been corrected.

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