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.
INC-164892 · Issue 636540
PDF generation corrected
Resolved in Pega Version 8.5.4
Issues with PDF generation have been resolved by upgrading the PD4ML libraries to version 4.0.9fx5.
INC-164979 · Issue 650154
Column values displayed in modify filter of grid
Resolved in Pega Version 8.5.4
Column values were not displaying in the modify filter after cancelling the ‘due date apply filter’ condition in grid -Go to My Work -> Work Queue -Apply filter condition for Program and Country/region columns. This was traced to the pysymbolic date value being posted after selecting and before applying the filter, and has been resolved.
INC-165277 · Issue 645169
PDF generation corrected
Resolved in Pega Version 8.5.4
Issues with PDF generation have been resolved by upgrading the PD4ML libraries to version 4.0.9fx5.
INC-165567 · Issue 643382
Window reference added for custom tab handling
Resolved in Pega Version 8.5.4
After configuring a tab layout in the portal harness rule to get tab view, launching the portal from Designer Studio and opening the tabs worked as expected, but opening the portal using end user operator and performing any operation in a tab resulted in the error "Uncaught ReferenceError: gIsCustomTabHeaderEnabled is not defined". This was caused by a reference property that was not being referred properly, and has been resolved by using gIsCustomTabHeaderEnabled from the window reference to handle the undefined scenario.
INC-166444 · Issue 642111
FlexModalTemplate Modal window size consistent
Resolved in Pega Version 8.5.4
The FlexModalTemplate modal window size was changing on second click. This was a missed use case for dirty dialog CSS implementation, and has been resolved by moving the CSS necessary into the isDirtyDialogOpen if condition.
INC-166706 · Issue 647476
Handling added for Rich Text Editor base tag in email
Resolved in Pega Version 8.5.4
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.