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.

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.

INC-136264 · Issue 582469

Chatbot text starts scroll at top of answer

Resolved in Pega Version 8.2.8

In order to present an improved interface for customers interfacing with chatbots, the code has been updated so that the recipient's chat scroll will remain at the top of an answer that would scroll off the screen.

SR-D37487 · Issue 507206

Helper classes showing in the Helper Class Picker

Resolved in Pega Version 8.2.8

When opening the skin rule -> Actions -> Launch -> Skin Preview -> Helper class, the helper classes were not displayed in the picker. The helper classes were visible if they were manually entered in the Cell read-write classes or Cell read-only classes. Investigation showed that the was throwing a StackOverFlow exception while finding comments in the text file. To resolve this, the regex has been rewritten to not use alternation.

INC-125398 · Issue 564979

Updated handling for checkboxes configured in the header

Resolved in Pega Version 8.2.8

After configuring multiple checkboxes where each checkbox had a different property and different DT as action set and then using them as a single column header in the table, the on-change of any one checkbox caused all of the checkboxes to be checked or unchecked in the column header. This was caused by the pega.ui.grid.prototype.checkAllIfInHeader, which selects or unselects all checkboxes present in table (header +. body) based on checkbox status in header. However, the header row should not be part of the iterator during this function, and the necessary update has been made.

INC-126255 · Issue 580907

Resolved "maximum limit for pending changes" error

Resolved in Pega Version 8.2.8

When attempting to create a work object in a custom way using doCreateNewCase from the Smart investigate layer by using the RMButtonWithoughtWorkCaseNGP section, a popup showed the error “You have reached maximum limit for pending changes. Please commit/cancel one or more changes to continue.” The error did not occur when creating the case using the out-of-the-box Create New Work action. This was traced to the custom configuration creating work object threads that were not destroyed after the work item is closed. To resolve this, handling has been updated for passing dynamiccontainerID and contentID parameters for OpenWorkByURL case. Note that the pzUpdateActionInfo activity must be called in any custom activity before the actual activity is invoked.

INC-128970 · Issue 583291

Post value in grid works after clicking on modal submit

Resolved in Pega Version 8.2.8

The row submit on the grid of the modal dialogue worked when the value was updated and there was a click outside the grid. However, when the value was auto-populated, after clicking on the submit and going back to edit the value in the grid, the row submit did not work. Investigation showed that when a modal was submitted with some server errors, the system replaced the DOM and a new grid is initialized: since some of the listeners related to grid are attached to body, on submit of modal with server errors, these old listeners were getting fired. To resolve this, a safe check has been added for modalDetailsDiv before accessing it in event listeners.

INC-129278 · Issue 568856

Date range filter error resolved

Resolved in Pega Version 8.2.8

When using different locale settings, an "Invalid date" issue was seen when selecting a value for a date range filter. This has been resolved.

INC-129388 · Issue 571375

Check for mobile added to Pega Client for Windows time control

Resolved in Pega Version 8.2.8

When attempting to enter time using the out of the box time control in Pega Windows Client application, the control became stuck and continued to show on the UI even when screens were progressed. If the control was marked as a required field, this was a blocker. This was due to the 'validation_validateFromUIEvent' overlay invoking the 'pega.util.Event.getEvent()' function: this function was trying to get the events by traversing all the way to the event initialization, but the process was timing out on mobile/touchable devices and returning the parent event as undefined. Because 'pega.util.Event.getEvent()' was undefined, the validation_validateFromUIEvent caused js errors. To resolve this, a check for mobile has been added to the validation.

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