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 note: beginning with the Pega Platform 8.7.4 Patch, the Resolved Issues have moved to the Support Center.

INC-125972 · Issue 604080

Improved resolved rules cache

Resolved in Pega Version 8.5.2

When Rule resolution iterated over a candidate list to fetch a candidate, performance issues were seen on very large sites. To resolve this, an enhancement has been added that will cache the resolved virtual table entries to optimize performance in high demand use cases like DSM.

INC-137775 · Issue 583784

Improved resolved rules cache

Resolved in Pega Version 8.5.2

When Rule resolution iterated over a candidate list to fetch a candidate, performance issues were seen on very large sites. To resolve this, an enhancement has been added that will cache the resolved virtual table entries to optimize performance in high demand use cases like DSM.

INC-146114 · Issue 604411

Create Survey routes case correctly

Resolved in Pega Version 8.5.2

The Create Survey utility was not routing the case to the user who initiated the case, but instead was routing it to the user who checked-in the case. This was traced to an error related to pxRequestor.pxUserIdentifier in the data transform pzpopulate survey params which is called when the survey utility is used, and has been corrected.

SR-D37444 · Issue 507037

WorkBasketGadget control updated for improved backwards compatibility

Resolved in Pega Version 8.3.1

After upgrade, the WorkBasketGadget Control was not retrieving the work queues. This was traced to a backwards compatibility issue introduced when greater security was put in place. The control WorkBasketGadget contains a call to pzEncryptURLActionString that was introduced in 8.x versions of the platform to encrypt URLs to avoid hijacking. The content of the URL relies on the pxRequestor.pxWorkGroup property, which is resolved using pega:reference tags. This approach was working in versions below 8.x, but these tags were not resolved at runtime. To correct this, requestorWorkGroup will be resolved as string and passed as a parameter instead of using pega:reference tags.

INC-142589 · Issue 595491

Corrected tooltip evaluation for multiselect

Resolved in Pega Version 8.5.2

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-128279 · Issue 591378

Layout Group tab alignment correctly shown in Microsoft Internet Explorer

Resolved in Pega Version 8.5.2

Even though the responsive breakpoint for a layout group was disabled, the tabs were getting changed to Menus in Microsoft Internet Explorer. This was traced to Tab-overflow being triggered in very small viewports when using Internet Explorer 11, and has been resolved by adding dom manipulations for all layout groups.

SR-D25012 · Issue 499851

Column filtering updated to better handle merged columns

Resolved in Pega Version 8.3.1

When filters were applied to a grid containing merged columns, the columns next to the merged columns did not have the filter class applied. This was traced to a calculation of the index in getFilteredColumnIndex function which did not consider the merge columns use case, and the uigrid js file has been updated to correct this issue.

INC-139023 · Issue 591163

Tab will exit portal side menu

Resolved in Pega Version 8.5.2

It is expected that the Tab key will take users out of the portal menu and to the next focusable element, but on the side navigation menu both tab and arrow keys moved to the next menu item. This caused users to have to navigate the entire menu. The correct behavior was seen for the Navigation rule when called from an Action (for example on the button). This was traced to the system using tabindex as "0" for every element in the menu, and the tabs code has been updated to exit out of the menu bar when pressed.

INC-137510 · Issue 591293

CKEditor Source edit with formatting resumes process automatically

Resolved in Pega Version 8.5.2

Buttons on the harness were freezing after applying format using CKEditor when source mode was turned on in rich-text editor. Investigation showed that on clicking the source button, after applying styles, the events were being paused and were not resumed automatically. This has been resolved by adding changes to resume the event queue.

SR-D25251 · Issue 493798

Added support for non-auto DisplayYesNo control

Resolved in Pega Version 8.3.1

A Change event on post value and refresh was not firing as expected in a section configured with a TrueFalse type property associated with a DisplayYesNo control. The same configuration worked correctly when used with a pxRadioButtons control. This was traced to non-auto control action JSON not generating on the second radio button(No) , and support has been added for this.

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