SR-D69818 · Issue 533164
Corrected Smart Info popup handling for hover away
Resolved in Pega Version 8.2.6
The Smart Info pop up was intermittently not closing automatically on hover away. When it happened, a "box" appeared around the the smart info pop up and the "notch" was missing. This was caused by a timing issue in the javascript, and has been corrected by adding a time delay to attach the listener properly in smartinfojs.
SR-D71105 · Issue 532189
Corrected error when using CharCounter in non-template mode
Resolved in Pega Version 8.2.6
An error message was generated when trying to save a section with the TextArea's Display CharCounter set to True. This was traced to an error in the remaining character count span generation for non template mode and has been corrected.
SR-D71202 · Issue 535408
Corrected autocomplete results for parameterized RD in grid
Resolved in Pega Version 8.2.6
An autocomplete included in a grid and configured with results display as 'List' where the source for the autocomplete was a parameterized report definition and the RD parameter was an associated property of autocomplete did not show any results. If the results display was changed from 'List' to 'Grid', it worked as expected. This has been resolved by adding a null check on rowdetail in the "replaceParamsTokens" method for autocomplete.
SR-D71355 · Issue 537008
Support added for dynamic CSS class reference in optimized grid
Resolved in Pega Version 8.2.6
When using the property pyStatusWork in an optimized grid, it was not possible to set a color code for different work statuses. This worked on an unoptimized grid. This has been resolved with the introduction of a dynamic CSS feature. This control can be changed to an autogenerated control like "Formatted text" and apply color coding through classes. To use this, a property value must be specified in cell classes in the presentation tab of the table cell, and then populate each result of a data page with that property which contains some class value appropriate for status value. CSS must be written for the different classes (class name is stamped on <td> in markup).
SR-D71402 · Issue 532331
Localization added for Pega Call Login screen
Resolved in Pega Version 8.2.6
Localization has been added to the label "Value can not be blank" on the Pega Call Login screen.
SR-D71450 · Issue 538101
Corrected display of ">" in multiselect control
Resolved in Pega Version 8.2.6
When using a Multiselect Property configured with a data page as a source, any value with symbol ">" displayed as > in the list the first time but displayed correctly after being selected. This was traced to the conversions being handled in the sectionResultMarkup of pzpega_control_multiselect for Cross-site scripting protection, and has been corrected.
SR-D71522 · Issue 539323
Radio button error resolved for scenario testing
Resolved in Pega Version 8.2.6
When creating a scenario test case that selected a radio button and navigated the screen, it worked to complete a case and save the scenario test case in a rule set. However, attempting to then run the scenario test case stopped with the error message "Value cannot be blank" for the radio button even though the value "No" was captured for the button. This was traced to the firing of the change event, and the system has been updated so 'pega.u.d.setProperty' will only fire a click event on a selected radio button option.
SR-D71756 · Issue 533549
Thread Cleanup error resolved
Resolved in Pega Version 8.2.6
After upgrade, intermittent exception errors were being generated by the FreeClipboard activity when switching between applications. This was traced to specific use-case issues with Thread Cleanup, and has been resolved.
SR-D71944 · Issue 543730
Resolved data page loop in templatized UI
Resolved in Pega Version 8.2.6
A Layout Group was configured with six dropdowns sourced to Parameterized datapages with "disable automatic refresh" unchecked; every next dropdown depended upon the previous property, and the previous property was sourced as parameter, and so on until last dropdown. When the value in the dropdowns changed, the section kept refreshing and the portal became unresponsive. This was traced to the combination of a Datapage as the source to the dropdown with "disable automatic refresh" unchecked and expression evaluation as well.Templatized UI has 'visible when' expressions for all the properties inside the top level page. Changing the first one fired refresh on the next one, and the next one's refresh fired the other drop down refresh until it became recursive. This did not occur in non-templatized UI as it does not have expression IDs and there are no recursive calls. This issue has been corrected by modifying how the temporary mapping is populated by the reloadCells API in Expression Evaluator to prevent unwanted cell refreshes.
SR-D72121 · Issue 536409
Currency Control accepts value on PostValue action set
Resolved in Pega Version 8.2.6
Currency control in the section was sourced by a decimal property. Irrespective of the value entered, the validation triggered the message "entered value is not a decimal value" and did not allow user to proceed. Investigation showed than on getting the server response for post value action, the target element was updated with the response value when it should be skipped for currency control. To resolve this, an additional check for attribute: data-formatting has been added to the textInput control so when action PostValue is configured on Currency control and there is a change of value, the system will skip replacing the value with formatted value.