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.
SR-D41446 · Issue 508991
Multiselect control modified to not allow duplicate capsules
Resolved in Pega Version 8.4
When using an OpenID Connect authentication service it was noted that the scopes were added multiple times when saving the authentication service or changing the scopes. Investigation showed this occurred when the multi select control was used for the scope field, with multiple values appended during reload cell activity itself. This was caused by the Multiselect control allowing duplicate capsules, and has been resolved.
SR-D41984 · Issue 510013
Added handling to correct '&' displayed as '&' in custom tab name
Resolved in Pega Version 8.4
When using a data transform and custom properties to set the tab title, clicking on a link containing "&" in the label opened a tab name which included "&" instead of "&". This has been resolved by modifying the handleGadgetLoad method in the pzpega_ui_dynamiccontainer file to handle the Cross Scripting FIlter and display the character.
SR-D42583 · Issue 514487
Label of a field is correctly rendered when a section is re-used with a visiblity condition
Resolved in Pega Version 8.4
The label of a field was not being rendered/visible when a section with a 'visible when' condition was re-used in different Page Contexts. The label was displayed correctly if 'Run visibility condition on client' was checked. As part of performance improvements made in a previous version, label generation was moved under the dlcellvisibility flag. Because of this, if a section was re-used at multiple places with different contexts and one place had visibility false and another had visibility true, the labels were not getting generated for the visible section. To resolve this, Label Generation has been moved out of dlcellVisibility to ensure label metadata will always be generated. Updated performance improvements have been made instead by way of a DSS setting (generateCellMetadata) so that when generateCellMetadata is true, the label generation will honor dlcellvisibility to generate the label metadata.
SR-D42701 · Issue 510923
XSS security added for Case Manager
Resolved in Pega Version 8.4
XSS security has been added to the Document features in the Case Manager portal.