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.

INC-163596 · Issue 636235

Checkboxes receive correct focus with accessibility

Resolved in Pega Version 8.6

It was necessary to click the tab twice in order to check the checkbox in the filter popup. This has been corrected by adding a check in the firstfocuselement method so the focus is placed correctly over input type elements.

INC-163651 · Issue 636900

Cancel button in offline works as expected

Resolved in Pega Version 8.6

When using the mobile app offline, clicking 'cancel' after creating a new case did not remove the case, but instead returned to the review screen. This was traced to the logic used to evaluate the conditions, and has been resolved so that the 'cancel' button will return to the worklist if offline, or display save/delete options when in the create stage of the online app.

INC-164311 · Issue 635785

Correct datetime target property used

Resolved in Pega Version 8.6

When using a declare expression for a datetime property to get its value from another datetime property, attempting to change the source datetime later resulted in the error "28-mar-2021 is not a valid date/time value". This occurred when the source datetime property had display readonly formatting, and was traced to the formatted value being sent in the callGetTargets API instead of the selected date value, which caused the function to be returned as empty because there was no target property in the same page before submission. To correct this, a check has been added which will get the value from data-value instead of element.value and will skip callGettragets if the target is empty.

INC-169907 · Issue 648484

Handling added for element outside viewport in overlay

Resolved in Pega Version 8.6

The left attribute from overlay styles was changing from "0" to a negative value (dynamically depending on screen size) while scrolling the results up and down. This caused issues such as attempting to view the duplicate case analysis screen or having the tool tip move to the extreme left when hovering the mouse on a link and scrolling. This was traced to an overlay launched from a table: if client.left was zero, the overlay left was given a negative value which causes the overlay to be shifted towards left side of the screen. To resolve this, an extra condition has been added to check if the associated element is outside the viewport when an overlay is launched from a table, and if so apply a flippedX value for left property.

SR-69015 · Issue 619995

Unescaping characters implemented for expressions

Resolved in Pega Version 8.3.6, Resolved in Pega Version 8.4.4, Resolved in Pega Version 8.5.3, Resolved in Pega Version 8.6

An issue where expression builder statements were evaluated differently at runtime than at testing has been resolved. Pega Platform expressions with String literals(that is, sequences of characters enclosed in quotation marks) now unescape characters in strategy shapes such as Set Property or Filter.

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.

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