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-A22200 · Issue 241230

Bulk actions filters refresh corrected

Resolved in Pega Version 7.2.1

The values entered into the right side column of the bulk processing filters were not getting submitted to the clipboard when default filter conditions were changed. The refresh action has been updated to correct this.

SR-A22234 · Issue 243871

Resolved CME error for case withdrawal

Resolved in Pega Version 7.2.1

When withdrawing a case, pxForceCaseClose was throwing Concurrent Modification Exception. This has been fixed.

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-A22263 · Issue 242102

Improved error reporting for PE install

Resolved in Pega Version 7.2.1

In order to facilitate debugging, attempting to install Pega Express from a directory with a space in the name will generate an error on the screen reiterating the installation instructions requiring that the directory name not contain a space.

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-A22298 · Issue 243924

Refresh corrected for tabbed screen flow perform harness

Resolved in Pega Version 7.2.1

When using the "TabbedScreenFlow7" perform harness, an incorrect refresh call caused the Actions menu on the work object to disappear from the screen. This has been resolved.

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.

SR-A22354 · Issue 245861

prpcUtils honors 5.4 compatibility checkbox

Resolved in Pega Version 7.2.1

Pega deployment using prpcUtils was failing due to the 5.4 compatibility checkbox being ignored: the product rule being exported still included schema changes in the exported RAP file. This has been corrected.

SR-A22365 · Issue 243530

Multi-parameter function value handling added to Report Definition chart

Resolved in Pega Version 7.2.1

When a chart control was configured using the property panel in design view, the chart preview did not update appropriately if it used a column defined by a function that with two or more parameters. To handle this, part of com.pega.pegarules.priv.desktop.reporting.chart.AutoChartConfigTranslator.translateDataItem(DataItem, ClipboardPage) has been refactored such that it only splits pyReportColumnKey on the first ',' (comma).

SR-A22384 · Issue 243895

Error Header and Button Footer scrolling fixed

Resolved in Pega Version 7.2.1

Error Header and Button Footer scrolling was corrupted due to an absolute positioning error in the harness. This 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