SR-D57358 · Issue 519791
Scrollbar added to dynamic content overlay
Resolved in Pega Version 8.2.6
An enhancement has been added to support dynamic content in overlay with a scrollbar.
SR-D57928 · Issue 526008
Special characters in field value display as expected
Resolved in Pega Version 8.2.6
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-D58779 · Issue 524348
Mashup will not load automation scripts
Resolved in Pega Version 8.2.6
After creating a mashup with Portal Type harness where a header menu item controlled navigation to each tab, loading different harnesses did not work using Ajax/Dynamic containers due to access denied / cross origin errors. This was traced to the use of pz_pega_ui_automation_scripts, which should not directly access the window.top or window.parent object because mashup provides a gateway-less implementation that leverages PostMessage browser API. This has been resolved by adding a 'when' condition in the pzHarnessStaticScripts HTML fragment rule to not load the automation scripts in this scenario.
SR-D58868 · Issue 531799
Check added for unicode calendar values
Resolved in Pega Version 8.2.6
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 522037
Cross-site scripting security added to RWClasses
Resolved in Pega Version 8.2.6
Cross-site scripting protections have been added to the RWClasses parameter.
SR-D60367 · Issue 534852
StretchTabsWidth performance improvements
Resolved in Pega Version 8.2.6
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 522497
Multi-select in drop down displays subset of a value
Resolved in Pega Version 8.2.6
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 534809
Read-Only harness takes precedence over editable section with when condition
Resolved in Pega Version 8.2.6
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 527201
Datetime control with Display details readonly works with Edit input
Resolved in Pega Version 8.2.6
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-D63416 · Issue 526522
Multi-select list control properly sets error message for server-side validation
Resolved in Pega Version 8.2.6
When using the Multi-select list control, client-side validation was working as expected but server-side validation was creating the Property-Set-Message error at Form level rather than Field level. This has been corrected.