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

SR-B90072 · Issue 343826

global/ServiceExport directory created after restart

Resolved in Pega Version 7.4

The global/ServiceExport directory was not created after restart due to an error in the refactoring static content logic for MultiTenancy. As part of correcting this, the system will initialize the static content directories at a later point and not during the initialization of static content class.

SR-B91026 · Issue 338537

Update Guide documentation errors fixed

Resolved in Pega Version 7.4

The Update Guide documentation has been updated to correct two errors; 1) page 11 now correctly indicates that updates are available for Pega v7.1.0 and higher. 2) page 58 now correctly indicates the parameter name is 'upgrade' in the instruction "Type generateddl.bat or generateddl.sh and pass in the required --action argument #generateddl.bat --action upgrade"

SR-B92155 · Issue 345201

ConditionsUtils library present after migration

Resolved in Pega Version 7.4

The ConditionsUtils functions were failing to compile after migration. This was traced to the ConditionsUtils library not having been included in the migration, and has been 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