SR-D68311 · Issue 535984
Corrected table row highlighting on iPad
Resolved in Pega Version 8.3.2
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-D68721 · Issue 532594
Corrected span tags in non-templated Autocomplete
Resolved in Pega Version 8.3.2
Span tags were seen in the auto complete list when Results display was selected as "In a list". This appeared only in non-template mode, and was traced to the application of a crossScriptingFilter after adding span.match element to the value. To correct this, the crossScriptingFilter will be applied before adding the span.match markup to the value.
SR-D69452 · Issue 536399
Layout management corrected for nested gadget sections
Resolved in Pega Version 8.3.2
Post-upgrade, some buttons were missing or mis-aligned, specifically the 'Reopen' and 'Cancel this Assignment' buttons were missing, and if 'Cancel this Assignment' was clicked, the Back button was missing. Investigation showed that when using nested gadget section includes, the necessary stack management to pop previous gadget parameters was not present. This has been resolved by adding a check for template rendering, as there is separate handling for template rendering to manage the stack.
SR-D70064 · Issue 541961
Case UI correct following multiple approval levels
Resolved in Pega Version 8.3.2
After proceeding through different levels of approvals, the UI of the case was incorrect on the final approval submit. This was traced to the forceSkinGeneration parameter, which was set to true, being used by a workformstyles fragment. This has been resolved by changing pzUsePreferenceSkin to "once" and setting the parameter forceSkinGeneration to false after the pyAttachAsPDF activity call.
SR-D70310 · Issue 537139
Window type check added for icon display logic
Resolved in Pega Version 8.3.2
When a Role had privileges to use Live UI, Agile WorkBench and Scenario Testing, the Scenario Testing tool icon intermittently did not show. This was traced to an incorrect condition used to check whether current window was of type desktop (portal) window, and has been resolved by adding a check that will also ensure consistency with Agile Studio icon display logic.
SR-D71105 · Issue 532188
Corrected error when using CharCounter in non-template mode
Resolved in Pega Version 8.3.2
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 535407
Corrected autocomplete results for parameterized Report Definition in grid
Resolved in Pega Version 8.3.2
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 Report Definition 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 537006
Support added for dynamic CSS class reference in optimized grid
Resolved in Pega Version 8.3.2
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 532330
Localization added for Pega Call Login screen
Resolved in Pega Version 8.3.2
Localization has been added to the label "Value can not be blank" on the Pega Call Login screen.
SR-D71522 · Issue 539321
Radio button error resolved for scenario testing
Resolved in Pega Version 8.3.2
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.