SR-D73224 · Issue 542630
Case manager portal links working with SVG file
Resolved in Pega Version 8.4.1
After modifying the pyPortalHeader to show a custom logo in the Case manager portal by saving the pyapp-logo.svg file into a ruleset and uploading the logo, none of the Case manager portal links or menus were working and a console error appeared. Investigation showed the SVG file stream was decoded and then encoded using the Base64Util.encode and decode, which was adding new line characters. To resolve this, step 4 in Rule-File-Binary.UploadFile Activity has been modified to remove the Base64 encode and decode.
SR-D73510 · Issue 538665
Cross-site Scripting filtering for ActionStringID
Resolved in Pega Version 8.4.1
Cross-site Scripting filter logic has been added to the ActionStringID function.
SR-D73847 · Issue 537828
Added exception handler for URL decode error
Resolved in Pega Version 8.4.1
After logging in to Pega Deployment Manager, clicking Users -> People in the left navigation panel resulted ArrayIndexOutOfBoundsException. This was traced to an incomplete trailing escape (%) pattern and has been resolved by adding checks and exception handling for incomplete data from the browser.
SR-D74008 · Issue 537291
A filter on the grid shows value for a second click
Resolved in Pega Version 8.4.1
A Filter on the grid was not showing any record value for a second click. This was traced to a conflict in considering column headers caused by the Filter Icon delegating two Grids, leading the process to take the context of the other Grid instead of the one which had been clicked. To resolve this, a check for the right context of the Grid has been added to the filterOnProperEvent method.
SR-D74057 · Issue 540062
Updated aria handling for Dynamic Layout Group 'Accordion'
Resolved in Pega Version 8.4.1
The Dynamic Layout Group display type 'Accordion' was not getting initialized properly on the browser developer inspector. This was traced to the aria-selected attribute set to always be true, and has been resolved by adding logic to set and unset aria- selected only on the active tab. When the tab is not active, then aria-selected will be false.
SR-D74165 · Issue 537515
DateRange clear button localized
Resolved in Pega Version 8.4.1
Localization has been added to the 'clear' button in DateRange.
SR-D74992 · Issue 546878
Improved CPMHC performance
Resolved in Pega Version 8.4.1
After upgrade, slowness was seen when using the CPMHC application. This has been improved by adding Microsoft Internet Explorer 11 optimization with the most recent javascript API.
SR-D75205 · Issue 543568
Refresh with DT or pre-activity added to dirty pop up check
Resolved in Pega Version 8.4.1
Given a button which when clicked launched a data transform to set a few properties on the UI followed by a section refresh, a dirty warning popup did not appear when closing the work object even though the property changed via the refresh section. This has been resolved with an additional condition in the dirty pop up check to handle a refresh section using a DT or pre-activity.
SR-D75964 · Issue 542687
Check added to ensure enter key triggers autocomplete onchange
Resolved in Pega Version 8.4.1
Tenant details were not loading, and no requests were seen being generated after the selection of the tenant. Investigation showed that for autocomplete control, a dummy onchange attribute was added, i.e., data-change = "[]". When the value was selected using the enter key, fireACOnElem was not executed in processEvent function as the condition isExplicitConfig(target) was true. To resolve this, an additional check attr(data-change) != "[]" has been added for ClientConditionExecutor to trigger fireACOnElem.
SR-D75966 · Issue 537946
Check added so DT parameters passed when using anchor tag
Resolved in Pega Version 8.4.1
When using a link control configured such that the value of the text in the link control refers to an anchor tag such as Text, clicking the link to launch a harness and call a DT with passed parameters was not working. Investigation showed that when the link had an anchor tag, pyDataTransformDynamicParams was not getting passed as query string parameter. In pega.desktop.showHarness function, there is a If condition which checks whether any "=" is present in preDataTransformName variable and if there is any, it does not add pyDataTransformDynamicParams. This was not an issue with anchor tag itself, but rather a generic issue: any value with "=" would behave in the same way. To resolve this, the pega.desktop.showHarness API has been updated to check against the proper value (pyDataTransform=) instead of just = to identify old modal parameters.