SR-D40055 · Issue 507422
Work List loads as expected in IE
Resolved in Pega Version 8.4
After upgrade, the Work List was not loading in IE. This was an unintended side effect of work done to handle resizing the Recents list when another tab was open, and that change has been reverted to resolve this issue.
SR-D40617 · Issue 507566
Escape added to Radio button field value to handle HTML tags
Resolved in Pega Version 8.4
A radio button with a field label to display a help icon and to open the help URL when the icon was clicked did not display as intended. Changing the control to text area produced the desired results. This was traced to the radio button's label being assigned to a field value which returned a string that at some points contained HTML tags, and has been resolved by escaping the pyLabelFor value before assigning it to the aria-label attribute of the radio button's div tag.
SR-D40762 · Issue 510370
ReloadSection passes event object explicitly
Resolved in Pega Version 8.4
After upgrade, 'replace current-model' was not working when used in a section with a link control that had an onClick event that was intended to launch a local action. Investigation showed that the link control was not working in the latest Google Chrome version, and this has been corrected by passing the event object explicitly to the reloadSection function in PZPEGA_UI_DOC_SUBMIT.js
SR-D40778 · Issue 512976
Asterisk symbol displayed for radio button set to required always
Resolved in Pega Version 8.4
When marked as required, the "Asterisk" symbol did not show up on the radio button label. This was traced to an XML cleanup issue with the pyReqRunOnClient property when required was configured as 'always' and has been corrected.
SR-D40803 · Issue 511593
JSON parsing error on export resolved by ensuring parameter encoding
Resolved in Pega Version 8.4
Menu items like "PDF" and "Excel" were not loading on click of the "Export" Button, and an "Exception in parsing JSON" message was logged. The export worked as expected when the menu rule actions of each menu item were modified to remove the openurlinwindow actions. This was traced to the Response JSON being broken due to a invalid format created when the "propositionName" was passed as an unencoded parameter when the report was exported. This has been resolved by ensuring the input parameters are encoded before creating the URL.
SR-D40941 · Issue 512593
Identifier property added for worklist with filter by format
Resolved in Pega Version 8.4
After configuring a Grid layout which displayed a users worklist, one of the properties representing the column in Grid had the property type as boolean. The property was derived from another report definition in the main report and a join was performed to display the property. Investigation showed that the filter for Boolean column did not show any filter values like ( [No Value, Y,N ) when run through a case Manager Portal, however the Boolean Column filter worked when run through Report Definition. Other properties from the same class that were not boolean worked with the filter. This was traced to the WorkListWidgetGridsAuto being set to Optimize code, causing filter by format to not be visible in the column properties of pxPages. To resolve this, code has been added for the identifier property
SR-D41035 · Issue 513206
Handlign added for OpenAssignment triggered from confirm harness
Resolved in Pega Version 8.4
Triggering openAssignment from the confirm harness was replacing the whole Ajax container DIV, leading to 'submit' no longer working. This has been corrected by adding additional handling for this usage.
SR-D41114 · Issue 508946
Localization added for 'NoResultys Found"
Resolved in Pega Version 8.4
It was not possible to translate/localize the message 'No Results Found' (autocomplete) to Spanish due to auto complete not containing any property or field value corresponding to this message. This has been corrected by adding the field value and corresponding code handling needed.
SR-D41130 · Issue 510080
Handling added for precision decimals in cascading dropdown on mobile
Resolved in Pega Version 8.4
A cascading dropdown with a parameterized datapage configuration containing decimal values with precision (such as 22.3,20.000) showed the values as expected on desktop, but the values were empty on mobile. The values did show on mobile as well if precision was not used. This has been resolved by updating templateengine_context so that decimal values will not be treated as a property reference.
SR-D41233 · Issue 511718
Radio button will not be generated for data page null result
Resolved in Pega Version 8.4
When a Radio Button was sourced from Data Page with a report definition or a data transform, a 0-results return still generated a radiobutton with a selectable dot but no option. This has been fixed by adding a check so the results will not be added to a data list if the value is undefined.