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.

INC-136264 · Issue 582469

Chatbot text starts scroll at top of answer

Resolved in Pega Version 8.2.8

In order to present an improved interface for customers interfacing with chatbots, the code has been updated so that the recipient's chat scroll will remain at the top of an answer that would scroll off the screen.

INC-125122 · Issue 581253

JMX authentication added

Resolved in Pega Version 8.2.8

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

INC-135359 · Issue 587036

CORS header configuration added for Stream tier

Resolved in Pega Version 8.2.8

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

INC-132963 · Issue 572247

Class Loader cache values wrapped with WeakReference for improved cleanup

Resolved in Pega Version 8.2.8

Out Of Memory exceptions due to Metaspace were observed on Web tier instances running with a max Metaspace size of 2GB. Investigation showed that in PRClassLoaderDB, mLoaderCache values were wrapped with a SoftReference. To resolve this, the Class Loader cache values will be wrapped with a WeakReference, allowing the cache to free memory when it is no longer needed. JVM options has also been added to switch types of References being used if there is a preference.

INC-134412 · Issue 577541

Proposition filter maintains eligibility criteria

Resolved in Pega Version 8.2.8

Eligibility details were occasionally lost when updating Offers. This was traced to a configuration that could cause individual criteria rules to be deleted when rows were added in the middle of the list. To resolve this, validation has been added to each eligibility criteria row to ensure that all expected values are entered for each row, and validation has been added to the logic string when advanced mode is used for offer eligibility criteria.

INC-135823 · Issue 580944

Transient property passivation handling improved

Resolved in Pega Version 8.2.8

Frequent "" errors were seen in the production log file while working on the WO. This was traced to corruption in the blob caused by transient properties during passivation. To resolve this, corrections have been made to the handling for the transient property entries in the blob.

INC-138840 · Issue 599979

Data-Summary reports default will not use the rule resolved setting

Resolved in Pega Version 8.2.8

An intermittent issue was seen where a query could become stuck for ~2 hours in the database. This has been resolved by setting the default for Data-Summary reports to not use the rule resolved setting.

INC-127976 · Issue 566157

Delete Requestor method updated for use with CMT

Resolved in Pega Version 8.2.8

JMS MDB Listeners with Container Managed Transaction (CMT) enabled in Websphere 8.5 had global transactions fail. To initialize a JMS-MDB listener, a requestor of type APP is used. Upon the service being fully initialized, the requestor is removed by executing a delete operation followed by a COMMIT. However, in this scenario, the initialization operation is running within a CMT context and a SQLException was raised indicating that the commit was not allowed. To resolve this, the delete requestor method has been refactored to take into account the CMT context so the commit is not executed if the transaction is managed by the container.

INC-121359 · Issue 571026

Resolved sync error for offline workorder

Resolved in Pega Version 8.2.8

After logging on to the mobile app and then switching to off-line mode before opening a workorder from the worklist and processing the full workorder from end to end in offline mode, reconnecting resulted in the work order being moved to the [email protected] work basket with “Sync-Failed” status. Investigation showed that this was a caused by the DateTime properties being an empty string or null despite being created with a valid string. This was traced to the datetime conversion handling, and has been resolved.

INC-127229 · Issue 568096

HTTPClient updated to match Apache's ConnectionRequestTimeout changes

Resolved in Pega Version 8.2.8

Connect Rest services were not timing out at the expected 60 second mark, but were instead running for 120 or even 200 seconds. This bug arose as a result of Apache's refactoring of their HTTPClient in version 4.3. This refactoring split ConnectionTimeout into two variables, ConnectionTimeout and ConnectionRequestTimeout, in order to give users more granular control over client timeout behavior. The implementations of HTTPClient have now been amended so that all HTTP Client configurations set ConnectionRequestTimeout appropriately.

We'd prefer it if you saw us at our best. is not optimized for Internet Explorer. For the optimal experience, please use:

Close Deprecation Notice
Contact us