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.

INC-120299 · Issue 578183

Added null check to ActivityStatusExceptionHandler

Resolved in Pega Version 8.5.2

Invalid Parameter Exceptions were being logged in the production environment related to an 'CPMInteractionPortalWorkArea' execution error on page 'pyTmpDisplayHarness' indicating "Invalid value for aReference passed to, char)". This has been resolved by adding a null check before reading the DC data model in the activity ActivityStatusExceptionHandler.

INC-128279 · Issue 591378

Layout Group tab alignment correctly shown in Microsoft Internet Explorer

Resolved in Pega Version 8.5.2

Even though the responsive breakpoint for a layout group was disabled, the tabs were getting changed to Menus in Microsoft Internet Explorer. This was traced to Tab-overflow being triggered in very small viewports when using Internet Explorer 11, and has been resolved by adding dom manipulations for all layout groups.

INC-132176 · Issue 588809

Cache cleared before PDF generation to ensure proper fonts

Resolved in Pega Version 8.5.2

The font File OCRAEXT.ttf added at location "/usr/local/tomcat/fonts" was not being picked when the PDF was generated via an agent execution. When the same activity was run manually, the font issue was sporadic. Investigation showed that when multiple apps use the same props directory but different fonts directories, the handling would sometimes cause one app to use another app's props file with the result of the improper fonts mapping. To resolve this, an update has been made to clear the cache before PDF generation starts to ensure the library reads the proper fonts.

INC-132219 · Issue 580266

Values with accent characters are sorted properly

Resolved in Pega Version 8.5.2

Table Layout column values using a pagelist were not sorted properly when the data contained French accent characters. This has been resolved.

INC-132569 · Issue 595174

Resolved case detail overwrite

Resolved in Pega Version 8.5.2

In the interaction portal, when the same property (dropdown) was used to populate the details of sections in two cases, the first section (email case) details were replaced by the second section (outbound call case) details. Investigation showed that the refresh API was getting the reloadElement in the entire DOM based on the event target name property. To resolve this, updates have been made to use context DOM APIs to get the correct section.

INC-133576 · Issue 590325

Expandable Grid behavior corrected

Resolved in Pega Version 8.5.2

Expanding any row in master details was collapsing a previously expanded row. This has been corrected.

INC-133978 · Issue 587698

Overlapping columns fixed in ReportViewer

Resolved in Pega Version 8.5.2

When Report Viewer was used for Report Definition, displaying it on dashboard columns resulted in columns that overlapped each other. This was traced to a resize issue related to the scrolling checkbox and has been resolved.

INC-135181 · Issue 597425

Clipboard handling updated to accommodate custom Cosmos portal

Resolved in Pega Version 8.5.2

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-135195 · Issue 598071

PD4ML library updated

Resolved in Pega Version 8.5.2

When generating a PDF from a report definition with more than 1000 records, the system would hang abruptly and stop responding. There was also a noticeable size difference in the generated file. This was an issue with the included version of PD4ML, and has been resolved by updating the version from 4.0.6 to 4.0.9fx1.

INC-135405 · Issue 582004

Simple button style updated to allow customization

Resolved in Pega Version 8.5.2

The Simple button style was not picking up the correct border style that was defined in the Skin rule when in the hover state. This was traced to the border radius value hard-coded in one of the custom files taking precedence over the value added for the border radius in the skin format. To resolve this, the simple button styles code has been removed from the controls.css file that had the border radius value hardcoded. The styles for simple button format will be configured in the skin, and a mixin has been added for modal buttons border styles that can be configured in the skin itself.

We'd prefer it if you saw us at our best. is not optimized for Internet Explorer. For the optimal experience, please use:

Close Deprecation Notice
Contact us