INC-163198 · Issue 637795
Performance improvements for research path interaction
Resolved in Pega Version 8.4.5
Research path interaction driver composite loading was taking an excessive amount of time due to RULE-HTML-SECTION @BASECLASS ERRORLIST being called multiple times. This has been resolved by changing the ErrorList Section to guard the getMessagesMapByEntryHandle API call with a condition "if (ClipboardPage.getMessageCountAll > 0)".
INC-163341 · Issue 637297
Discard functionality in dirty check confirm corrected
Resolved in Pega Version 8.4.5
Clicking on the Discard functionality in the dirty check confirm on popup closed the item rather than launching the expected work flow. This was traced to gDirtyOverride being returned as false instead of null in the explorerFormIsDirty function. To resolve this, the logic used to for gDirtyOverride on a native alert close for dirty handling has been removed.
INC-163544 · Issue 639298
Accessibility corrected for Cosmos user portal left navigation panel
Resolved in Pega Version 8.4.5
It was not possible to see the focused control label in the left pane of the Cosmos user portal because it was not expanding when its control received focus from tabbing. Investigation showed the class acting as a polyfill for :focus-within was applied only on the observed element when using Microsoft Explorer 11, and this has been resolved by updating the CSS selectors and ensuring the class is applied to every parent element down the DOM tree.
INC-163596 · Issue 636234
Checkboxes receive correct focus with accessibility
Resolved in Pega Version 8.4.5
It was necessary to click the tab twice in order to check the checkbox in the filter popup. This has been corrected by adding a check in the firstfocuselement method so the focus is placed correctly over input type elements.
INC-164311 · Issue 635784
Correct datetime target property used
Resolved in Pega Version 8.4.5
When using a declare expression for a datetime property to get its value from another datetime property, attempting to change the source datetime later resulted in the error "28-mar-2021 is not a valid date/time value". This occurred when the source datetime property had display readonly formatting, and was traced to the formatted value being sent in the callGetTargets API instead of the selected date value, which caused the function to be returned as empty because there was no target property in the same page before submission. To correct this, a check has been added which will get the value from data-value instead of element.value and will skip callGettragets if the target is empty.
INC-164631 · Issue 641441
Updated Ajax container close to resolve intermittent portal freeze
Resolved in Pega Version 8.4.5
The portal was intermittently freezing after the "+" icon was clicked to create a new case from the Create menu. This was traced to the Ajax container not closing after creation of the create modal, and has been resolved.
INC-164892 · Issue 636538
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-164924 · Issue 639010
Serbia added to country codes list
Resolved in Pega Version 8.4.5
The CountryCode for Serbia (SRB) has been added to the existing country codes.
INC-165277 · Issue 645170
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-165363 · Issue 635076
Dirty Check Warnings added for decimal fields
Resolved in Pega Version 8.4.5
Dirty Check Warnings have now been added for decimal fields by adding the required logic to the isContainerDirty API in pzpega_ui_doc_dirtyhandling js file.