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.

SR-D29034 · Issue 500682

Added support for JSON mapping of deep nested pagelist objects

Resolved in Pega Version 8.1.7

An exception occurred when using a JSON data transform in the service activity to map the clipboard data to JSON on the third level of a structure formed as Pagelist-->page-->pagelist. To resolve this, support has been added for nested pagelist mapping with deep nesting of objects (configured for one sided actions) and arrays.

SR-D38931 · Issue 507058

Support added for Multiple Set-Cookies in Connect REST

Resolved in Pega Version 8.1.7

When using a REST connector, the service returned multiple cookies as separate Set-Cookie response headers, but only the last header value received was stored when using pzResponseHeaderMap on the parameter page. In order to support this use, changes have been made to store multiple header values from Connect-REST responses.

SR-D18853 · Issue 503274

Visibility on client check removed to enable Pulse on click

Resolved in Pega Version 8.1.7

When Pulse was configured on click of a icon, the comment section was not visible. Investigation showed that at the time of DOM load, pyMessage property was not available in the DOM because 'Run visibility condition on client' was checked by default. Visibility on client checks have been removed to resolve this issue.

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.

INC-181773 · Issue 685435

Attached zip file has correct extension

Resolved in Pega Version 8.5.6

When using a custom function with the SendSimpleEmail activity, an attached .zip file was corrupted on receipt. The issue was not present with other mime types (ex. images, docs, pdf). Investigation traced this to the extension for the zip file being incorrectly set as xzip or multipart, and this has been resolved by adding a condition to set the extension correctly.

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