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.

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". 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.

SR-C82408 · Issue 422327

Repaired instance insertion for REST connection invoked via Queue

Resolved in Pega Version 8.2.1

After upgrade, the REST connection invoked in an activity which in turn called OOTB ProcessQueue was not getting the response into the SYSTEM-QUEUE-EXECUTIONREQUEST-CONNECT-CREATEBOOKING instance. The right response was observed coming from other source systems in the logs, and the work object status also changing as expected. This has been resolved by exposing a DSS to revert to the old behavior of Response being present in the queueItem when a connector is queued for execution.

SR-C82480 · Issue 421487

Column Headers properly aligned after expand/collapse of Tree Grids

Resolved in Pega Version 8.2.1

When using a hierarchical table - tree grid with a configuration that included Width of content-Pixels(Fit Content), a Fixed (pixel) size grid, and Freeze Header, expanding and collapsing back the contents resulted in a misalignment of the column headers. The fixed header implementation makes use of multiple table layouts which have to kept in sync via javascript; this issue has been resolved by rewriting the fixed header implementation to call setHeadersWidth on expand/collapse of a treegrid row.

SR-C80129 · Issue 425386

Enhancement added to hide class join warning from end user

Resolved in Pega Version 8.2.1

An enhancement has been added to hide the joined class warning message at the end user portal if the section pzManageRecords is delegated to the user. This is done by by checking pxLimitedAccess on the pxThread clipboard page.

Ready to crush complexity?

Experience the benefits of Pega Community when you log in.

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