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 note: beginning with the Pega Platform 8.7.4 Patch, the Resolved Issues have moved to the Support Center.

INC-179025 · Issue 665546

Null check added for getTargetNodeUUID

Resolved in Pega Version 8.7

A null pointer error was seen from the tracer during a security scan. This has been resolved with the addition of a null check for TracerRequest.getTargetNodeUUID.

INC-179106 · Issue 662617

Null data page check added for DataPageTelemetryImpl

Resolved in Pega Version 8.7

Recent work was done to modify the StreamChangeTracker trackValueChanges API to return false when invoked for properties of mode page. An additional null check has been added in DataPageTelemetryImpl.recordDataPageLoaded to handle a null pointer exception caused by null data page definitions.

INC-179167 · Issue 659590

Atmosphere update

Resolved in Pega Version 8.7

The Atmosphere jar has been updated to version 2.4.5.9.

INC-179448 · Issue 676270

Tracer protections updated

Resolved in Pega Version 8.7

Cross-site scripting protections have been updated for Tracer.

INC-179837 · Issue 658967

AES call to mbean disabled

Resolved in Pega Version 8.7

Under certain conditions, the AESRemote 'push memory' agent call to the legacy memory management mbean caused unexpected behavior in declarative rules for work running in data flows and queue processors. This has been resolved at this time by overriding the push memory usage agent activity to skip mbean and connect REST.

INC-180184 · Issue 665091

Assistance and diagnostics added for issue with opening imported 'when'

Resolved in Pega Version 8.7

After upgrade, attempting to open rules that were developed on lower environments and then imported resulted in unknown errors. A workaround has been added to skip and log any corrupted property that might be interfering with the rule opening: enable Skip-Corrupt-Property to put this in place. To improve diagnostics, the new logger NBA-WME-DEBUG has been added. If the error continues after using Skip-Corrupt-Property, Skip-Corrupt-Property should be disabled and NBA-WME-DEBUG should be enabled and kept active until the issue occurs again.

INC-180901 · Issue 666447

Heap dump ability added for OpenJDK

Resolved in Pega Version 8.7

Support for OpenJDK has been added to the heap dump generation process.

INC-182148 · Issue 668009

Handling added for missing schema for persistClusterState

Resolved in Pega Version 8.7

The message "Error retrieving database indices java.lang.NullPointerException" was being logged repeatedly, indicating an issue with ClusterManagementAPI. Investigation showed there were missing default Schema values in the prconfig files, and this has been addressed by adding fallback scenarios for missing schema information during PersistClusterState.

INC-182537 · Issue 667592

French added to Locale List Separator

Resolved in Pega Version 8.7

Exporting data to Excel in CSV format resulted in text with French accent characters such as "Décision pour une nouvelle demande de règlement" to appear as random characters, and columns were not being split. This has been resolved by adding a record for the French locale in the pzGetLocaleListSeparator decision table rule.

INC-182572 · Issue 663557

Support added for multiple host proxy architecture

Resolved in Pega Version 8.7

When using an architecture where certain types of users were sent through multiple proxy servers to get the Pega Cloud instance, an exception was generated at the point of accessing the environment. This was traced to the use of Apache 2.4 with mod_proxy. As the request passed through each proxy, the x-forwarded-host header had values appended to it by mod_proxy which resulted in the error "com.pega.pegarules.pub.context.PRSecurityException: Multiple host names in header X-forwarded-Host". This has been resolved by updating the code to support using a multiple host proxy configuration.

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