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 update your bookmarks. This site will be discontinued in Dec 2024.

Pega Platform Resolved Issues for 8.1 and newer are now available on the Support Center.

INC-196186 · Issue 725412

Check added for repeating dynamic layout submit context

Resolved in Pega Version 8.6.5

The postprocess of a local action was not executing when the local action was in a table that contained a repeating dynamic layout, and a null pointer exception was generated. Investigation determined that when a repeating dynamic layout was used inside a grid, the submit action on the layout was incorrectly happening in the context of the grid. To resolve this, a check has been added to determine whether the repeating dynamic layout is inside a grid so the correct context is used.

INC-198784 · Issue 697526

PD4ML upgraded

Resolved in Pega Version 8.6.5

Issues with PDF generation have been resolved by upgrading PD4ML to version 4.0.13.

INC-199137 · Issue 708165

PD4ML upgraded

Resolved in Pega Version 8.6.5

Issues with PDF generation have been resolved by upgrading PD4ML to version 4.0.13.

INC-205394 · Issue 706788

Hidden subprocess steps highlighted in screen flow navigation

Resolved in Pega Version 8.6.5

When a subflow was used as a last step within a screenflow and the subflow steps navigation links were hidden, the subprocess step was not highlighted as current. To correct this an update has been added that will highlight the circle on the navigation for a subprocess set as last step with substeps hidden, and the lines on the navigation step will be highlighted on the left side for a subprocess set as a step other than the last step and which has substeps hidden.

INC-206058 · Issue 709517

Property label correctly highlighted after validation failure

Resolved in Pega Version 8.6.5

The property label was not changing to red after validation failed. This has been resolved.

INC-208848 · Issue 720106

Cosmos landing page configuration icon updated

Resolved in Pega Version 8.6.5

In order to allow changing the Cosmos landing page configuration icon, the harness has been made available. The default icon has also been updated.

INC-210145 · Issue 710462

Added dirtycheck handling for case wide flow

Resolved in Pega Version 8.6.5

After opening an assignment and making some changes, clicking on the configured case wide flow process in the actions menu did not generate the expected pop-up window offering save/discard, resulting in the task being closed without knowing whether the changes were saved. This has been resolved by adding a call back functionality to handle dirtycheck for this scenario.

INC-211082 · Issue 717176

Updated default portal harness handling for switching applications

Resolved in Pega Version 8.6.5

After opening the user portal in a new browser tab through interaction with the search, a blank screen was presented when attempting to switch applications via the operator menu. Performing the same actions in the main / originally opened portal worked as expected. This has been resolved by creating a new section pyPortalNavigationHeader in pzPortalNavigation which has an action to open the harness which is available first in D_pzDynamicnavigationpages. This new section has been marked as available to allow local modification of the default harness for sites not using dynamic navigation.

INC-211743 · Issue 711669

PD4ML upgraded

Resolved in Pega Version 8.6.5

Issues with PDF generation have been resolved by upgrading PD4ML to version 4.0.13.

INC-211911 · Issue 713054

Able to expand rows when other rows are expanded

Resolved in Pega Version 8.6.5

When multiExpand, threadProcessing, and readonly flags were true, attempting to expand multiple rows at the same time collapsed already opened rows and generated an error indicating "target is not defined". This was caused by 'handleEditItem' not calling the collapse functionality for an opened row correctly, and has been resolved by adding a check which allows the expansion of multiple rows for readOnly details.

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