SR-D55781 · Issue 523204
Corrected Microsoft Internet Explorer 11 view for Data-Corr-Letter attachments
Resolved in Pega Version 8.2.6
When opening an attachment of type “Data-Corr-Letter”, the document showed correctly in Google Chrome but in Microsoft Internet Explorer 11 was displayed in a small frame that did not allow viewing the entire content. This was traced to a legacy HTML rule with an IE8 emulation meta tag to support OCX, and has been resolved by adding a 'when' condition for the meta tag.
SR-D55972 · Issue 518644
SmartInfo disappears if cell clicked
Resolved in Pega Version 8.2.6
After configuring a smart info on a table cell on hover where the table cell was also clickable to open a case, the smart info remained on the screen when the cell was clicked until the mouse was moved. This was opposite of the expectation that the smart info would disappear on click in this scenario. Analysis showed that the overlay event was not being dismissed if its associated element was removed/hidden, and this has been corrected.
SR-D56038 · Issue 518032
Corrected top row focus on scroll up for paginated table
Resolved in Pega Version 8.2.6
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-D56373 · Issue 518884
Mutiselect can localize "Use"
Resolved in Pega Version 8.2.6
Localization has been added for the value "Use" in the multiselect control.
SR-D56723 · Issue 523837
Added check to resolve blank screen for embedded Ajax container with tabs
Resolved in Pega Version 8.2.6
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-D56953 · Issue 523475
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-D57164 · Issue 531134
Multi Select Control panel search by word fixed for Microsoft Internet Explorer
Resolved in Pega Version 8.2.6
Multiselect search by word functionality was not working in Microsoft Internet Explorer 11: clicking on the down arrow resulted in the selection panel opening up for 1 or 2 seconds and then disappearing. It is working fine in chrome. Investigation showed that focushandler was getting called after popover open, which caused it to hide. The multiselect search worked in Google Chrome because in that case focushandler was called first and then popover was opened. The issue with Microsoft Internet Explorer has been resolved by updating the event handling.
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.