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.
INC-201372 · Issue 694015
Accessibility improvements for Cosmos Case Life Cycle
Resolved in Pega Version 8.6.3
Keyboard navigation has been updated to improve accessibility for the case life cycle component. For the "Show stages with expandable steps" configuration, code has been added to hide the steps container when tabbing through the stages. For the "Show stages with steps as overlay" configuration, the "Use form navigation (by tab)" option has been enabled for every repeating dynamic layer inside the steps overlay.
INC-201739 · Issue 694505
Switch from Pega base64 utility to java.util.Base64.getEncoder
Resolved in Pega Version 8.6.3
An on-premises Web Application Firewall (WAF) was interpreting the characters "%0a" in the Pega auto-generated URL as an "HTTP Response Splitting" attack. As a result communications were intercepted and a 403-error screen was shown. In addition, the characters %250A were interpreted as LF (line feed) or \n in the refreshFor hash generation. To resolve this, an update has been made to use java.util.Base64.getEncoder().encodeToString instead of the Pega base64 utility.
INC-201929 · Issue 692850
Removed incorrect field validation errors
Resolved in Pega Version 8.6.3
When integer controls in a section were configured as required field, clicking on the field but not entering any value resulted in the prompt for the required field validation "Value cannot be blank", and any attempts to add a positive integer using number keypad after that resulted in the repeated validation error. This has been resolved by updating pzpega_control_textinput.
INC-202218 · Issue 692877
Input from Microsoft Windows keyboard numpad enabled
Resolved in Pega Version 8.6.3
After entering a currency amount using the right side number pad keys on a Microsoft Windows keyboard, a mandatory field validation was being thrown on what appeared to be a correct input. This was due to an if condition in the keyup function that caused entries from the right side number keys to not be considered as input, and has been resolved by removing the condition from the pzpega_control_textinput file.