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-B15884 · Issue 288287

Page level error display honors KeepPageMessages value

Resolved in Pega Version 7.3

Page level error messages on the perform harness were flickering when a flow action was submitted. This was caused by the message only displaying for half a second, and has been corrected by correctly honoring the "pega.u.d.KeepPageMessages" value.

SR-B16230 · Issue 287871

Dollar sign character will be escaped if present in data page value

Resolved in Pega Version 7.3

If a section was configured to show the data with a data page as source, using the dollar sign in the value caused the amount to not be displayed correctly in the grid. This has been corrected by adding code to escape the $ character when it's present in the data.

SR-B16331 · Issue 303039

Check added to WorkUnlock to ensure cover page exists

Resolved in Pega Version 7.3

An intermittent error was logged related to workunlock. This was caused by Work-.Close calling workUnlock from the param.coverPage without performing a check first to ensure that the coverPage exists and has a class. To fix this, the WorkUnlock activity has been modified to verify that the coverPage has a class before unlocking the cover object.

SR-B16331 · Issue 294717

Cover page check added to Work-Close

Resolved in Pega Version 7.3

An intermittent stack trace was being generated in Work-Close; this has been resolved by adding a check to ensure that the coverPage exists and has a class.

SR-B16784 · Issue 287160

Attachments removed when work object withdrawn

Resolved in Pega Version 7.3

After adding an attachment and then withdrawing the case, the unneeded attachments were still being stored in the attachments section until a refresh was performed. This was traced to code in the UpdateAndDeleteAssignments activity that appended the target page rather than replacing. This has been modified to ensure attachments are eliminated when the status of a work object is moved to 'Withdraw'.

SR-B17100 · Issue 290607

Optimistic locking fixed for GetNextWork

Resolved in Pega Version 7.3

The optimistic locking feature was is not working as expected when GetNextWork was invoked. This was caused by missing parameter passing, and has been fixed.

SR-B17355 · Issue 289241

Accessibility improved for properties in accordion layout

Resolved in Pega Version 7.3

The screen reader was reading the property name for Properties configured on Accordion Layout titles instead of the content of the property. This has been fixed.

SR-B2191 · Issue 275647

Fixed Chrome position resetting with proposition change

Resolved in Pega Version 7.3

When duplicating a proposition in Chrome, any change in an attribute refreshed the screen and reset the scrollbar all the way to the top. This has been fixed.

SR-B2595 · Issue 274239

Enabled process cleanup for change stage shape

Resolved in Pega Version 7.3

When using the "Approve\Reject" step in case designer on a flow containing logic to jump back to a previous stage on rejection, the system created the new assignment needed for jumping back to the previous stage but did not clean up the existing assignment. This caused two parallel flows at the same time and the old assignment was loaded on the screen. This has been fixed by enabling the CleanUpProcesses parameter in the Change stage shape function of pzPostApprovalActions.

SR-B26249 · Issue 290765

Flickering in Tabbed Layout header corrected

Resolved in Pega Version 7.3

In a Tabbed Layout with four tabs using expandable Repeat grid sections, the first column table header had extra grey space generated intermittently. The pzpega_ui_Grid js file has been updated to correct this.

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