INC-166706 · Issue 647477
Handling added for Rich Text Editor base tag in email
Resolved in Pega Version 8.4.5
Clicking on an email interaction case from the worklist was not opening the case. This was traced to a base tag present in Rich Text Editor content which impacted security protections, and handling has been added to remove this tag.
INC-167379 · Issue 640577
Unescape function added to CSR portal layout template rule
Resolved in Pega Version 8.4.5
When older sections previously used by the CSR portal were carried forward into more recent versions and were 'saved as' in the application ruleset, the error "Uncaught TypeError: pega.util.Dom.unescapeHTML is not a function" appeared. Dashboard loading took an excessive amount of time or didn't load at all, and no actions were working on the dashboard screen and tabs. This was traced to there being an older implementation of pega.util.Dom.unescapeHTML in pzpega_ui_template_layout_header, and this issue has been resolved by adding a custom unescape function in the rule itself so that it doesn't fail in cases where the dependent rule is not able to load the standard unescapeHTML utility.
INC-167599 · Issue 648281
PDF generation corrected
Resolved in Pega Version 8.4.5
Issues with PDF generation have been resolved by upgrading the PD4ML libraries to version 4.0.9fx5.
INC-167747 · Issue 646577
PDF generation corrected
Resolved in Pega Version 8.4.5
Issues with PDF generation have been resolved by upgrading the PD4ML libraries to version 4.0.9fx5.
INC-168050 · Issue 640133
Resolved unregistered request for Dev Studio clipboard viewer
Resolved in Pega Version 8.4.5
After upgrade, running a report in Dev Studio and then clicking to start the tracer or clipboard did not open, but instead generated the error "Unregistered request encountered." This has been resolved by adding a pySecureFeatures check in step1.
INC-168426 · Issue 648079
Corrected popup placement
Resolved in Pega Version 8.4.5
SmartInfoContainer element top and left dynamic values were incorrectly calculated for popups. This was caused by the Cosmos application style overriding the platform style, and has been resolved by removing the Cosmos styling and using platform CSS for the tooltips and guided tour elements.
INC-168695 · Issue 643014
String conversion logic updated for toFixed function
Resolved in Pega Version 8.4.5
The toFixed function of pzpega_ui_formatNumber.js was incorrectly converting a string while formatting the value. This potentially caused the UI to hang until manually refreshed. To resolve this, the logic has been updated to convert the string to a number before calling toFixed().
INC-169866 · Issue 653550
View content type updated to FIELD
Resolved in Pega Version 8.4.5
After upgrade table grids were not visible in the UI for some operators while other operators with the same access group were able to see the same table with the result rows. Investigation showed that the personalized view stored in 8.1.x did not have a content type set, causing all of the columns to be hidden after upgrade to 8.4+ due to the personal view not matching with the design time view. To resolve this, the content type has been updated to FIELD for views.
INC-171352 · Issue 653693
Focus set correctly on the modal window in theme-Cosmos
Resolved in Pega Version 8.4.5
in theme-Cosmos with touch enabled, clicking on a button to open a modal window set the focus on the background instead of in the modal window, forcing tabbing through the full page to reach the modal window. This was traced to the templates not using the pzModalCancel control which has the necessary container_close for the modal dialog close icon, and has been resolved by adding a check to set the focus correctly.
INC-171449 · Issue 649931
Added null check for expression ID in Disable-When-Condition
Resolved in Pega Version 8.4.5
A Radio Button was not disabled despite a 'when' rule if a Data Page was used as the List source in the Radio buttons control and the property was passed as a parameter of the data page. Investigation showed that the expression ID for the Disable-When-Condition was present, but there were no expressions to evaluate. This has been resolved by adding a null check to verify if expressionResults is an empty object.