SR-D62436 · Issue 527200
Datetime control with Display details readonly works with Edit input
Resolved in Pega Version 8.3.2
After upgrade, a date time control was being reformatted incorrectly when it was set with Display details as read-only with an Edit input rule configured on the property to convert the date entered (ex, 112019 to 01/01/2019). To resolve this, a data-editinput attribute has been added in the control markup to support this configuration.
SR-D64244 · Issue 532980
Support added for recording with sIngle-option radio button inside a repeating grid
Resolved in Pega Version 8.3.2
Recording a test case was not working when a single option radio button (i.e., radio button control with property of type boolean) was configured inside a repeating grid. In this case, it was found that the Radio button markup did not have a data-test-id attribute for non-template single option; this has been added.
SR-D64667 · Issue 531804
Cursor issue resolved for tab within expandable row
Resolved in Pega Version 8.3.2
When pressing the “Tab” key on an expanded row, the cursor was not moving inside the expanded part. This has been fixed by adding a check to get the correct first focusable element.
SR-D64694 · Issue 533960
Check added for Turkish locale in Firefox
Resolved in Pega Version 8.3.2
When using Firefox in the Turkish locale, attempting to open worklist subsets or edit tables in a modal dialogue caused the browser to hang. This was traced to the character conversion process in the browser and has been resolved with the addition of a check.
SR-D64945 · Issue 534321
Accessibility enhanced for multiselect
Resolved in Pega Version 8.3.2
Aria attributes for multiselect items and container have been added to enhance accessibility.
SR-D66095 · Issue 529705
Cross-site scripting security added to Richtext Editor
Resolved in Pega Version 8.3.2
A scenario where HTML objects could be copied and pasted into CKEditor and the click action modified to perform different actions was traced to Pega event attributes present in the Rich Text Editor content. This has been corrected by blacklisting Pega event attributes like data-click, etc. In
SR-D66387 · Issue 530841
ReloadSectionsCache handling improved
Resolved in Pega Version 8.3.2
Change Tracker was reporting changes properly and ExpressionEvaluator logic identified the correct DOM element related to layout refresh, but the refresh was not getting triggered due to _isInvalidRefresh logic. This was traced to reloadSectionsCache not being optimally maintained, and has been resolved by updating reloadSetionCache to avoid unnecessary reloads and only update the cache after a reload section is completed.
SR-D66436 · Issue 529670
Correct Value shown for Helper Text controls with labels
Resolved in Pega Version 8.3.2
Helper Text sourced from a field value was displaying the field value's 'Translate From' value rather than the 'Translate to' value. Analysis showed that the 'title' attribute of the corresponding icon on the DOM was being populated differently depending on whether it was a control with labels (not working) or a caption on a checkbox control (worked as expected). To address this, a check has been added for datetime and checkbox controls to send fieldname as pyCaption and pyActionPrompt respectively instead of pyTooltip to resolve the value.
SR-D67674 · Issue 537587
Check added to skip validationtype for disabled controls with Accessibility
Resolved in Pega Version 8.3.2
On enabling Accessibility, a disabled DateTime control was throwing a 'required' error. This was due to the dropdown markup having the validationType="required" attribute set if the control was configured with a required 'when' expression. Even though the expression evaluated as false, validationType="required" was still set. This issue was seen only in non-template datetime control, and has been corrected with a check to skip adding a validationType attribute for a disabled control in Accessibility mode.
SR-D68277 · Issue 541814
Added logoff check for requestors
Resolved in Pega Version 8.3.2
After upgrade, the error "java.lang.InterruptedException. Requester has been destroyed" was appearing in the logs. Investigation showed this was related to unregister requests being submitted after logoff, and has been resolved by updating the system to check for logout before sending unregister requests.