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-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-B81422 · Issue 332673

Fixed null-pointer exception on rollback

Resolved in Pega Version 7.4

Attempting a rollback using prpcServiceUtils.properties and serviceConnection.properties was causing an null-pointer exception. This has been resolved with improved error handling.

SR-B81422 · Issue 330657

Fixed null-pointer exception on rollback

Resolved in Pega Version 7.4

Attempting a rollback using prpcServiceUtils.properties and serviceConnection.properties was causing an null-pointer exception. This has been resolved with improved error handling.

SR-B84123 · Issue 333253

Documentation corrected for path to PostgreSQL on SUSE Linux

Resolved in Pega Version 7.4

An incorrect path was included in the Linux documentation for the instructions to install pljava: the correct path is "PostgreSQL_Home"/lib64/ , and the documentation has been corrected to reflect that.

SR-B86779 · Issue 340677

Dirty state check added to TabbedScreenFlow data import

Resolved in Pega Version 7.4

In Data Import Wizard, selecting a file to import and then clicking cancel produces the prompt "You are about to discard your changes". After that, clicking Cancel and then Next caused the data wizard screen to vanish and the activity status message screen appeared. This was due to a missing dirty state check for the import harness pzTabbedScreenFlow7, and has been fixed.

SR-B87348 · Issue 334834

Deployment guides updated for Tomcat 7.3.1

Resolved in Pega Version 7.4

The deployment guides have been updated to reflect that Tomcat 7.3.1 has dropped the explicit reference to the urandom syntax that had been added in version 7.3.

SR-B89463 · Issue 338119

Upgrade error message enhancement

Resolved in Pega Version 7.4

An enhancement has been added to the upgrade process to give a more robust error message that can be used to help determine which parameter error needs to be 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