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-138309 · Issue 591150

Added busy state reset to reenable buttons after custom frame cancel

Resolved in Pega Version 8.3.5

When using a custom iFrame in a section that called a third-party URL, clicking on cancel for the popup "Do you want to stay on this page or leave it?" caused the screen to freeze. This was traced to the cancellation of the dirty page setting a busy state which disabled all the buttons and did not have a path to recovery. This has been resolved by updating the busy state so it will reset when the user chooses to cancel the changes and reenable all the buttons.

INC-137100 · Issue 605837

Added predictive text handler for Japanese on iOS

Resolved in Pega Version 8.3.5

The autocomplete function was not working well in MobileView when using Japanese IME on iOS. This has been resolved by adding a new input handler for IOS mobile, which will be triggered when predictive text is selected in mobile.

INC-142248 · Issue 601766

Added safe check for ActivateTabs

Resolved in Pega Version 8.3.5

After configuring a data transform action for a close icon to set a requestor level data page value and a parent-level dynamic layout was configured with a refresh when condition to track this Data page property, pzMicrodynamicContainer was throwing a null pointer exception after this refresh occurred indicating the tag name passed to isRegularTarget function was invalid. This has been resolved by adding a safe check to ensure that activateTabs is called only for tab based Ajax containers.

INC-138968 · Issue 594170

ARIA landmarks added to put dynamic layout in tab order

Resolved in Pega Version 8.3.5

As part of W3 accessibility specifications, ARIA landmarks have been added to dynamic layouts to direct tabbing focus. If the role type is "landmark" or "document", tabindex=-1 will be added, and for component widgets tabindex=0 will be added unless it is a non-focusable element like Alert, log etc.

INC-142141 · Issue 595676

Call to OnBeforeWindowClose changed to asynchronous

Resolved in Pega Version 8.3.5

After accepting a chat and accidentally closing the interaction portal with the active chat, the active record was left in an unresolved state that did not allow bot interaction until the 720 minute bot timeout was reached. This was caused by the pyOnBeforeWindowClose activity not being called as expected, and was traced to Google Chrome blocking the synchronous request needed. To resolve this, the call has been converted to an asynchronous request.

INC-137510 · Issue 591295

CKEditor Source edit with formatting resumes process automatically

Resolved in Pega Version 8.3.5

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.

INC-145119 · Issue 601712

Client side validation works with Reference page property

Resolved in Pega Version 8.3.5

A reference page property in a 'when' rule was not evaluating properly for checking a Date field when client side validation or Client side template UI was checked on the Harness level. This was traced to pyRequired being boolean: the boolean being compared to a string false value yielded a wrong comparison, leading to the wrong validation type required. To resolve this, the system will use the === comparator to compare boolean false in datetime to remove the required validator.

INC-135181 · Issue 597424

Clipboard handling updated to accommodate custom Cosmos portal

Resolved in Pega Version 8.3.5

After upgrading and moving to Theme-Cosmos, a browser-level refresh on the user portal was not remaining on the same screen that issued the refresh, but rather on the default screen of the user portal. This was traced to a difference in clipboard handling of the Body parameter value for strJSON that was exposed through a customized Cosmos User Portal where Ajax Container was not used but still present in DOM. In order to support this use case, the tab_support file in sendReqToUpdateClipboard method has been updated.

INC-139328 · Issue 589874

Corrected Excel table picture being included with rich text editor paste

Resolved in Pega Version 8.3.5

As an unintended consequence of code added to allow pasting or dragging and dropping an image for upload using rich text editor and the CK Editor, any copied content from Excel also added a table picture to the last cell as part of the pasted data. This has been resolved by updating the system to recognize content copied from Excel and prevent uploading of the image.

INC-145535 · Issue 600786

Corrected layout group overlapping content

Resolved in Pega Version 8.3.5

When an editable Table with Master Detail Edit has a section that contains a Layout group (Tab) inside the Master Detail Flow Action, if there are more layout group headings than that can be contained in the screen, a left and right arrow are displayed to toggle between headings in the layout group heading bar. However, timing issues sometimes caused the contents of the layout group to overlap on top of the content below the layout group and the screen was freezing with a loading icon. This was traced to console errors, and has been resolved by adding an 'undefined' check to prevent those errors.

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