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 update your bookmarks. This site will be discontinued in Dec 2024.

Pega Platform Resolved Issues for 8.1 and newer are now available on the Support Center.

SR-C82530 · Issue 420609

Atmosphere XSS Vulnerability fixed

Resolved in Pega Version 8.1.3

Atmosphere has been updated to close a potential XSS vunerability.

SR-C83808 · Issue 421299

FIRST aggregate in bucketed window fixed

Resolved in Pega Version 8.1.3

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-C83915 · Issue 421169

Enhancement added to support property reference name for section include

Resolved in Pega Version 8.1.3

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-C85035 · Issue 421948

Added getIfPresent check for Field Value parameters with pzAPICreateJsonForView

Resolved in Pega Version 8.1.3

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-117083 · Issue 176581

Added sorting and filtering to work item AssignedTo and Status fields

Resolved in Pega Version 7.1.9

An enhancement has been added to allow for filtering and sorting the list of assignments at the bottom of a work item by the 'Assigned To' and 'Status' fields.

SR-128383 · Issue 193256

Child class assignments carried for bulk processing

Resolved in Pega Version 7.1.9

While processing the assignments from the Bulk Actions, the class of the parent work object was applied to child class assignments. This generated a 'Flow Action not found' error. This has been corrected so when the flow action sets a property value, it is setting the value at pyWorkPage instead of the page list item while processing the Child class assignments.

SR-130216 · Issue 202688

AssignActions modified to correctly ResumeFlow from sub-user

Resolved in Pega Version 7.1.9

If two flow actions were defined on a particular assignment in a flow that used WHEN rules to affect visibility in a sub-user's workflow, ResumeFlow was not correctly picking up the flow after the sub-user performed an action and closed the workflow. This was caused by the AssignActions state persisting instead of repopulating and continuing the flow, and the RUF 'FindAssignment2' has been modified to handle this correctly.

SR-132494 · Issue 201073

Exposed 'style' parameters for Workbasket and Operator dropdowns

Resolved in Pega Version 7.1.9

The ShowAllOperators and WorkBasketGadget out-of-the-box controls defaulted to in-line styles even when alternate styles were provided. To correct this, 'style' is now an exposed parameter for both Workbasket and Operator dropdowns.

SR-132896 · Issue 202844

Added handling for customized flows using "different work item" subprocess

Resolved in Pega Version 7.1.9

After upgrade, customized flows using the "different work item" choice on the subprocess for calling work flow from embedded data page work objects generated the error "'On Another Work Item' was specified yet the same object was supplied." This was traced to a missing pzInsKey for this use case, and the LaunchFlow RUF has been updated to handle this customization.

SR-133048 · Issue 202946

Enhancement added to filter list of bulk processing operators

Resolved in Pega Version 7.1.9

When opening Case Manger portal > Open bulk Actions, selecting the Filter condition as 'Assigned To Operator' showed all operators in the autocomplete list. An enhancement has been added to create the extension activity 'pyGetListOfOperators' for RD which can be updated as per the user requirement to filter the list of operators to be shown in the Bulk Processing Search.

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