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.

INC-130304 · Issue 567923

Retry logic added for downloading upgraded rules

Resolved in Pega Version 8.5.1

A Rules upgrade failed while downloading applications from the maintenance server due to an SFTP server connection failure. This has been resolved by adding logic to retry if the first connection attempt fails.

INC-130304 · Issue 567926

Retry logic added for downloading upgraded rules

Resolved in Pega Version 8.4.3

A Rules upgrade failed while downloading applications from the maintenance server due to an SFTP server connection failure. This has been resolved by adding logic to retry if the first connection attempt fails.

INC-133214 · Issue 590378

Deployment Manager rollback works for directed inheritance

Resolved in Pega Version 8.4.3

Rollback was not working correctly in Deployment Manager for history classes using directed inheritance. This was traced to a redundant check in AbstractHistoryPageKeeper that enforced the history pages pattern inherited from one of the base history classes, and this has now been removed.

INC-140093 · Issue 592310

Upgrade Applications Schema filtering update

Resolved in Pega Version 8.4.3

The Pega Installer was failing at Pega Rules Upgrade with an error indicating "Rules Schema assoc_data Index already exists". This has been resolved by updating the Upgrade Applications Schema to use filter for compare, but not to get custom tables.

INC-141641 · Issue 596632

Upgrade Applications Schema filtering update

Resolved in Pega Version 8.4.3

The Pega Installer was failing at Pega Rules Upgrade with an error indicating "Rules Schema assoc_data Index already exists". This has been resolved by updating the Upgrade Applications Schema to use filter for compare, but not to get custom tables.

SR-119963 · Issue 176108

Corrected record imports in multitenant environment

Resolved in Pega Version 7.1.8

In the multitenant environment, reimporting an operator record using application -> import was causing an 'IntegrityConstraintViolationException' exception. This was caused by the query not being properly tenant-qualified for the environment, and has been corrected.

SR-121277 · Issue 181001

Deployment user privileges updated for upgrades

Resolved in Pega Version 7.1.8

When attempting to upgrade some installations, the upgrade script was failing while trying to determine the current PRPC version. This was caused by the deployment user lacking the DBA privileges to read/write the tables in the rules and data schema, and has been updated.

SR-121709 · Issue 179068

New default directory setting added to DDL generation

Resolved in Pega Version 7.1.8

If the DDL for a new PRPC installation was generated without using the optional parameter for the file location, the file was created in the root directory. To avoid this, a default gen_dir setting (./schema/generated) has been added to generateDDL.sh to handle cases when the parameter has not been set.

SR-122215 · Issue 180037

Resolved installation errors for DB2 Z/OS with WebSphere

Resolved in Pega Version 7.1.8

A problem was encountered while installing split schema on a DB2 z/OS system with WebSphere. This was caused by an erroneous system setting where the ports to the DB2 database were not open in this environment. While the Admin could correct the environment to open the ports and allow the application server node to connect to the DB2 database, this has been changed in the software to default to the correct settings.

SR-122292 · Issue 182878

Operators and Access Groups are now automatically force re-indexed during import

Resolved in Pega Version 7.1.8

If a number of new OperatorIDs were created and added to two workgroups and then the changes were exported, the new OperatorIDs were present when the file was imported to other environments but a query run against the table PR_INDEX_OPERATOR_WORKGROUP did not incorporate the new IDs. While there was a workaround of manually forcing a re-index during import to fully incorporate the new IDs, the Operators and Access Groups are now automatically force re-indexed during import to ensure data is up to date.

Ready to crush complexity?

Experience the benefits of Pega Community when you log in.

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