INC-169545 · Issue 649519
Localization updated for decimal slider
Resolved in Pega Version 8.7
When using the Indonesian locale, selecting the range on a slider which allowed selection of a decimal / double value that was then displayed in another textbox caused the value to increase incrementally and the slider always showed the end max. Investigation showed that this was caused by the handling of the comma decimal separator used in Indonesia, and has been resolved by updating the handling to ensure the slider value is converted to the respective locale.
INC-194239 · Issue 685736
JAWS reads characters limits in grid text area
Resolved in Pega Version 8.6.3
A text area in a grid with a character limit was not reading the maximum characters and remaining characters when using JAWS. This has been resolved by adding the necessary aria attributes to the non-template text area control.
INC-163644 · Issue 652968
Error message handling added for nested page lists
Resolved in Pega Version 8.7
When a multiselect referring pagelist(x).pagelist2() had an error message, the error was repeated for all pagelist(y).pagelist2() in the UI. This has been resolved by adding error handling for nested page lists by using registerErrorMessages for multiselect errors.
INC-197481 · Issue 695585
Accessibility improved for blank field errors in non-auto generated controls
Resolved in Pega Version 8.6.3
When using non-auto generated controls, leaving an edit field blank causes an error message informing that the value cannot be blank. An accessibility issue was seen where this error text was not part of the field label or description, preventing it from being announced by screen readers (NVDA or JAWS) when focus is on the field. This has been corrected by adding aria-describedby in non-template textarea.
INC-175990 · Issue 652089
Browser check added to ensure on-click event trigger
Resolved in Pega Version 8.7
Clicking Submit from the screen after opening the case from the worklist did not trigger the click event action when using Microsoft Internet Explorer 11. This was due to a change in that browser, and has been resolved by adding a check.
INC-197410 · Issue 690218
Handling added for invalid numeric range
Resolved in Pega Version 8.6.3
When filtering the range in number column with value as “1000000” , the validation message appeared as "1000000 : This results in an invalid numeric range". This has been resolved with an update to use Data-value to get the non-formatted value for decimal.
INC-182874 · Issue 675312
Update Language Pack for correct direct web access link localization
Resolved in Pega Version 8.6.3
When a direct web access (DWA) link was generated for an external user to perform an action on an external assignment, the shared link was corrupted when used with localization on the receiving system. This was due to the JSP fragment in the correspondence not being properly translated during localization. To resolve this, please access the most recent Language Pack available from https://community.pega.com/marketplace/language-packs/pega-platform .
INC-195321 · Issue 684972
Check added for readonly header control
Resolved in Pega Version 8.6.3
After configuring an optimized grid and adding a checkbox control in the header with editable options, when the control in corresponding column was configured as Auto, the checkbox in the header was rendered as read-only. When the control in the corresponding column was configured as "Read-only always" or displayText control was used, the checkbox was rendered as editable control. This was traced to a missing check for pyEditOptions = "Read-only", and has ben resolved.
INC-187617 · Issue 692544
Added API for Pega Call Team websocket reconnect
Resolved in Pega Version 8.6.3
When a call came in, the operator was not able to pick it up due to the popup only containing a reconnect section. This has been resolved by adding the disconnectAndReconnect API which will be used by Pega Call Team if the websocket reconnect limit exceeds 5.
INC-189748 · Issue 694739
Added API for Pega Call Team websocket reconnect
Resolved in Pega Version 8.6.3
When a call came in, the operator was not able to pick it up due to the popup only containing a reconnect section. This has been resolved by adding the disconnectAndReconnect API which will be used by Pega Call Team if the websocket reconnect limit exceeds 5.