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-C6751 · Issue 349286

Corrected duplicate table names for DB2 z/OS import

Resolved in Pega Version 7.4

When using Explicit DDL generation for DB2 z/OS, auxiliary tables were generated with the same name when deploying on single schema deployment. This happened when importing archives that created tables in both the PegaRULES and PegaDATA logical DBs when those logical DB names corresponded to the same database schema, and was due to the handling of lob table names for single schema deployments using Pega DB logical names for storing the last generated index. This has been fixed by changing to tracking the last generated index by DB2 z/OS database name / database schema name in order to prevent PegaRULES and PegaDATA lob tables from having naming collisions.

SR-C6751 · Issue 349078

Corrected duplicate table names for DB2 z/OS import

Resolved in Pega Version 7.4

When using Explicit DDL generation for DB2 z/OS, auxiliary tables were generated with the same name when deploying on single schema deployment. This happened when importing archives that created tables in both the PegaRULES and PegaDATA logical DBs when those logical DB names corresponded to the same database schema, and was due to the handling of lob table names for single schema deployments using Pega DB logical names for storing the last generated index. This has been fixed by changing to tracking the last generated index by DB2 z/OS database name / database schema name in order to prevent PegaRULES and PegaDATA lob tables from having naming collisions.

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"

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