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-202510 · Issue 695889

SOAP connector supports OAuth2 profile

Resolved in Pega Version 8.7.1

Support has been added for using an OAuth2 profile as one of the allowed profiles for SOAP connector.

INC-204897 · Issue 696163

Log4j file security vulnerability issue addressed

Resolved in Pega Version 8.7.1

A zero-day vulnerability was identified in the Apache Log4j logging software which could potentially allow malicious actors to take control of organizational networks. Pega has immediately and thoroughly addressed this issue. More information can be found at https://docs.pega.com/security-advisory/security-advisory-apache-log4j-zero-day-vulnerability .

INC-174409 · Issue 661658

Article on "Specifying the content of a product rule" updated

Resolved in Pega Version 8.7.1

The documentation for the 'Class instances to include' section of the Rule-Admin-Product form has been updated to more clearly specify that the report definition used as a filter requires the inclusion of the pzInsKey property in the data returned from the report definition. This can be accomplished by either of the following: * Include pzInsKey 'Edit columns' (Query Tab) section of the report definition. --or-- * On the 'Data Access' tab, 'Row key settings' section, check the 'Get row key' checkbox (it will list the row keys for the class -- pzInsKey should be among them).

INC-195216 · Issue 686911

MSGraph documentation updated

Resolved in Pega Version 8.7.1

The documentation for using MSGraph has been updated to reflect that standard headers cannot be overridden.

INC-170458 · Issue 667371

Handling updated for queue processor locks

Resolved in Pega Version 8.5.6

The Final activity mentioned in the processing epilog of the Service File rule was not being consistently called from File Listener, causing some of the cases to become stuck and not continue to the next stage. Investigation showed that if the lock was held by the queue processor requestor, the system was unable to obtain the lock but still proceeded to update the LogServiceFile page and persist it. This resulted in overwriting changes made on the LogServiceFile page by the requestor, resetting the completed-batches-count set back to 0. To resolve this, RuleServiceFile -> updateLSFBatchCounts() will call the overloaded lockAndLoad() method in LogServiceFile that accepts a parameter called lockAttempts. This will attempt to obtain a lock for a given number of times before throwing an exception.

INC-172849 · Issue 665981

SortPageList method updated for Obj-Sort

Resolved in Pega Version 8.5.6

Sorting page lists backed by a node level datapage using Obj-Sort was causing a ConcurrentModificationException. This has been resolved by updating the SorterImpl.sortPageList method to use java7CollectionsSort instead of collectionsSortWithInferenceEngineDisabled.

INC-173434 · Issue 672674

Pushservlet cookie path updated to resolve error

Resolved in Pega Version 8.5.6

A very large number of exceptions were being logged indicating "Unhandled error in web.request.internal.URLComponentProcessorImpl.populateCSRFToken", impacting the ability to perform log analysis. This exception has been resolved by updating the pushservlet cookie path.

INC-176138 · Issue 668937

Decision table query performance improvements

Resolved in Pega Version 8.5.6

Work done previously to improve performance by preventing the decision rule from being treated as a custom rule has been further augmented by preventing the standard Declarative Rules from being treated as Custom Rules while building the Declarative Cache.

INC-180891 · Issue 663513

Zip compression added for tracer XML

Resolved in Pega Version 8.5.6

After upgrading from Pega 7 to Pega 8, attempting to save and download a trace session would run for a time before pausing and displaying the message "Operation failed. Network error". Investigation showed the tracer was generating a very large XML file which was consuming the heap and causing the issue. To resolve this, an update has been made that will reduce memory usage by using GZip compression on the file. The new behavior will be to always zip tracer XML by default.

INC-180901 · Issue 666445

Heap dump ability added for OpenJDK

Resolved in Pega Version 8.5.6

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

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