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

INC-153138 · Issue 625567

Database primary keys generated as NONCLUSTERED for imports

Resolved in Pega Version 8.4.5

When a primary key was defined for a table and the table was exported and then imported, the primary key was generated as CLUSTERED. This resulted in an MS SQL Cluster Index violation because all Pega-shipped tables generated during installs/upgrades have a PK constraint index with NONCLUSTERED index type as it allows for a longer key. This was a missed use case, and has been resolved by updating the system such that when importing with MS SQL database, the primary key index is made NONCLUSTERED all the time so it will be consistent with the base platform.

INC-154042 · Issue 621259

Pega Catalog custom upload control modified

Resolved in Pega Version 8.4.5

Attempting to upload a catalog.zip file caused the system to hang and thread dumps were seen in the logs. Investigation traced the issue to the custom control used to upload the catalog, which was posting the entire content in form data rather than sending a multi-part request. The control contained both legacy code which used form.submit() and encoding along with new code that used SafeURL and sent an async request. With this, encoding could not be set to multi-part in case of an AJAX request. To resolve this, the catalog upload control has been modified to use the appropriate legacy code that performs form.submit() and sets the encoding properly.

INC-157196 · Issue 629296

Deprecated service package features now require authentication

Resolved in Pega Version 8.4.5

Authentication has been added to deprecated features of the standard service package to improve security. If issues are encountered during product migration, please use the Deployment Manager.

INC-158519 · Issue 625078

Filter considers all instances pages during deployment

Resolved in Pega Version 8.4.5

During package deployment, attempting to use Filter to skip some of the instances only displayed the result of the current active page instead of all pages. This was an unintended consequence of previous work, and has been resolved by adding the logic to strip quotes in the value and adding the "Pagination activity manages filtering" checkbox by default.

INC-159834 · Issue 632247

StackOverFlow logging improved

Resolved in Pega Version 8.4.5

Enhanced diagnostic logging information has been added to help find issues when StackOverFlow errors occur.

INC-160288 · Issue 626066

Kerberos handling updated for database remap

Resolved in Pega Version 8.4.5

After upgrade from Pega v7.2 to Pega v8.4, using Kerberos authentication was failing during the remap task. Investigation showed that null username and password values were being passed to SchemaAssignmentUtility along with the flags as arguments, causing the utility to misinterpret the arguments. As arguments should be populated only when flags and values are available and not null, an update has been made which will set the username and password flags only if they are not null in the Remap database tables target.

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