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-141570 · Issue 597844

Performance improvements for first JVM start and login

Resolved in Pega Version 8.6

First JVM start and first log in were taking a long time with Oracle DB. To resolve this, several updates have been made to optimize performance.

INC-141838 · Issue 598173

Locking and classmap improvements

Resolved in Pega Version 8.6

Threads were getting stuck inside classMap and tableInformationMap, causing nodes to go down. This was traced to issues with class map performance and locking, and has been resolved by replacing the lock library with a newer version and refactoring the tableInformationMapImpl class to use a concurrent hashmap instead.

INC-142036 · Issue 594579

Additional BIX logging added

Resolved in Pega Version 8.6

In order to improve the ability to trace and resolve issues related to BIX extract rule failures, additional diagnostic logging has been added.

INC-142188 · Issue 600329

Resolved parent lock sending child item to broken queue

Resolved in Pega Version 8.6

esolved parent lock sending child item to broken queueIf the ServiceLevelEvents agent tried to process the queue item for a child case but encountered a lock error because the parent case was locked, the queue item was immediately going to the Broken-Process status instead of re-queueing the item to try again in 15 minutes. If the property was set to 'Copy data from a data page', the item was re-queued. To resolve this, the unwind and forward chain calls have been reversed. A dynamic system setting is available to reset the change.

INC-142569 · Issue 597898

CORS headers added for Health check URL

Resolved in Pega Version 8.6

Pega Health Check URLs were throwing CORS error when invoked for application Health checks. This has been resolved by adding CORS headers for pingService responses.

INC-142792 · Issue 594501

Modified thread data page cleanup

Resolved in Pega Version 8.6

Some cases were becoming stuck at a particular stage and not proceeding further even though the task in the backend was complete. Investigation traced this to work done that removed declarative pages at the thread level to optimize performance while other clipboard pages were retained, and the issue has been resolved by deleting all thread data pages after every item processed by the agent.

INC-142831 · Issue 605474

Corrected Outlook web inline image handling

Resolved in Pega Version 8.6

Outlook web was not able to render inline images and instead added them as external attachments. Investigation showed inline images were not being rendered properly in Outlook web due to the disposition not being set. This has been corrected.

INC-143376 · Issue 604530

Adding handling for property without parent page

Resolved in Pega Version 8.6

Filtering was not working for a DateTime control in an optimized grid with embedded property which was a function alias defined in a report definition referenced by a Data Page. This was traced to the system assuming that every property has a parent page, which this use case did not. To resolve this, an update has been made that will return null for the parentGroupOrListProp if one does not exist.

INC-143461 · Issue 601840

Updated JSON DT nested page property handling

Resolved in Pega Version 8.6

In a JSON data transform, when using an "Update page" step on a single-page property, as a child step of an "Append and map to" step where a page list property is given, the page list was populated with only one result but the single-page property was treated like a page list and received multiple results. This has been resolved by updating the ClipboardJSONDeserializer implementation and downstream abstractions to support "clipboard only" relations as properties in nested Page Lists.

INC-143668 · Issue 617488

Performance improvements for Attachment Migration Utility

Resolved in Pega Version 8.6

The Attachment Migration Utility was showing a zero count for attachments in the Pega Database. This was traced to the underlying report definition that retrieves data for the Attachment Migration Utility timing out, and has been resolved by updating the activities to improve performance for applications having a large number of attachments without customization.

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