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-D55233 · Issue 520721

AJAX container handling updated to use Harness context API

Resolved in Pega Version 8.4

After creating a service case and adding a task to the case, a button configured to refresh the section on a condition worked correctly the first time but did not respond to a second click. This was traced to the tasks being located in two different Ajax containers: in this usecase the condition evaluation logic related to actions was still using the regular DOM API and using the context from the first AJAX container. To resolve this, the system has been updated to use the harness context API pega.ctx.dom.getElementsByName instead of DOM API to resolve the necessary elements from the correct AJAX container.

SR-D55461 · Issue 523176

Corrected modal timing issue when deleting Data Transform or Property rules

Resolved in Pega Version 8.4

When deleting Data Transform or Property rules, there were times when the deletion modal only appeared briefly and then the web page turned white, the message "No stream to display" appeared at the top of the web page, and all other content disappeared. This was more frequent when the requestor had been idle, but occurred under other situations as well. This was traced to a timing issue: once the modal action (localaction -modal or flowinmodal) is triggered the event queue should be paused, but in some cases the system was executing the next action in the queue and causing the no Stream to Display error. To resolve this, pega.u.d.bModalDialogOpen will be set to true in the prerender callback instead of success callback. This will set the flag in the pre-rendering logic so that correct modal status will be known to the action processor.

SR-D55972 · Issue 518645

SmartInfo disappears if cell clicked

Resolved in Pega Version 8.4

After configuring a smart info on a table cell on hover where the table cell was also clickable to open a case, the smart info remained on the screen when the cell was clicked until the mouse was moved. This was opposite of the expectation that the smart info would disappear on click in this scenario. Analysis showed that the overlay event was not being dismissed if its associated element was removed/hidden, and this has been corrected.

SR-D56038 · Issue 518033

Corrected top row focus on scroll up for paginated table

Resolved in Pega Version 8.4

When loading results in a table with progressive pagination, scrolling down and waiting for data to load and then scrolling back up resulted in the focus being set on the second row instead of the first as expected. This was due to an incorrect calculation for Scrolltop, which has been corrected.

SR-D56373 · Issue 518885

Mutiselect can localize "Use"

Resolved in Pega Version 8.4

Localization has been added for the value "Use" in the multiselect control.

SR-D56490 · Issue 518806

Resolved Sporadic ControlBuild error in sections

Resolved in Pega Version 8.4

After upgrade, a sporadic error was seen with sections of a VTable after a server restart where a portion would not load and the error "com.pegarules.generated.html_property.ra_stream_pxtextinput_1786000787_default incompatible with com.pega.pegarules.pub.runtime.ControlBuilder" was seen. This issue was traced to invalid generation of an assembly parameter map for random sections the first time the table was called after restart. To resolve this, the system will now allow assembly parameter generation for a second time when they are empty, and the assembly parameters preparation will be handled as a synchronous process.

SR-D56836 · Issue 518011

Includes() function changed for Microsoft Internet Explorer compatiblity

Resolved in Pega Version 8.4

The complete screen was not loading due to "includes()" not being supported in Microsoft Internet Explorer, resulting in a console error and the flow breaking. To resolve this, ".includes()" has been changed to indeOf.

SR-D57278 · Issue 519461

Padding added to keep sort icon always visible in Google Chrome

Resolved in Pega Version 8.4

When sorting a grid column on Google Chrome, the sort icon was missing if the header label was large. This was traced to the Sort icon being handled as a background image of 12px in width inside 'display:table-cell' which was forced to shrink by the resize. To resolve this, 'padding: 0 6px;' has been added to each side to keep the space intact for the sort icon to always be visible.

SR-D57629 · Issue 532493

Navigation sub menu shows all options

Resolved in Pega Version 8.4

The switch app menu was running off the bottom of the screen, and using arrow keys to navigate it caused the whole portal to jump up. This was traced to the sub-menu style attribute 'top' being changed to '0' if it was given a negative value. To resolve this, a condition was added to check whether the rendering sub-menu height is greater than viewport, and adjust the top attribute value accordingly.

SR-D61860 · Issue 523584

Preflight Optimization styling now handlies right-to-left language packs

Resolved in Pega Version 8.4

When using Preflight Optimization on a generated app with the AR (Arabic) locale, Pages rendered in Right-to-Left (RTL) mode did not have the proper styling or placement for the radio button target and text. The same app rendered correctly when using an empty (default to EN - English) locale. Investigation showed that Preflight Optimization of CSS was failing when using Right-to-Left (RTL) languagebecause the use of preflight bypassed all other CSS processing. To resolve this, the handling of Preflight's CSS Optimization has been updated to handle cases using a Right-to-Left language (ex: Arabic).

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