INC-213262 · Issue 709457
Refresh added to limit commit log partition size
Resolved in Pega Version 8.6.4
Issues were seen on DDS nodes, including slowness and randomly dropping out and being replaced by new nodes. WARN messages in Cassandra logs reported issues relating to a large partition size of adm_response_commit_log_date_tiered table. Investigation showed the large partition size (over 10GB) was causing frequent C* query timeouts due to scanning a large number of tombstones, resulting in node terminations. This has been resolved with an update which will limit the commit log partition size by refreshing the NID every set interval.
INC-213945 · Issue 709365
Additional logging and executor work for Adaptive Decision Manager
Resolved in Pega Version 8.6.4
The Adaptive Decision Manager Pulse operation stopped running on some of the ADM nodes, causing an impact on the model update. To address this, some additional protections have been added for pulse operations running in a scheduled executor, and ERROR logging has been enabled.
INC-216894 · Issue 712241
Refresh added to limit commit log partition size
Resolved in Pega Version 8.6.4
Issues were seen on DDS nodes, including slowness and randomly dropping out and being replaced by new nodes. WARN messages in Cassandra logs reported issues relating to a large partition size of adm_response_commit_log_date_tiered table. Investigation showed the large partition size (over 10GB) was causing frequent C* query timeouts due to scanning a large number of tombstones, resulting in node terminations. This has been resolved with an update which will limit the commit log partition size by refreshing the NID every set interval.
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 https://collaborate.pega.com 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.