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-B11988 · Issue 284340

Fixed pagination exception for grid with pagegroup property

Resolved in Pega Version 7.3

An invalid reference exception was generated while navigating to the second page of a grid sourced with a pagegroup property. This was an error with the preActivityParams being encoded twice, causing characters to be corrupted. The string query has been updated to resolve this problem.

SR-B12026 · Issue 283561

Overridden data flow with RD partitioned key fixed

Resolved in Pega Version 7.3

A validation error was thrown and data flow activation failed for an overridden data flow with a RD partitioned key. This was traced to the circumstanced pzValidateRuleExistance (triggered when the dataflow shape was overridden) trying to open the property rule with pyPurpose set to rule name whereas the actual property should have been pyPropertyName. This has been fixed.

SR-B12207 · Issue 285722

Corrected Org text field handling for templated mobile sections

Resolved in Pega Version 7.3

Given a section pyWorkSummary_Mobile with a text input field called Organization, the organization name was shown correctly in the Declare_crmOrg page but on the UI it was displaying 'Org Not Found'. This was caused by recent section template changes that caused the object to be rendered on the wrong thread, and has been fixed.

SR-B12215 · Issue 281902

Cancel button fixed for pzTabbedScreenFlow7 harness

Resolved in Pega Version 7.3

The Cancel button was visible on the modal template of the Data import Wizard but was missing on the pzTabbedScreenFlow7 harness. This has been fixed.

SR-B12256 · Issue 281696

Editability check added to asterisk symbol (mandatory field expression) display

Resolved in Pega Version 7.3

Sections using conditional read-only and editable modes displayed the mandatory expression (asterisk symbol) in both modes. To correct this unexpected behavior, the GenerateLabelCellContent RUF has been updated to check whether the control is editable and only generate the asterisk if the result is true.

SR-B12345 · Issue 281568

Custom Validator support restored to Workformstandard

Resolved in Pega Version 7.3

Recent refactoring changed the behavior of Workformstandard. In order to support custom edit validate rules defined as part of the application to be executed on client-side, the custom validators HTML fragment has been restored to Workformstandard with correct pre-checks.

SR-B12369 · Issue 282877

Select button accessibility update

Resolved in Pega Version 7.3

Further refinements have been made to accessibility enhancements which will maintain focus on a select button after posting/submitting if a hidden input is present.

SR-B12374 · Issue 282127

Resolved StaleThreadError in LogHelper

Resolved in Pega Version 7.3

Repetitive stale thread errors were appearing in LogHelper. A check for thread destruction has been added to resolve this.

SR-B12374 · Issue 287614

Resolved StaleThreadError in LogHelper

Resolved in Pega Version 7.3

Repetitive stale thread errors were appearing in LogHelper. A check for thread destruction has been added to resolve this.

SR-B12451 · Issue 283057

Added case type propagation for layered applications built with NA wizard

Resolved in Pega Version 7.3

After creating an application on top of another using the New Application wizard and selecting the case types which need to be included the new application, not all of the cases and classes that should be present were shown. This was an issue with the correct pagelist not being checked while populating case types in the layered application, and code has been added to ensure all the case types of an existing application will come to a newly created application if the new application is built on top of an already existing application.

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