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-179664 · Issue 661109

Child Case comments pop-up opens as expected

Resolved in Pega Version 8.7

Comments on the header level were opening correctly, but the comments pop-up for the child case tab was not. This has been resolved by adding a safe check for the eventTarget.closest method.

INC-179683 · Issue 664452

Handling added for decoding file names containing umlauts

Resolved in Pega Version 8.7

Two issues were seen with file names that contained an umlaut: When sending file with an umlaut in the name via PegaCHAT, the error "Failed to load resource: the server responded with a status of 404 (404)" appeared on the Client side and a preview was generated. On the Agent side, the message was sent but attempting to open it resulted in an error that the file did not exist. This was traced to the unescape javascript API returning the wrong decoded values if the encoded value of an umlaut character was sent, and has been resolved by adding a safe check to avoid a malformed URI. Second, an image was not displayed in the Rich Text Editor if the image name contained the ä or Ä character in it. Investigation showed the activity parameters were being changed when it was invoked from the script. If the file name sent was "aysnÄ1626292145235.png" it was encoded to "aysn%C3%841626292145235.png" as expected, but when the parameter was passed to the Activity the value further changed to "aysn%C3%83%C2%841626292145235.png", causing the file open failure because the names did not match. To resolve this, code has been added which will correctly decode the encoded values of umlaut characters.

INC-179752 · Issue 659880

Web Mashup works from nested iframe

Resolved in Pega Version 8.7

Web Mashup was failing with the error "Browser cookies must be enabled for PRPC Internet Application Composer to function" when it was configured within a nested iframe setup. This has been resolved by adding a cookie check and the appropriate handling for this usecase.

INC-179883 · Issue 661616

Pega reference tags persist

Resolved in Pega Version 8.7

Cross-site scripting protections have been updated to allow Pega reference tags.

INC-180108 · Issue 667352

Desktop browser java render error corrected

Resolved in Pega Version 8.7

Attempting to open Clipboard, schedule a report, or perform any activity which generated in a pop-up resulted in a blank screen and browser errors indicating "Uncaught TypeError: (…) is not a function 2. Uncaught TypeError: cannot set property '...' of undefined". This has been resolved by adding a semicolon to the last line of pzpega_desktop_automation_support_js.

INC-180275 · Issue 666456

Collaboration control hidden if data type is delegated

Resolved in Pega Version 8.7

When collaborating using a customized CaseManager portal with some delegated data types, the admin user refreshing the Data Type view changed the collaborator's view from the portal to show the Data Type tabs, allowing the second person to open rules (properties, Data Pages, etc) and see the configuration even though they could not make any changes. This has been resolved by updating pzDataTypeDelegated to display the collaboration control only if pzDelegation is false.

INC-180322 · Issue 670118

Cosmos collapsible summary panel works with hidden tabs

Resolved in Pega Version 8.7

The collapsible summary panel in Cosmos was not working correctly in combination with hidden tabs. This was due to the active tab index being created from the "data-lg-child-id" value which has a constant value for each tab and did not account for some tabs being hidden. To resolve this, the process for finding the "active" tab index is now based on the actual index instead of on the "data-lg-child-id" attribute.

INC-180482 · Issue 661513

Browser compatibility update for setActivityAction

Resolved in Pega Version 8.7

After update, the Parameter Configuration popup was blank when using Microsoft Internet Explorer. This was traced to security updates that utilized the SafeURL.prototype.setActivityAction containing the startsWith API which is not supported by Internet Explorer. To resolve this, startsWith has been replaced with indexOf for cross-browser compatibility.

INC-180712 · Issue 664784

Improved accessibility for utility pane

Resolved in Pega Version 8.7

Accessibility issues with Autocomplete Role have been resolved by adding role = "combobox" for autocomplete in template mode.

INC-181089 · Issue 667655

Corrected modal focus on assignment open

Resolved in Pega Version 8.7

After opening an assignment and using keyboard navigation, the focus was not set on the first focusable element as expected. Hitting "TAB" set focus to the second focusable element. This was traced to previous work done on focusing elements under the modal, and this has been resolved by removing the "document.activeElement.blur()" as it is no longer needed.

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