INC-167871 · Issue 666296
Desktop browser java render error corrected
Resolved in Pega Version 8.6.3
Attempting to open Clipboard, schedule a report, or perform any activity which generated in a pop-up resulted in a blank screen and browser errors indicating "Uncaught TypeError: (…) is not a function 2. Uncaught TypeError: cannot set property '...' of undefined". This has been resolved by adding a semicolon to the last line of pzpega_desktop_automation_support_js.
INC-176113 · Issue 661469
Duplicate messages removed from hover over smart info
Resolved in Pega Version 8.6.3
If a particular mandatory field was not selected and saved, scrolling over any help text bubble in that screen caused the error messages to pop up multiple times. This was an issue with the recreation of error tables on hover over smart info and has been corrected.
INC-178417 · Issue 670112
Flag reset added for grid with 'Expand When'
Resolved in Pega Version 8.6.3
A grid using an 'Expand When' condition worked as expected when the condition was true, but once expanded the grid did not collapse if the expand condition was changed to false even if a section/harness refresh was performed. This has been resolved by adding an update which will reset the flag when the result of 'Expand When' is false.
INC-178831 · Issue 680985
Ensured correct context for multi-select
Resolved in Pega Version 8.6.3
When using multi-select controls, there was an intermittent issue with selecting values using a mouse click. Using the tab key worked as expected. This was traced to the focus being event triggered multiple times so pega.ctx.dom returned undefined values in the second call.This has been resolved by focusing the target element before creation of capsule to ensure the context remains the same.
INC-180108 · Issue 667351
Desktop browser java render error corrected
Resolved in Pega Version 8.6.3
Attempting to open Clipboard, schedule a report, or perform any activity which generated in a pop-up resulted in a blank screen and browser errors indicating "Uncaught TypeError: (…) is not a function 2. Uncaught TypeError: cannot set property '...' of undefined". This has been resolved by adding a semicolon to the last line of pzpega_desktop_automation_support_js.
INC-180322 · Issue 684230
Cosmos collapsible summary panel works with hidden tabs
Resolved in Pega Version 8.6.3
The collapsible summary panel in Cosmos was not working correctly in combination with hidden tabs. This was due to the active tab index being created from the "data-lg-child-id" value which has a constant value for each tab and did not account for some tabs being hidden. To resolve this, the process for finding the "active" tab index is now based on the actual index instead of on the "data-lg-child-id" attribute.
INC-182287 · Issue 670742
Decimal places showing correctly after update
Resolved in Pega Version 8.6.3
After selecting Decimal places in the Property Panel in the section for a particular property, the decimal places were not added on tab-out at runtime. Decimal places were correctly applied if no property was specified. Investigation showed that an explicit post value call was initiated to apply the read-only formatting, but that call was suppressed by other conditions related to updating the Pega version. To resolve this, an unneeded data-auto-formatting conditional check has been removed.
INC-182724 · Issue 677845
Added empty space handling for tab labels
Resolved in Pega Version 8.6.3
After upgrade from Pega 6 to Pega 8, tab names were not displaying when rules were opened in Designer Studio. This was traced to empty space in the label which caused the Tab name to show as empty, and has been resolved by updating pzpega_ui_dynamiccontainer to use the trim method to check whether the label is empty or not.
INC-182726 · Issue 677531
CORS DSS settings corrected for Constellation
Resolved in Pega Version 8.6.3
After moving to the new HIPPA edition, the developer work area in Constellation appeared as blank under Channel-Portal-Landing Pages. This was traced to a DSS setting issue when using cross-origin resource sharing (CORS), and has been resolved.
INC-182803 · Issue 679725
SearchKeyword assed to HandleInput allow list
Resolved in Pega Version 8.6.3
After creating a section and placing a template grid with a button to refresh the section on click, clicking the button generated a SECU0001 alert. This was traced to gridMetadata_(uniqueID).pySearchKeyword not being registered when the property is part of a form data post request, and this has been resolved by adding pySearchKeyword to the allow list in HandleInput.java.