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-172944 · Issue 662828

Skin rule circumstancing article added

Resolved in Pega Version 8.6.4

An article on skin circumstancing best practices has been added to to aid in working with this functionality.

INC-176462 · Issue 657412

Dashboard widget drilldown section adjusts dynamically

Resolved in Pega Version 8.6.4

While trying to expand the drilldown columns, text was overlapping due to the grid not adjusting the large size of data dynamically. This was traced to an unnecessary CSS rule being applied to set max-height which broke the styling. This has been resolved by removing the height limitation on detail cells.

INC-180100 · Issue 662894

Scrollbar persists for multiselect

Resolved in Pega Version 8.6.4

Selecting more than 20 values in the multiselect control caused the scrollbar to disappear. This has been resolved by removing a custom popover height calculation.

INC-183672 · Issue 701868

Corrected vertical scroll bar for iPad Mashup page

Resolved in Pega Version 8.6.4

After update, the vertical scroll bar shown on the Web Mashup page in Apple Safari on iPad continued to increase and showed excessive blank space. This was caused by the iframes,section height being considered as the iframe height, and has been resolved by setting the section height as 'auto' in case of mashups.

INC-186081 · Issue 675207

Report filter popup displays correctly

Resolved in Pega Version 8.6.4

The filter popup was not displayed on the report column for which the filter was intended. This has been resolved by updating the popover js to fix the overlay issue.

INC-187196 · Issue 680749

Resolved Ajax popup alert for optimized iOS table

Resolved in Pega Version 8.6.4

When using an application on iOS with a section that contained at least 3 tables with 'optimize code allow' set to true, refreshing caused the error "AJAX request failed. Reason: communication failure" to be displayed. This has been resolved by adding an update which will skip the alert for the pzBuildFilterIcon activity when triggered from pzpega_ui_template_grid_helpers.

INC-188644 · Issue 708958

Autocomplete cancel closes correctly

Resolved in Pega Version 8.6.4

Clicking on an autocomplete field and navigating to the next tab without selecting any values caused the autocomplete results to be displayed in the next screen until there was a click or an action was performed in that screen. This was due to the autocomplete not closing correctly, and has been resolved by removing the event.cancelBubble setting.

INC-189748 · Issue 701457

Websocket disconnect code logged

Resolved in Pega Version 8.6.4

An update has been added which will log the websocket disconnect code for additional diagnostic information.

INC-190233 · Issue 675486

Production check removed for Get Action Details API

Resolved in Pega Version 8.6.4

After creating an assignment for a case and calling the Get Action Details Applied Assignment API, the name tag for views was not included in the returned JSON. This has been resolved by removing a check for production level.

INC-194415 · Issue 692825

Improvements for dirty popup

Resolved in Pega Version 8.6.4

Multiple issues have been addressed for dirty popups. 1) While working on an assignment, making a change and then clicking on the left navigation (Home, Dashboard) did not show the dirty pop up as expected, and the change was lost. The dirty pop up did appear on the Cancel button and Actions within the case. This has been resolved by improving the context switching for visibility of the dirty pop up. 2) Attempting to work around the previous issue by clicking "Do not display dirty warnings" only worked the first time it was tried. With this change in place, opening the assignment, making a change, then clicking Home, caused the pop up to appear as desired, but opening the assignment again and making a change, then clicking Home again did not prompt the dirty pop up. This was due to the click handler getting hit twice, leading to the already open dirty dialog being closed during the second call to the function 'isFormDirty' in pzpega_ui_doc_actionRouter.js file, and this has been resolved. 3) When attempting to close the case as a draft, clicking the save button caused the system to keep loading for a few minutes without sign of completing the save process and eventually the browser had to be closed. The content was saved, but the system was not able end the loading screen. This was caused by an incorrect harness context which caused the "SubmitInProgress" flag to be true on the incorrect harness context so the modal was not dismissed. To resolve this, on clicking the "Save" button, after the confirmation modal is closed, the pega.u.d.isDirtyDialogOpen will be reset to false.

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