SR-D56038 · Issue 518031
Corrected top row focus on scroll up for paginated table
Resolved in Pega Version 8.3.2
When loading results in a table with progressive pagination, scrolling down and waiting for data to load and then scrolling back up resulted in the focus being set on the second row instead of the first as expected. This was due to an incorrect calculation for Scrolltop, which has been corrected.
SR-D56723 · Issue 523836
Added check to resolve blank screen for embedded Ajax container with tabs
Resolved in Pega Version 8.3.2
When an Ajax container was within another section with a tab group, trying to open a perform harness resulted in a blank screen. This has been resolved by adding a check to ensure this.headers[this._active] exists before trying to retrieve variables from it.
SR-D57278 · Issue 519460
Padding added to keep sort icon always visible in Google Chrome
Resolved in Pega Version 8.3.2
When sorting a grid column on Google Chrome, the sort icon was missing if the header label was large. This was traced to the Sort icon being handled as a background image of 12px in width inside 'display:table-cell' which was forced to shrink by the resize. To resolve this, 'padding: 0 6px;' has been added to each side to keep the space intact for the sort icon to always be visible.
SR-D57629 · Issue 521727
Navigation sub menu shows all options
Resolved in Pega Version 8.3.2
The switch app menu was running off the bottom of the screen, and using arrow keys to navigate it caused the whole portal to jump up. This was traced to the sub-menu style attribute 'top' being changed to '0' if it was given a negative value. To resolve this, a condition was added to check whether the rendering sub-menu height is greater than viewport, and adjust the top attribute value accordingly.
SR-D57928 · Issue 526006
Special characters in field value display as expected
Resolved in Pega Version 8.3.2
After configuring a text input with a helper text (Help Icon with overlay on hover) that pointed to a Field Value, and the Field Value pointed to a property from the clipboard {.HelperText1} that had a value like (Some text here), in runtime the text in helper was printed with the HTML ASCII number and the text instead of the parentheses around the text. This has been resolved by escaping the special characters so they are displayed as expected.
SR-D58868 · Issue 531797
Check added for unicode calendar values
Resolved in Pega Version 8.3.2
After creating a repeating grid section for work report definition with enabled filter option, running the section and giving the filter value in unicode calendar form such as ２０１９／１１／１２ did not pass validation. This has been resolved by adding a check for unicode values
SR-D59003 · Issue 522035
Cross-site scripting security added to RWClasses
Resolved in Pega Version 8.3.2
Cross-site scripting protections have been added to the RWClasses parameter.
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.