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-A22107 · Issue 241929

Empty workbasket names localized

Resolved in Pega Version 7.2.1

In the dashboard of the Case Manager portal, the names of empty Workbaskets were not visible due to missing initialization in the localization. This has been fixed.

SR-A22147 · Issue 244096

Autogenerated prconfig sets v6 or v7 based on detection

Resolved in Pega Version 7.2.1

The autogenerated prpcUtils prconfig.xml file was setting the database/storageVersion to 6. In order to facilitate other setups, a flag has been provided in prpcUtils.properties as pega.storageVersion which will set the value in generated prconfig.xml to an empty string so the engine handles setting this to 6 or 7 in the same way that is possible when running the system.

SR-A22152 · Issue 247716

Report Def Filter using .pxObjClass returns all results

Resolved in Pega Version 7.2.1

Using .pxObjClass as a filter in Report Definitions resulted in different and/or incomplete Class arrays being built depending on how the Value field was populated. This was traced to an incorrect "if" check in objClassOptimizer causing class names to be missed, and has been fixed.

SR-A22198 · Issue 244738

Empty access groups handling added for organizational instance

Resolved in Pega Version 7.2.1

If an unauthenticated access group was configured in the organizational instance, errors occurred because the organization instance access groups are only considered for session authorization once the user is authenticated. This will now be handled through a validate activity change in the Data-admin-organization to honor the emptiness of access groups

SR-A22200 · Issue 242371

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-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.

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