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-A21705 · Issue 243428

Corrected unexpected scroll after smartinfo

Resolved in Pega Version 7.2.1

After a smartinfo box is shown for a particular column in a repeat grid, hovering on the column caused the mouse indicator to go to the bottom of the section, i.e. the screen goes down even when not scrolled down. This was caused by a focus issue, and has been corrected.

SR-A21810 · Issue 241087

PreClose updated to better handle inactive DC documents

Resolved in Pega Version 7.2.1

The PreClose extension point was not always being triggered for inactive DC documents utilizing the pzClearRecentItem and pzClearAllRecentItems APIs due to stale settings. The correct this, the handlegadgetLoad method has been updated to delete the docObj after the document has loaded.

SR-A21905 · Issue 242013

Post value handles editing existing RTE

Resolved in Pega Version 7.2.1

On Change event, the Post Value action was not working when editing RTE that had some content already present in it. This was a harness logic issue, and has been corrected.

SR-A21908 · Issue 245505

Eliminated new case creation on browser refresh

Resolved in Pega Version 7.2.1

When using the tabbedscreenflow7 harness, refreshing the screen caused a new Case to be created. This was seen in a no-frame portal with the top navigation for every action set to createNewWork, and the same new work URL was hit during the refresh. This has bene fixed by modifying replaceHistory in dynamiccontainer_lite.js to add a condition to skip returning when strHarnessMode is not action.

SR-A21997 · Issue 246052

Double quotes encryption handling now configurable

Resolved in Pega Version 7.2.1

When a property type of TextEncrypted was used, the apostrophe in a string was being changed to "'" due to XSS security filters. A parameter to ShowTextEncryptedPropertyValue control to support escaping double quotes has been added and is configurable based on need.

SR-A22016 · Issue 242244

Removed screen flicker when editing WorkObject

Resolved in Pega Version 7.2.1

Whenever a DynamicContainer action was invoked from the master details of an RDL row, a new harness was opened and dismissed, causing the RDL to momentarily appear on the screen. This has been fixed.

SR-A22074 · Issue 245363

Auto-logout updated to close browser window

Resolved in Pega Version 7.2.1

After upgrade, the pxSessionTimer was giving a timeout warning, but users were not automatically logged out as expected and the countdown timer showed a negative value. This was traced to the use of an old implementation of the pxSessionTimer rule which previously would trigger a browser window close when the time expired. This close function is not implemented in v7.2, causing the unexpected behavior. This has been fixed by updating the LogoffTimer HTML Rule to call the closeModal API by passing the correct dialogArguments.

SR-A22240 · Issue 245501

Progressive load grid display corrected for expand pane

Resolved in Pega Version 7.2.1

In an expand pane grid with progressive load, expanding the row details and switching tabs in the row details led to skewed UI on the first display (the second tab inside the row details contains larger amount of markup), but corrected itself on the second expansion. The expand pane in this configuration contained a tab group in which the height of the contents in the second tab was greater that the height of the contents in the first tab, and the resize function has been updated to correctly register and display this difference.

SR-A22287 · Issue 242965

Pega0031 debug tool stack trace updated

Resolved in Pega Version 7.2.1

When an activity was run which performed a show-html/show-stream twice, the first PEGA0031 alert was raised with no stack trace. The second instance of show-html/show-stream would log the PEGA0031 alert along with the stack trace of this interaction, and the first would not be seen. This was caused by the improper clearance of the pxHTMLStream property on the thread page at the end of the HTTP interaction and has been fixed.

SR-A22343 · Issue 242534

Error message display corrected for address map display

Resolved in Pega Version 7.2.1

Errors generated on the rendering of an address map control were immediately disappearing. This has been fixed.

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