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-140341 · Issue 593706

Cross site scripting updates

Resolved in Pega Version 8.6

Additional cross site scripting protections have been added to pyActivity processing and pzTransformAndRun.

INC-140421 · Issue 595472

DSS added to enable short-term IBM MQ tracing

Resolved in Pega Version 8.6

In order to support on-demand MQEnvironment tracing, a DSS property has been added to enable tracing for a day. This is done by setting the DSS property IBMMQEnabler = true , which will set MQEnvironment.enableTracing(86400000); and tracing will be enabled for a 24-hour period.

INC-140750 · Issue 589926

Resolved post-passivation login issue

Resolved in Pega Version 8.6

An authentication error was seen when operators tried to log in again after passivation. This was traced to a corrupted BLOB, and has been resolved.

INC-140879 · Issue 596570

Agent tracing handling updated

Resolved in Pega Version 8.6

When attempting to trace agents the error "Unable to trace the agent" appeared on screen. Investigation showed that the data page used by the Tracer was not always available in a thread that was displaying the section, most commonly if the section was using deferred loading. This has been resolved by using a data page available in a thread that opens a Tracer's section.

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.

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