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-139095 · Issue 596508

Portal loads for Simplified Chinese locale in Microsoft Internet Explorer

Resolved in Pega Version 8.2.8

When using Microsoft Internet Explorer, the portal would not load when using the Simplified Chinese locale. This was caused by Microsoft Internet Explorer rendering the locale as 'zh-CN-#Hans' instead of the expected 'zh-cn'. This has been resolved by adding a check to remove the "#" in the locale string to avoid a malformed URL.

INC-139260 · Issue 592216

Handling added for third party form library

Resolved in Pega Version 8.2.8

When using a third party library which created a form tag, the wrong form was used on submit in the Ajax container. This has been resolved by updating the pzpega_ui_doc_submit file submitInner method to handle this use case.

INC-140289 · Issue 589001

Check added to preserve clipboard pages for pop-up

Resolved in Pega Version 8.2.8

Many properties were missing in the clipboard after launching an ImageViewer. This was traced to the clipboard pages being deleted in the pop-up mode, and has been resolved by adding a check to not delete pages in case of pop-up opened from top navigation case.

INC-142589 · Issue 595492

Corrected tooltip evaluation for multiselect

Resolved in Pega Version 8.2.8

After adding help text for a multiselect help icon with overlay on hover field, the value was not being sourced. Changing to a different type of help text or control type worked as expected. This was due to an error in case sensitivity, using pyToolTip when it should have been pyTooltip, and has been corrected.

INC-143260 · Issue 599304

Overlapping columns fixed in ReportViewer

Resolved in Pega Version 8.2.8

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-147794 · Issue 602702

Entity relation diagrams UI corrected

Resolved in Pega Version 8.2.8

After upgrade, attempting to create a campaign showed a blank page. This was traced to the Entity relationship diagram not loading, and has been resolved by adding a safe check.

SR-D91344 · Issue 560624

Resolved PageCannotBeSerializedForPassivationException in logs

Resolved in Pega Version 8.2.8

The exception "One or more properties could not be serialized during passivation and have therefore been lost. They will not be available on activation. Please ensure that all property data is Serializable" was observed in the logs. Investigation showed there was an HTML fragment in 'pzGridOpenAction' that was adding non-serializable properties to the clip board. This did not cause a functional issue, but has been resolved by modifying the way the system obtains and reuses the class definition.

SR-D96909 · Issue 558139

Removed extra scroll bar in Multiselect

Resolved in Pega Version 8.2.8

An extra scroll bar was appearing when opening the multi-select control case manager portal using the "Results displayed Maximum 500 results to display" setting. This was a result of recent updates to the popover scroll and height that caused on overflow condition. To resolve this, the logic for Multiselect has been updated.

INC-118918 · Issue 562155

Table Pagination elipses display properly for more than 10 pages

Resolved in Pega Version 8.4.2

When a table layout was configured with a report definition as the Data Source, the Pagination format in the grid header properly showed 'Page 1,2,3 ...' if there were fewer than 10 pages, but if there were more than 10 pages the '...' (elipses) were not appearing. This has been corrected.

INC-119669 · Issue 562589

Special character handling added to filters for table sourced with parameterized Report Definition

Resolved in Pega Version 8.4.2

Filters were not working on a table when sourced with a report definition which accepted a parameter value containing special characters (Eg: S&P). This has been resolved by using StringUtils.reversibleCrossScriptingFilter in the pzGetGridColUniqueValues activity to allow filters to contain special characters.

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