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.

SR-D84364 · Issue 551403

Check for circular references added to SearchInventoryImpl to prevent recursive call

Resolved in Pega Version 8.4.2

An out of memory error was traced to SearchInventoryImpl infinitely recursing over a clipboard property, where the child property referenced a parent property and resulted in an endless loop. This has been resolved with the addition of a depth check to ensure that the search does not recurse infinitely.

SR-D85100 · Issue 556262

ProductInfoReader updated to fetch only most recent version information

Resolved in Pega Version 8.4.2

After upgrade, running Hfix scanner on Pega Marketing 8.2 displayed missed critical Hfixes for Pega Marketing 8.1. This has been resolved by modifying ProductInfoReader.runQuery to fetch only latest version of DAPF instances during a scan.

SR-D98404 · Issue 558207

Handling added for hotfix Rule-Application instances

Resolved in Pega Version 8.4.2

A null pointer error during DL file expansion performed as part of the second phase of a hotfix installation caused the hotfix install to fail. The null-pointer exception was thrown because the code, primarily used for export, performed a database lookup of a Rule-Application and assumed the response would be non-null without checking the result. During export the Rule-Application would normally exist because the system would have interacted with it already during the export by identifying it and writing it to the archive. During phased hotfix installation, rules are staged to the database in a different table during the first phase and reconstituted during the second phase. The scenario for this error was a missed corner case specific to the unusual combination of including Rule-Application instances in a platform hotfix. To resolve this and prevent further issues, handling has been added for this use case.

SR-D83027 · Issue 548584

Resolved Microsoft Internet Explorer 11 custom dropdown issue

Resolved in Pega Version 8.4.2

Microsoft Internet Explorer 11 was not consistently opening the dropdown when the dropdown format in skin used a custom state for hover,focus and active. This has been resolved by making the styles that are present in the mobile controls CSS file available to skin configuration.

SR-D86694 · Issue 548670

TeamMembersWidget section include corrected for PortalNav

Resolved in Pega Version 8.4.2

An error was seen when attempting to include the pyTeamMembersWidget section inside a pyPortalNav section. Investigation showed there was a data corruption in the section. As a local change, it was possible to 'save as' the section to a ruleset and delete the section embedded in the grid, then drag an embedded section layout from Layouts, add it to the grid row, and select pyTeamMembersWidgetRow. As a permanenet resolution, the corrupted section has now been replaced.

SR-D87991 · Issue 558973

Support added for Ajax container refreshCaseSections

Resolved in Pega Version 8.4.2

The Refresh/Visibility Condition in Dynamic Layout was not working in the Interaction portal, but did work in a Stand alone service case. This resulted in the summary area not being refreshed when a case was opened in a new tab, which is a new feature supported in Cosmos, leading to a post value used in the case processing area to not be present in the Summary panel on blur of the input field. This was due to the use of the new Ajax container, which did not yet have support for all the out-of-the-box actions such as Refresh-Section or Refresh-Condition. That support has now been added by way of the javascript API pega.u.d.refreshCaseSections.

SR-D90284 · Issue 551474

Added 'when' condition to class change in ShowColorPicker activity

Resolved in Pega Version 8.4.2

When using an included color picker control in a section, selecting a color resulted in the color picker pyworkpage class content changing to Embed-Skin-Controls. This has been resolved by modifying the previous behavior of always changing pyWorkPage's obj class as part of the ShowColorPicker activity by adding a 'when' condition to change the class only if it is empty.

SR-D93564 · Issue 557262

Corrected screenflow CSS precedence

Resolved in Pega Version 8.4.2

After upgrade, the screen flow navigation chevrons were not displaying correctly due to the screenflows CSS styling not taking the correct precedence in the markups. This has been resolved.

SR-D96061 · Issue 562601

Localization added for "Preview"

Resolved in Pega Version 8.4.2

Support has been added for localizing the text "Preview".

SR-D98614 · Issue 559863

Parent and child case links resolved for Cosmos

Resolved in Pega Version 8.4.2

After upgrade to v8.4, a behavior change was seen in creating a child case (Add Work) from a Parent case when using an application built on the Cosmos theme. Items such as pyWorkCover Page and CoveredInsKeys were missing, Data Propagation from the parent case to the child case was not working, the Child case max Instance configuration was not being applied, and when the child case was created from Add work, the child case appeared in an unexpected popup. This was traced to work done to implement a feature of creating subcases in a dialog (using a tertiary AJAX container) which was missing handling for a target parameter used for the child case clipboard, and has been resolved.

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