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.

SR-D20144 · Issue 493561

Function LengthOfPageList resolves correctly for Insure framework

Resolved in Pega Version 8.3

When using the Insure framework, it was not possible to expand any steps in the activity. Investigation showed that the rule 'LengthOfPageList' was present in the library Utilities in two different rulesets – Pega Rules and Pega Insure CSB. When the rule was cached with an application stack containing Pega Insure CSB, it generated a "Failed to find instance" error for applications that did not use Pega Insure CSB in the stack. During the run-time call to the correct LengthOfPageList() RUF was not resolved because of ambiguity in the resolution. To correct this, the call to the RUF will now contain a fully qualified name.

SR-D26101 · Issue 494891

Added explicit step page to resolve NPE with custom error message

Resolved in Pega Version 8.3

A null pointer exception was generated during case run time harness refresh after a custom error message was inserted. This was traced to a blank step page related to the custom message, and has been resolved by adding a primary step page at step 10 of the New(Work-) activity to prevent the NPE on harness reload.

INC-163292 · Issue 635837

Portlet service deprecated

Resolved in Pega Version 8.4.6

Portlet authentication services have been removed from the standard installation package.

SR-C81829 · Issue 419227

pxCoveredCountOpen value decrease corrected

Resolved in Pega Version 8.2.1

When a flow reached the resolved stage (Resolved-Withdrawn), pxCoveredCountOpen was reducing the count by 2 instead of 1, eventually causing the value to go negative and prevent any further work objects from being marked as Withdrawn. Investigation showed the "Update status" activity was being called twice due to the Temporary WorkPage used to delete assignments persisting and appearing as a duplicate pyWorkPage. This caused an issue when using findPage by pzInsKey. To correct this, the "pxDeleteAssignmentsForWork" activity for Step-15 has been modified to explicitly remove the temporary WorkPage after the assignment is deleted.

SR-C85035 · Issue 421947

Added getIfPresent check for Field Value parameters with pzAPICreateJsonForView

Resolved in Pega Version 8.2.1

Calling pzAPICreateJsonForView was altering case values if localized field value parameters were added. This has been corrected by performing a getIfPresent and getIfString on the property pyFieldValueParams so field value parameters will not be added to the main page if they're not present.

SR-C82244 · Issue 421173

Enhancement made to allow passing of URL in actionset via the DX API

Resolved in Pega Version 8.2.1

When using the action "Open URL in Window" and the option "Use Alternate Domain" to pass a URL that is in saved in a property, the name of the property was passed when using the DX API instead of the URL. To allow this use, an enhancement has been added to support storing a last submitted value and a reference so that an action set with a property reference can return a reference object with lastSavedValue and the reference name attached.

SR-C83915 · Issue 421168

Enhancement added to support property reference name for section include

Resolved in Pega Version 8.2.1

When requesting the view of a section from a repeating dynamic layout where the name of the section is taken from a property, the DX API returned an error on the tracer indicating "Invalid value for aReference passed to com.pega.pegarules.data.internal.clipboard.ClipboardPageImpl.getString(String)". This has been resolved by adding an enhancement to support using a property reference for section include.

SR-C75566 · Issue 420773

Added null check to avoid DisplayCardAccountHeader rendering issue

Resolved in Pega Version 8.2.1

When the out of the box section DisplayCardAccountHeader was created by View editor and then converted to full section editor, the embedded sections were empty or not seen. This was traced to the design view javascript hitting an error which caused the design view rendering to fail. To correct this, pzpega_ud_gridlayout_model has been updated to wrap the line in question with a null check and set the value to empty string if it doesn't already exist in the model.

SR-C83808 · Issue 421298

FIRST aggregate in bucketed window fixed

Resolved in Pega Version 8.2.1

FIRST aggregates were not giving the correct results if used in a Sliding Time window together with an average aggregate.This was traced to an incorrect implementation of FirstAggregatorHolder.substractAggregate which used propertyIndex to get aggregate value (which was not correct in this context), and has been fixed by using the correct index in FirstAggregatorHolder class.

SR-C80215 · Issue 421849

Migrated Data Flows open correctly from the data flow landing page

Resolved in Pega Version 8.2.1

After upgrade, Data Flows made in an earlier version could not be opened from the data flow landing page. Instead, a generic error screen was displayed and an NPE on activity pxMigrate was logged. This was caused by a missing null pointer check, and has been corrected.

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