SR-D45101 · Issue 512528
Added support for Helper Text Question Mark with visibility condition
Resolved in Pega Version 8.2.6
The Helper Text Question Mark was not displaying if the control was configured with "Help icon with overlay on hover" combined with a visibility condition. This was a missed use case, and the expression visibility support for controls.changes have now been added in the pzpega_ui_DLCellTemplate.js file.
SR-D47344 · Issue 519891
Single quotes escaped in RTE title field value
Resolved in Pega Version 8.2.6
A JSON parse error was caused by single quotes not being escaped in the RTE title field value. This has been corrected.
SR-D47689 · Issue 520829
EvaluateConditions properly sets context for refresh section
Resolved in Pega Version 8.2.6
Rule Not Found and Unresolved Assembly Errors were seen in production logs after upgrade. Investigation showed that the method context used by pzpega_ui_changetracker.js in "evaluateConditionsOnXThread" was not reset correctly, causing the refresh section response for the Recents List to not be properly updated. This has been resolved by updating the evaluateConditionsOnXThread method to set the proper context after evaluateClientConditions is run.
SR-D47886 · Issue 514779
Home icon retains correct color after refresh
Resolved in Pega Version 8.2.6
By default, the home icon is a svg tag with dark or white filling (based whether it is selected or not), however if another tab was selected and the page refreshed, the icon went black and became a svg img tag. This has been corrected.
SR-D48544 · Issue 530851
Corrected null-pointer exception for Expression Builder launch from data join
Resolved in Pega Version 8.2.6
A null pointer exception error seen when attempting to open the Expression Builder from a data join strategy component was traced to a code comment that overran the line length and was rendered incorrectly during JS compacting. This has been corrected.
SR-D49076 · Issue 523172
Modified section auto-call to pagination refresh
Resolved in Pega Version 8.2.6
When the pulse gadget had at least one pulse note, Page error messages were flashing and not displayed permanently. This was traced to a custom error section: if a request was sent in one context/page, while getting the response the system also fetched a new error section for that context/page. That meant "pyFeedInner" was called to refresh, and that function includes "pzKeepPageMessages" as false. The reload call was originating from pagination that was happening automatically even when the current index was less than the page size. To resolve this, the system has been updated to not send a new request when current index is less than the page size.
SR-D49305 · Issue 519364
Tab layout group handling improved
Resolved in Pega Version 8.2.6
A difference in scrolling speeds between left and right arrows and an issue with the cursor correctly being redirected to mandatory fields were traced to errors in the tab layout group handling. The right scrolling issue was due to the calculation for right tab movement being incorrect in certain resolutions with relatively positioned elements, and has been corrected. The cursor redirect was caused by an error in the layoutgroup focus when used inside a screen flow where the first focus goes to the screenflow navigation on load, and has been resolved by adding a try catch for an invalid selector in case of a div error.
SR-D50208 · Issue 517232
Corrected layout of sort and filter icons for grid tables
Resolved in Pega Version 8.2.6
The sort and filter icons in a table grid were almost overlapping, and in some cases the sort icon was so small that it was almost not visible unless the width of the specific text was enlarged to see it. This was traced to a CSS snippet present in one of the override files that forced the width of the name column grid header to 100%, and has been corrected by ensuring the sort column is left aligned next to the column header.
SR-D50311 · Issue 516351
Testautomation API documentation updated
Resolved in Pega Version 8.2.6
The documentation explaining how to create, run and edit scenario tests has been updated with the following information:1. Scenario tests cannot be run from the Actions > Run menu of the service rule form. 2. Run option from the test case rule form is removed in the latest releases. https://community1.pega.com/community/pega-support/question/scenario-testing-how-create-run-edit-test-cases
SR-D51776 · Issue 531984
Check added to resolve Ajax Container instantiation error in log
Resolved in Pega Version 8.2.6
When using the Microsoft Internet Explorer or Edge browsers, manually launching a Service Intent and clicking the F5 refresh button properly refreshed the screen, but the PegaRULES log file contained the error "(DynamicContainerDataModel) Error occurred while instantiating tab for the thread index." This issue / exception was observed only when pzCustomDCTabHeader was configured (pyEnableCustomTabHeaders) and when there was a AjaxContainer configured in the document. Because the CustomTabHeader recreation (DynamicContainerDataModel.updateCustomTabHeader) should be skipped for AjaxContainer, as CustomTabHeader is applicable only to the top level DC document and not to the AjaxContainer document, a check has been added to resolve this issue.