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.

SR-D38729 · Issue 507031

Included section with defer load loads in modal flow

Resolved in Pega Version 8.2.4

An included section in a dynamic layout with 'defer load content' enabled was not loading in a modal window when it included a table sourced from Data Page which in turn called a Connect Soap to load the data. When the modal window was launched, it indicated it was loading text but did not actually load any data. When 'defer load' was unchecked, the data loaded as expected. In addition, the tab groups in the modal screen flow were not displayed. The same tab group did show when opened through a separate flow. This was traced to the data-harness-id not getting added to the flow in the modal case, and has been resolved by adding data-harness-id to the preRenderer in modalOverlay to handle modal flows.

SR-D40055 · Issue 507421

Work List loads as expected in Microsoft Internet Explorer

Resolved in Pega Version 8.2.4

After upgrade, the Work List was not loading in Microsoft Internet Explorer. This was an unintended side effect of work done to handle resizing the Recents list when another tab was open, and that change has been reverted to resolve this issue.

SR-D36176 · Issue 508406

Work List loads as expected in Microsoft Internet Explorer

Resolved in Pega Version 8.2.4

After upgrade, the Work List was not loading in Microsoft Internet Explorer. This was an unintended side effect of work done to handle resizing the Recents list when another tab was open, and that change has been reverted to resolve this issue.

SR-D40617 · Issue 507565

Escape added to Radio button field value to handle HTML tags

Resolved in Pega Version 8.2.4

A radio button with a field label to display a help icon and to open the help URL when the icon was clicked did not display as intended. Changing the control to text area produced the desired results. This was traced to the radio button's label being assigned to a field value which returned a string that at some points contained HTML tags, and has been resolved by escaping the pyLabelFor value before assigning it to the aria-label attribute of the radio button's div tag.

SR-D38946 · Issue 507906

Dragresize plugin removed from RTE for better Microsoft browser compatibility

Resolved in Pega Version 8.2.4

When a messge was sent through Pega chat while using the Edge web browser, the text field where the message was entered before the send button was pressed did not get cleared. This was traced to the Edge browser throwing a Permission Denied error while attempting to access a detached DOM element. To resolve this, the 'dragresize' plugin has been removed from RTE as its implementation is not compatible with Microsoft Internet Explorer 11 and Edge.

SR-D39455 · Issue 508605

Shortened URLs (bit.ly) supported with custom image size

Resolved in Pega Version 8.2.4

Marketing offers were very slow to load, often generating requestor lock exceptions due to the wait time. This was traced to one cell in one section that housed a company logo: the source to icon had a shortened "bit.ly" URL when the ImgaeIO API in Java expected the actual URL as its input. The API could not convert the shortened URL to the actual URL, resulting in the retries and connection failure. To resolve this, 'javax.imageio.ImageIO' invocation will happen only when the image size is auto. If custom height and width are used to display an image, Pega will not depend on the Java library and the system will be able to resolve the shortened URL.

SR-D42143 · Issue 509316

Tab names maintained after Ajax container refresh

Resolved in Pega Version 8.2.4

When using an Ajax container in Tabs mode, a browser refresh with multiple tabs opened caused the active tab name to be changed to the main tab name. This was caused by the work object name being lost during the refresh, and has been corrected.

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