INC-162426 · Issue 638770
Regex handling updated for Rich Text Editor spellcheck
Resolved in Pega Version 8.5.4
When using the Rich Text Editor and performing a spell check, the spell checker was adding additional CSS to the property. This was traced to the presence of a unicode newline character causing the existing regex to fail to strip the style tags. To resolve this, regex handling for the unicode newline character in the style tag has been added.
INC-162642 · Issue 636139
Show Stream activities updated
Resolved in Pega Version 8.5.4
Authentication requirements have been added to Show Stream activities.
INC-163198 · Issue 637797
Performance improvements for research path interaction
Resolved in Pega Version 8.5.4
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 637299
Discard functionality in dirty check confirm corrected
Resolved in Pega Version 8.5.4
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 639300
Accessibility corrected for Cosmos user portal left navigation panel
Resolved in Pega Version 8.5.4
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 636236
Checkboxes receive correct focus with accessibility
Resolved in Pega Version 8.5.4
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-163651 · Issue 636901
Cancel button in offline works as expected
Resolved in Pega Version 8.5.4
When using the mobile app offline, clicking 'cancel' after creating a new case did not remove the case, but instead returned to the review screen. This was traced to the logic used to evaluate the conditions, and has been resolved so that the 'cancel' button will return to the worklist if offline, or display save/delete options when in the create stage of the online app.
INC-163702 · Issue 634969
Path to image resource files updated for offline app
Resolved in Pega Version 8.5.4
When using the offline app, "resource missing " errors were seen for some image files. This has been resolved by overriding the images folder path in the userworkform with the correct path to the webwb folder.
INC-164012 · Issue 640040
Source edit with formatting resumes process automatically
Resolved in Pega Version 8.5.4
When opening a paragraph rule and clicking on Actions > checkout out to branch, the rule refreshed and the modal never appeared to allow the selection of a branch on the current application. This was an inadvertent side effect of work done to resume the event queue if it was paused when applying styles, and has been resolved by modifying the work so it resumes the action sequence only when source mode is initialized in the Rich Text Editor.
INC-164311 · Issue 635786
Correct datetime target property used
Resolved in Pega Version 8.5.4
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.