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-134893 · Issue 587170

Added check for localeDb properties in dateTimeUtils

Resolved in Pega Version 8.6

On click of the Approval/Finish assignment submit button, a blank screen appeared and no further progress could be made. This was traced to an issue with the operator locale not being properly set by the html fragments that initialize the locale for use in dateTimeUtils. This has been resolved by adding a check for properties in the localeDb object.

INC-135181 · Issue 597423

Clipboard handling updated to accommodate custom Cosmos portal

Resolved in Pega Version 8.6

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-135285 · Issue 586133

ProcessMerge activity handling updated for auto-populate

Resolved in Pega Version 8.6

If a flow action had auto populates and declaratives configured in it, merging back to pyWorkPage in the main page was not working correctly due to the method used for accessing the base page from the flow in a modal thread. This has been resolved by updating the handling for this process.

INC-135523 · Issue 590436

Tab panel read meaningfully by screen readers

Resolved in Pega Version 8.6

When the tabPanel received focus with accessibility, the entire tab content was read instead of the W3 standard of only reading "Edit ". This has been resolved by ensuring the Tabpanel has the proper aria-labelledby.

INC-135992 · Issue 595355

Corrected Windows attaching file to incorrect case

Resolved in Pega Version 8.6

When using Microsoft Internet Explorer with Windows 10, opening multiple cases in multiple browser tabs and switching between the different cases created a condition where a file might be attached to the wrong case. This has been addressed by updating pzHarnessInlineScripts.

INC-136057 · Issue 587165

Modal dialog close for date/time works as expected

Resolved in Pega Version 8.6

When a date/time property was used in a modal screenflow in Chrome, changing the date property on the pop up calendar and then clicking the modal close caused the screen to freeze. This was caused by the plf.handleModalClose() being called a second time for a container close event that was not available in window.event. This has been resolved.

INC-136563 · Issue 607419

Tenant Switching updated

Resolved in Pega Version 8.6

When working on new “tenant switching” implementations in a multi-tenant environment, the API itself seemed to be working as expected (case details from another tenant were shown correctly in review mode), but clicking on the assignment unexpectedly opened the case in a new window that contained the same review view of the case rather than the perform view. Clicking the assignment link again caused yet another review window to open with the same issue, over and over. This has been resolved by adding a UI-side update to send the requests on proper sub-domain URL instead of using the parent domain, and by ensuring the document threads are properly deleted for multitenant usecases.

INC-136659 · Issue 593768

Template circumstancing works for report definitions

Resolved in Pega Version 8.6

On circumstancing the pyMyCasesReport using the Template option, it always displayed the base report definition instead of the circumstanced one when referenced the same report in the table in section. Because the grid component called two activities 'pxRetrieveReportData' and 'pxRetrieveReportMetadata' to render the table, the step page passed to these activities was from @baseclass. This caused the circumstanced template created in work- class to not get picked up. To resolve this, updates have been made to ensure the step page to the above activities will be of the report definition class.

INC-136793 · Issue 585604

Updates made to display busy indicator correctly in Google Chrome 84

Resolved in Pega Version 8.6

The Pega busy indicator was not displaying correctly in Google Chrome 84 due to changes in that browser. The needed updates have been made to adjust for these changes.

INC-137100 · Issue 604058

Added predictive text handler for Japanese on iOS

Resolved in Pega Version 8.6

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.

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