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-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.

INC-214222 · Issue 719322

Confirmation message correctly displays

Resolved in Pega Version 8.6.5

Two issues were seen with inconsistent display of the confirmation message. In one instance, after an assignment was finished the Review harness was appearing instead of Confirm harness and no confirmation message was displayed. In the second instance, after creating a case and moving to the next stage, coming back to the previous stage did not show the confirmation message. These issues were traced to the Ajax container primary getting closed before refreshing the section pyCaseMainPageNotification, causing the harness context issue as well as the failed conditional parameter strPHarnessPurpose issue which caused the message to not display. These have been resolved.

INC-214338 · Issue 712498

Navigation updated for checkbox control in table cell

Resolved in Pega Version 8.6.5

Keyboard-only navigation was not working correctly when there was a checkbox control in a table cell. This was traced to the manageFocus function in the pega_ui_templatizedGridComponent js file which was setting the tab index to -1 when the checkbox value was updated. This has been resolved by skipping the execution of this function for checkbox control to handle the case when escape is not pressed before tabbing to come out of the table when there is a checkbox control in a cell.

INC-214809 · Issue 719135

Confirmation message correctly displays

Resolved in Pega Version 8.6.5

Two issues were seen with inconsistent display of the confirmation message. In one instance, after an assignment was finished the Review harness was appearing instead of Confirm harness and no confirmation message was displayed. In the second instance, after creating a case and moving to the next stage, coming back to the previous stage did not show the confirmation message. These issues were traced to the Ajax container primary getting closed before refreshing the section pyCaseMainPageNotification, causing the harness context issue as well as the failed conditional parameter strPHarnessPurpose issue which caused the message to not display. These have been resolved.

INC-215046 · Issue 714674

Deleting case in create stage returns user to home/Dashboard

Resolved in Pega Version 8.6.5

When using a multi-step form in Create Stage, performing a Cancel + Save&Close, then re-opening the case and using a Cancel + Delete, the result of the cancelation is not shown and the user is not returned to the Home/Dashboard screen. This was caused by an issue where the specific AJAX container was not closed, and has been resolved by modifying the pyCaseActionAreaButtons to execute the pyCloseCase local action when clicked to close the case.

INC-215215 · Issue 713856

Validations fire on collapsed accordion layouts

Resolved in Pega Version 8.6.5

Client validation was not firing on the selected tab of a layout group if the accordion layout was collapsed. If focus was switched to the second tab, the client validation on the first collapsed tab did not work. This has been resolved by modifying the 'else if' condition to pass the validation for the fields places in layout group tabs.

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