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-143861 · Issue 597558

pzIsScalar 'when' rule updated for Value list and Value group

Resolved in Pega Version 8.2.8

When using the GET/Cases/{ID} API to fetch details about a case, an intermittent HTTP 500 error appeared. This was traced to the 'when' condition pzIsScalar being returned as true for the ValueList property types and trying to set the value on the summaryData embedded page. This has been resolved by updating the pzIsScalar 'when' rule to better handle Value list and Value group.

INC-144358 · Issue 601013

Localization added for "Automatically" and "Manually" field values

Resolved in Pega Version 8.2.8

The Dutch translation of "Child case [Case_type] [Case_id] has been [Instantiation_mode] instantiated" used the hard-coded English expression "manually". This has been resolved by adding the "Automatically" and "Manually" field values to localization.

SR-D72456 · Issue 561116

Added duplicate page handling for Bulk actions

Resolved in Pega Version 8.2.8

Trying to resolve cases using Bulk Actions and Bulk Resolve resulted in the exception "Trying to save an invalid page. The cover open count is incorrect; it is -1". This was traced to duplicate pages available on the clipboard with same the insHandle. To resolve this, the pzUpdateAndDeleteAssignments activity has been updated to check for duplicate pages, then pick the right page which is not being served by the findPageByHandle engine API.

SR-D77719 · Issue 569770

OpenIfStale updated to resolve optimistic locking race condition

Resolved in Pega Version 8.2.8

A race condition was created in optimistic locking by having two assignments save at overlapping times. This has been resolved by modifying the pzShowConflicts activity to use a version of openIfStale which will consider a workpage as stale even if the difference in pxUpdateDatetime is in milliseconds.

SR-D98224 · Issue 580592

Updated endpoint Cross-site scripting protection

Resolved in Pega Version 8.2.8

Cross-site scripting security has been updated for Endpoints in Display activities.

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 *.DOMAIN.com 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.

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