SR-D66436 · Issue 529671
Correct Value shown for Helper Text controls with labels
Resolved in Pega Version 8.2.6
Helper Text sourced from a field value was displaying the field value's 'Translate From' value rather than the 'Translate to' value. Analysis showed that the 'title' attribute of the corresponding icon on the DOM was being populated differently depending on whether it was a control with labels (not working) or a caption on a checkbox control (worked as expected). To address this, a check has been added for datetime and checkbox controls to send fieldname as pyCaption and pyActionPrompt respectively instead of pyTooltip to resolve the value.
SR-D68277 · Issue 541815
Added logoff check for requestors
Resolved in Pega Version 8.2.6
After upgrade, the error "java.lang.InterruptedException. Requester has been destroyed" was appearing in the logs. Investigation showed this was related to unregister requests being submitted after logoff, and has been resolved by updating the system to check for logout before sending unregister requests.
SR-D68311 · Issue 535986
Corrected table row highlighting on iPad
Resolved in Pega Version 8.2.6
A table row was highlighted when clicked on an iPad in landscape view, but when the device was rotated to portrait view the row was not highlighted. This was traced to the background CSS overriding the selected style, and has been corrected by modifying py-responsive-overrides.css.
SR-D68776 · Issue 535467
Improved Timezone sync between operator setting and server
Resolved in Pega Version 8.2.6
When the operator timezone was empty, it defaulted to America/New_York in client side code. To better sync client and server, changes have been made so that when an empty timezone is seen, the system will retrieve the timezone from the server configuration.
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.