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-142589 · Issue 595489

Corrected tooltip evaluation for multiselect

Resolved in Pega Version 8.4.3

After adding help text for a multiselect help icon with overlay on hover field, the value was not being sourced. Changing to a different type of help text or control type worked as expected. This was due to an error in case sensitivity, using pyToolTip when it should have been pyTooltip, and has been corrected.

INC-142714 · Issue 596554

Recent Cases from different applications available to open

Resolved in Pega Version 8.4.3

An enhancement has been added which will allow opening other application assignments in the Recent Cases section of the current application when the user has access to multiple applications.

INC-143005 · Issue 596954

Fluid Overlay displays as expected in Firefox

Resolved in Pega Version 8.4.3

After upgrade, using the Overlay format "Fluid" to perform the screening matches task in CLM using Firefox had an overlay that covered the entire screen but was missing the scrollbar to manage the content. This has been resolved by adding changes to support dynamic content (with scrollbar) for center overlay.

SR-A5412 · Issue 219159

Error marking fixed for TreeNavigation7 screen flow

Resolved in Pega Version 7.3.1

When using the TreeNavigation7 harness in the screen flow to call the validation from the post action, any property error in any of the flow-actions caused only the first flowaction to be marked as having an error while the rest were marked as successful. This has been fixed.

SR-B35942 · Issue 295191

Grid filter column localization fixed

Resolved in Pega Version 7.3.1

The repeating grid's column filter was not displaying the localized pyStatusLabel value. This has been fixed.

SR-B64971 · Issue 315219

Added alt text attribute to paperclip icon for accessibility

Resolved in Pega Version 7.3.1

A paperclip icon in the pzMultiDragDropControlStandard rule did not have alternative text, impacting its accessibility. An alt="" attribute has been added to the image tag to correct this.

SR-B51367 · Issue 311023

Resolved stack overflow for three level nested WO

Resolved in Pega Version 7.3.1

A StackOverflow exception was generated when using three levels of nested work objects due to a recursive looping of the parent pzInskey looking for its children. To fix this, the pyLoadMyCasesNested activity has been updated to set the RD based on whether a parameter sent to it is blank.

SR-B58009 · Issue 312838

Updated removeAssignment call for Assign- class

Resolved in Pega Version 7.3.1

After upgrade, some cases were becoming corrupted with the error "trying to calculate the handle of an instance may not be written to Database". This was traced to an unnecessary removeAssignment call to the ProCom flow library when work objects class is of Assign- ; this is old and has references to named pages like newAssignPage which may be empty. To correct this, the call to pega_procom_flow.RemoveAssignment has been replaced with pega_processengine_flowutilities.RemoveAssignment.

SR-B64353 · Issue 313990

Resolved assignment error when competing with SLA

Resolved in Pega Version 7.3.1

An Assignment error was occurring when the SLA competed with the user for an assignment. This was an error with setting the success indicator in the EstablishContext Activity, and has been fixed.

SR-B53049 · Issue 311589

SLA agent honors custom case type time-out

Resolved in Pega Version 7.3.1

Despite an assignment having a 3-hour lock period, the SLA agent was able to advance the assignment and remove access if the goal/deadline passed in less than that lock period. This was caused by a handling error where the order of steps led to not honoring custom timeout mentioned in the case type. This has been fixed.

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