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.

INC-193767 · Issue 683298

Handling updated for validating properties with a FieldValue

Resolved in Pega Version 8.5.6

Running a report which included a property calculated by a Declare Expression generated an excessive number of log messages indicating "Error occurred while executing forward chaining on page 'pyReportContentPage.pxResults". Degraded system performance, stack overflow, and other similar issues were seen. This was traced to an infinite loop that resulted from a missed use case for a Report Definition with a Target property of a Declare Expression with FieldValue, and has been resolved by disabling autochain while validating properties with a FieldValue.

INC-194490 · Issue 685238

Parameter handling updated for GetRepositoryFolderName

Resolved in Pega Version 8.5.6

An UnresolvedAssemblyError was generated with an Unauthenticated Thread exception after opening the declare expression Embed-Application-StorageProvider pyFolder and performing a private edit. This error was traced to the Rule-Utility-Function call "pxGetRepositoryFolderName()", which was expecting a parameter "tools" which was not being passed from the declare expression rule. To resolve this, the pyFolder and pyFoldeIf declare expressions and pzsetContentStorage have been modified to pass 'tools' as a parameter to pxGetRepositoryFolderName.

INC-194806 · Issue 680967

Performance improvement for message processing

Resolved in Pega Version 8.5.6

Severe performance degradation was seen for message processing in pdc-central after update. Investigation showed there was an issue with a write lock not not being acquired while reloading the datapage definition, causing concurrent dirty reads and multiple definition reloads. To resolve this, DeclarativePageDefinitionCacheImpl has been updated to acquire a write lock to prevent dirty reads of the same stale data page definition while reloading.

INC-195586 · Issue 698859

Updated access group handling for CurrentWorkPool property

Resolved in Pega Version 8.5.6

After update, the pxThread.pxCurrentWorkPool property was not properly populated in App Requestors when the activity was called from Rest service. This was caused by a difference in the authentication check after a security modification, and has been resolved.

INC-197479 · Issue 695024

ClusterAndDBCleaner updated to with with Oracle query limits

Resolved in Pega Version 8.5.6

The pzClusterAndDBCleaner job scheduler was not able to cleanup data in pr_op_data session table due to the delete query formed to clean up this table throwing "ora-01795 maximum number of expressions in a list is 1000 oracle 19c" exception. This has been resolved by splitting requestor IDs into batches of 1000.

INC-199192 · Issue 689036

Check added to ensure StepPage generation for Top keyword

Resolved in Pega Version 8.5.6

A ClassCastException was thrown when top page is used, indicating "com.pega.pegarules.data.internal.clipboard.ClipboardPropertyImpl cannot be cast to com.pega.pegarules.pub.clipboard.ClipboardPage". This has been resolved by adding a check which will generate a myStepPage for Keyword "Top" as necessary.

INC-199320 · Issue 690621

Corrected duplicate record error message

Resolved in Pega Version 8.5.6

When inserting a duplicate record in a grid, the error was shown at the harness level instead of the record level. This was traced to the error messages being removed from the step page, and has been resolved by updating the system so messages will not be cleared if the same value is being set.

INC-199341 · Issue 694713

Content-type values made consistent

Resolved in Pega Version 8.5.6

The content-type for service APIs was returned as 'text' for 401 errors when using a custom authentication type instead of the parent-type/child-type format such as text/plain, text/html, application/json, etc. This has been corrected.

INC-199679 · Issue 688736

Handling added to email encoding for ISO-8859-8-i charset

Resolved in Pega Version 8.5.6

After update, cases were intermittently not getting created from inbound email and the process became stuck. This has been resolved by adding handling to replace the ISO-8859-8-i charset with ISO-8859-8 for encoding the mail content.

INC-199749 · Issue 695536

Updated use of declarative processing during performance testing

Resolved in Pega Version 8.5.6

After update, the performance test script build was not working. A stack overflow indicated an issue with the load activity for the D_InteractionHistory data page referenced by expressions/properties. This has been resolved by disabling declarative processing during the estimation of data size.

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