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 note: beginning with the Pega Platform 8.7.4 Patch, the Resolved Issues have moved to the Support Center.

SR-B90586 · Issue 340645

Baseref set correctly on Microsoft Internet Explorer 11 action launch

Resolved in Pega Version 7.4

An 'Activity status error' appeared when trying to launch a local action upon click of a menu item on Microsoft Internet Explorer 11. Investigation showed this was due to the 'Basereference' not being set in Microsoft Internet Explorer because it was being calculated on a stale element, and this has been fixed by calculating the proper live element when the baseref is null.

SR-B93716 · Issue 340451

Grid summary added for accessibility

Resolved in Pega Version 7.4

pzRBShortcutsGrid7 now includes a Grid Summary to enhance accessibility.

SR-B97228 · Issue 343365

Added support for imported flow stage ID in DS dropdown

Resolved in Pega Version 7.4

In Designer Studio, any flow rule that contained a Change Stage flow shape imported from a previous version that was configured to go to a specific stage name displayed an incorrect value in the dropdown list. This was due to the difference in the application versions: Previously, Stage ID was used in Flow metadata while recent versions support both ID and Name. The UI depends on the Name to show the drop down, meaning imported flows were not passing the needed information. To make the system more robust, a new 'when' rule has been added to pzIsIDUsedInChangeStage to decide whether to show the Name or ID.

SR-C3153 · Issue 345296

Manage review team error fixed

Resolved in Pega Version 7.4

Any action in "Manage review team" function inside branch review was showing an error. This has bene fixed by passing a missing parameter as AssociationClass:"Link-Association".

SR-C3921 · Issue 349058

Handling added for idled WO with empty values

Resolved in Pega Version 7.4

After opening a work object and then idling it for at least 15 minutes, trying to perform a Word merge resulted in HTML code being inserted into previously empty values. This has been corrected.

SR-C6529 · Issue 350614

Edit Pipeline trigger on merge state resolved

Resolved in Pega Version 7.4

The property "pyStartBuildOnBranchMerge" (which corresponds to the UI setting called "Trigger build on merge" on the 'Add Application pipeline') was not changed as expected when using the Actions>Edit Pipeline to alter the state of "Trigger build on merge". This was true whether the option was being switched OFF or ON, with the setting remaining fixed at its original state. This was traced to pyStartBuildOnBranchMerge persisting after being deleted, and has been resolved by defaulting the value of pyStartBuildOnBranchMerge to false to allow the calculation of the pyStartBuildOnBranchMerge state to work correctly.

SR- · Issue 319981

Field labels localized in pyAccountSettings

Resolved in Pega Version 7.4

Localization has been added to the field labels in the pyAccountSettings section rule.

SR- · Issue 324033

Files updated to resolve memory leaks

Resolved in Pega Version 7.4

The following files have been updated to address memory leak issues when processing a large number of cases: PZPEGA_UI_DYNAMICCONTAINER_LITE PZPEGA_PROCESS_ENGINE PEGA_TOOLS_EVALDOMSCRIPTS PZPEGA_UI_DOC_LIFECYCLE PZPEGA_CONTROL_DROPDOWN

SR-B47513 · Issue 328997

Logic updated for expandAll to resolve CME

Resolved in Pega Version 7.4

A concurrent modification exception was appearing on a node level page when using expandAllToproperties due to two threads simultaneously trying to expand the page. This has been fixed by modifying the logic in expandAll(true, true).

SR-B64115 · Issue 330040

Handling and logging added for null PRThread tenant ID

Resolved in Pega Version 7.4

In cases where no PRThread was not found from the thread container when writing a ruleset index to DB, the tenant ID was lost and the system used the default "Shared". This resulted in a tenant RSL shown twice in the DB, one as the tenant itself and the other as Shared. Two changes have been made to resolve this: first, debug logging has been added to the stack trace if the thread is null, and second, if this happens in a MT environment, the system will skip writing to the DB so the tenant TSL will not be given as Shared.

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