INC-198601 · Issue 695498
Autocomplete value retained post refresh
Resolved in Pega Version 8.6.3
After update, including an autocomplete control in the UI configured as 'on change refresh this section' resulted in the selected value getting removed from the list after being selected. Investigation showed this could happen in a customized environment if Selected Autocomplete and associated Autocomplete fields had Refresh section configured. While removing the refresh conditions resolved the condition, this has been addressed by adding handling for this use case.
INC-198958 · Issue 691676
Scroll bar appears consistently
Resolved in Pega Version 8.6.3
The scroll bar was not consistently appearing beside the menus containing vertical overflow. This has been resolved by setting the correct max-height on the menu all the time.
INC-199043 · Issue 697069
Preview link aligned under item
Resolved in Pega Version 8.6.3
The preview option was not showing below the link control configured to open the case, but instead was displayed elsewhere on the page. This was traced to changes made in Google Chrome v.93+, and has been corrected by changing the perspective to none instead of 0 so the link is displayed in the expected location.
INC-199496 · Issue 690006
Corrected quotation mark handling for multi select
Resolved in Pega Version 8.6.3
After defining a source for multi select where the selectable list contained double quoted text, for example: Testing for "Double Quotes", the double quotes were converted to single quotes in the selection list. This caused the value Testing for "Double Quotes" to be displayed as Testing for 'Double Quotes'. This has been corrected.
INC-199558 · Issue 693303
Updated calling activities from refresh to use invokeActivity
Resolved in Pega Version 8.6.3
The Refresh DX API was inconsistently throwing an index out of bound exception when using a checkbox which invokeed an activity on check to save and commit the case. This has been addressed by updating calling activities from refresh to use invokeActivity, and a try/catch has been added to capture exceptions and add a page message if the activity is not found or has an error.
INC-199625 · Issue 690722
Handling added for dropdown with duplicate option values
Resolved in Pega Version 8.6.3
When load behavior used "After screen renders" and dropdown options had duplicate values, a console error was observed and the UI became frozen. This has been resolved by adding handling for scenarios where the dropdown has duplicate option values.
INC-199817 · Issue 690109
Corrected decimal handling in integer control
Resolved in Pega Version 8.6.3
An integer property was accepting decimal values on screen and not throwing default integer validation errors. In addition, the place holders shown on the integer controls on the screen were decimal values. This has been resolved by restricting the decimal values for the integer control with integer property, modifying the code for restricting decimal values for integer field, and updating the code for showing the integer placeholder for integer field.
INC-199953 · Issue 695419
Updated Document-StateTracker reset
Resolved in Pega Version 8.6.3
An unexpected performance issue was seen after refreshing a case. This was traced to the Document-StateTracker taking longer than expected to reset from "busy" to "none", often reaching the 70 second max timeout setting, and has been resolved by calling setNavigationDone so that the document-statetracker dom element updates back to "none" immediately.
INC-199989 · Issue 692578
Flow action modal pop-up closes after submit
Resolved in Pega Version 8.6.3
On clicking Submit button on the modal window, the post action was successfully completed but the buttons froze and the modal window did not close. This was traced to a missing condition in the if loop to handle the needed flow action logic, and has been corrected.
INC-200952 · Issue 691209
Added check for page current index before refetching
Resolved in Pega Version 8.6.3
When using Refresh in a table, the error "The page index "-1" specified for this RDB call is invalid; it is not zero or a positive integer" was generated. This was caused by updateFilteringState modifying the pyCurrentPageIndex value for refetching even though refetching is not required if pyCurrentPageIndex is already 1, and has been resolved by adding a check for page current index and only refetching if it does not equal 1.