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-B238 · Issue 271610

Fork shape works with both when and percentage connectors

Resolved in Pega Version 7.2.2

An error was generated when trying to save a flow rule that contained both percentage connectors and When rules fork shapes. This was due to the 'ValidateModelProcess' activity getting all connectors in the flow and checking if there is at least one connector with Percentage, then iterating each decision shape by iterating the connectors and checking for percentage error scenarios. To fix this issue, the system will get the connectors from the decision shape in context and check if at least there is one percentage connector, then check for validation after that.

SR-B599 · Issue 270485

Flow Dependency queries performance improvements

Resolved in Pega Version 7.2.2

Case dependency queries executed by PEGA have been tuned to improve system performance when mid flow dependencies are getting fulfilled.

SR-A100811 · Issue 271627

Breadcrumbs display consistently

Resolved in Pega Version 7.2.2

Case stage breadcrumbs intermittently did not display when a work item was opened. This has been corrected by updating pxDisplayStages(Pega-EndUserUI rule set) to change from grid source to data page source and pass the the pzInsKey parameter.

SR-A93826 · Issue 264612

Corrected Field level audit issue

Resolved in Pega Version 7.2.2

Field level auditing was creating two extra "TrackSecurityChange_Change" entries when a new item was added to a Page List at the same time an existing item was removed. It was also updating audit incorrectly the item value was changed for one row at the same time another row was added. This has been fixed by modifying the Memo audit functions to update the values correctly on save when an entry or row is added/edited and other is removed.

SR-A102249 · Issue 270854

Lock warning correctly cleared after WO transfer

Resolved in Pega Version 7.2.2

If a work object opened by another user was transferred into a new workbasket, the expected lock warning showed up but refreshing the work object list caused a harness error. This was traced to incorrect clearing of the error message from the primary parameter page, and has been fixed.

SR-A98885 · Issue 265576

UpdateCalculationLabel modified to get embedded property label

Resolved in Pega Version 7.2.2

In Case Default rule -> open calculation tab, the calculated property field has a maximum value of 64 characters. In order to allow the setting of an embedded property as a target value (which would exceed the 64 character limit), pyUpdateCalculationLabel has been modified to get the label of the embedded property.

SR-A99757 · Issue 265774

UpdateCalculationLabel modified to get embedded property label

Resolved in Pega Version 7.2.2

In Case Default rule -> open calculation tab, the calculated property field has a maximum value of 64 characters. In order to allow the setting of an embedded property as a target value (which would exceed the 64 character limit), pyUpdateCalculationLabel has been modified to get the label of the embedded property.

SR-A96555 · Issue 264154

RequiredSkills Declare Index fixed for Federated Case Manager

Resolved in Pega Version 7.2.2

In Federated Case Manager, skill-based routing of assignments to a workbasket generated a pyCommitError indicating "Cannot save instance of class Index-AssignmentSkills-Federated". This was due to missing index table properties needed by the Index-AssignmentSkills-Federated.RequiredSkills declare index, and has been fixed.

SR-A99521 · Issue 266569

Localization added to DisplayStages

Resolved in Pega Version 7.2.2

Localization has been added to 'Show all steps' and 'Hide Steps' in pxDisplayStages.

SR-A94737 · Issue 265585

Correspondence updated with party role change from dropdown

Resolved in Pega Version 7.2.2

On changing the party role from the drop down, the value was not updated in the correspondence. This was due to CreateSelectedCorr activity only being called when the correspondence was changed in the drop down, and has been resolved by regenerating the correspondence view any time an edit is selected and submitted.

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