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-135992 · Issue 595353

Corrected Windows attaching file to incorrect case

Resolved in Pega Version 8.5.2

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-136563 · Issue 607418

Tenant Switching updated

Resolved in Pega Version 8.5.2

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 593767

Template circumstancing works for report definitions

Resolved in Pega Version 8.5.2

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-137100 · Issue 604057

Added predictive text handler for Japanese on iOS

Resolved in Pega Version 8.5.2

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-137510 · Issue 591293

CKEditor Source edit with formatting resumes process automatically

Resolved in Pega Version 8.5.2

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-137757 · Issue 600490

Primary page setting updated for micro DC container

Resolved in Pega Version 8.5.2

In Cosmos, a "Cannot Render Section" error displayed on submit of modal dialogue. This was caused by a primary page calculation error for the micro DC container, and has been corrected.

INC-137818 · Issue 594023

Corrected sorting icon accessibility when grid size is not fixed

Resolved in Pega Version 8.5.2

After configuring a table and checking the boxes for Filtering and Sorting and unchecking the fixed (pixel) size grid box, tabbing in to the grid/table using the keyboard did not bring the focus to the sorting icon /header, but instead the focus went to the filter icon. If filter was unchecked and sorting was checked, the focus went to the first row of the table. This was traced to the column headers missing the tabindex attribute when the column headers were not fixed. When the column headers were fixed, tabindex =0 was present for the column header and the sort icon was accessible. This was traced to the Freeze Header value not being updated according to Fixed Size value because it was not a fixed size grid. To resolve this, an extra condition has been added in GenerateCellContent Rule-Utility-Function to be used while checking the Freeze Header.

INC-137966 · Issue 597740

Embed-ReportFilter supports pyDateproperties

Resolved in Pega Version 8.5.2

After creating a report definition with Date time filter values where the 'from' date and 'to' date are input and propagated as “pyStartDateTime” and “pyEndDateTime” in the clipboard, opening the pyDate properties from clipboard resulted in a 'rule not found' exception. No properties of other data types generated the error. This has been resolved by creating the pyStartDateTime,pyEndDateTime and pyDisplayTimeperiod properties in Embed-ReportFilter to support this use.

INC-138309 · Issue 591148

Added busy state reset to reenable buttons after custom frame cancel

Resolved in Pega Version 8.5.2

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-138354 · Issue 594353

Third party cookies reminder added for Mashup in incognito browsers

Resolved in Pega Version 8.5.2

When working in incognito/private browser windows, attempting to use Mashup displayed a message indicating login credentials were not recognized ("Unknown password and/or username"). This was due to recent changes originating with the browsers regarding blocking third-party cookies which are necessary for Mashup to run. For informational purposes, a new API has been added which will check for the PegaRules cookie; if the cookie is not present, the message "Third party cookies must be enabled for Mashup to function." will be displayed. This message may be customized by configuring the setting "pega.web.config.xCookiesDisabled" with the required message.

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