SR-D60367 · Issue 534851
StretchTabsWidth performance improvements
Resolved in Pega Version 8.3.2
Slowness was seen when a new intent task was created through an interaction. To improve performance, some of the unnecessary calls to the Layout Group _updateStretchTabsWidth() function have been eliminated, and the function code has been updated to use native javascript performant helper functions so it starts rendering sooner. A flag has also been added to disable addnewtab and resizeactions: these need to be enabled through pega.u.d.DISABLE_LG_RESIZE and pega.u.d.DISABLE_ADDNEWTAB.
SR-D61122 · Issue 522496
Multi-select in drop down displays subset of a value
Resolved in Pega Version 8.3.2
In a multi-select drop down, choosing a value (say EMEA-Interior) and then choosing a subset of that value as the second choice (ex, Interior), the second value was not getting selected. If the selection was performed the other way around (Interior first and then EMEA-Interior), it worked as expected. Analysis showed that patterns with similar names did not have the necessary differentiation in the system, and a comma has been added to the generated ID to identify similar values in multiselect capsules.
SR-D62361 · Issue 534808
Read-Only harness takes precedence over editable section with when condition
Resolved in Pega Version 8.3.2
Given a harness which was marked as Read Only and contained sections which were configured as editable based on some conditions, when the condition became true, the section became editable and ignored the read only conditions applied on the harness. Investigation showed that when a read-only 'when' rule evaluated to false, it rendered the layout in Edit mode instead of falling back to the read-only status of parent. This has been corrected by ensuring that when read-only evaluates to false, the system will fall back to the parent read-only status.
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.