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-134932 · Issue 578544

Timeout for node to join cluster increased and made configurable

Resolved in Pega Version 8.5.1

Hazelcast timeouts were causing application restart failures. This was traced to a rare case scenario of heavy processing on the primary node causing the new node to not be able to join the cluster within the designated 5 minute threshold. To compensate for this, the default time to join has been increased to 9 minutes and a prconfig setting has been added to configure the time setting.

INC-133270 · Issue 581839

Automatic agent restart added for temporary connection issues

Resolved in Pega Version 8.5.1

An agent that was stopped due to an issue with the database connection did not recover when the connection was reestablished. To resolve this, updates have been made that will handle an automatic restart of the agents when there are temporary connection issues.

INC-135359 · Issue 587038

CORS header configuration added for Stream tier

Resolved in Pega Version 8.5.1

An enhancement has been added that allows setting the CORS header (Access-Control-Allow-Origin) to allow *.DOMAIN.com on Stream tier (/stream/view & /stream/click) calls by way of the setting /stream/httpHeaders .

INC-134069 · Issue 583024

Added Kafka logging

Resolved in Pega Version 8.5.1

In order to help diagnose issues encountered during Kafka background processing, additional logging has been added to QueueProcessorDatasetHandler.

INC-142792 · Issue 594499

Modified thread data page cleanup

Resolved in Pega Version 8.5.1

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-125122 · Issue 581255

JMX authentication added

Resolved in Pega Version 8.5.1

Support has been added for JMX authentication through user and password.

INC-130886 · Issue 590374

Bad Stream error after passivation resolved

Resolved in Pega Version 8.5.1

A "Bad Stream" error was seen when attempting to reassign a case to the Workbasket, and a save of the work object failed. This was caused by a corruption of the work object during passivation, and has been resolved.

INC-130265 · Issue 580309

Cross-site scripting updates

Resolved in Pega Version 8.5.1

Additonal Cross-site scripting protections have been added to pyActivity processing and pzTransformAndRun.

INC-141570 · Issue 597845

Performance improvement for first JVM with Oracle

Resolved in Pega Version 8.5.1

After performing a fresh installation of Pega with Oracle DB, the first JVM was taking an excessive amount of time to come up, and logins were also very slow. This was caused by code that optimized node startup query performance by shipping completed assemblies for Oracle that are not recommended for use with newer Oracle versions (10 or newer). This has been resolved.

INC-122072 · Issue 581029

Delay in writing database template records resolved

Resolved in Pega Version 8.5.1

After upgrade. a real-time event based campaign with an offer flow that used a database template showed an excessive delay in updating the database template. A queue entry related to "WriteOutboundAgent" was also showing as failed, and analysis of the logs showed that the transaction type was not being set. This was traced an exception during a regular close operation of the result set iterator: the API used to close the transaction contained code specific to PostgreSQL while the site was using Oracle. This has now been resolved.

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