INC-150188 · Issue 613653
Dirty dialog flag reset added for custom modals
Resolved in Pega Version 8.4.4
When a discard button in a custom Cosmos modal dirty dialog was clicked, pega.u.d.isDirtyDialogOpen was not reset to false. This caused the modal dialog to not be shown the next time. This has been resolved by modifying pzpega_ui_doc_dirtyhandling to support this dirty handling discard use case.
INC-150222 · Issue 612576
Custom client-side future date validation works on mobile
Resolved in Pega Version 8.4.4
After developing a custom client side validation based on documented examples that used jquery to locate two input fields (date pickers) and added an on-change function, the validation worked as expected on the desktop but gave a validation error for any future date when using the mobile app or browser. This was an issue with the name attribute handling on mobile, and has been resolved.
INC-150407 · Issue 605842
Validation error messages correctly cleared in nested markup
Resolved in Pega Version 8.4.4
A UI Freeze issue was seen whenever mandatory input was missed and the form was submitted. Continuing was possible after browser refresh, but a new Next>> button appeared. This was an unintended side effect of work done to correctly clear validation messages when areas had captions, and has been resolved by modifying that work so it performs as expected on nested markup.
INC-150472 · Issue 607394
Sorting works after selecting a view on GRID
Resolved in Pega Version 8.4.4
After configuring an optimized table with personalized view, saving a view and toggling to the new view, the sorting on the grid did not work anymore. Returning to the default view did not fix the problem, but sorting was reenabled after a browser refresh. This was traced to duplicate removeinstance calls of the grid which deleted the click event listeners for sort, and has been resolved.
INC-150555 · Issue 620542
isDCSPA flag added to ensure correct harness after reload
Resolved in Pega Version 8.4.4
When moving from a Process Flow to a Screenflow configured with tabbedscreenflow7, the first reload caused a switch to a Perform Harness that resulted in the error "Unable to open an instance using the given inputs", and footer buttons disappeared until multiple refreshes were done. This was an issue specific to the environment configuration at the site, but to avoid future issues a code update has been made that will add the isDCSPA flag if the value is not present in the parameter page.
INC-150872 · Issue 613079
JAWS reads the tab name and the close icon details seperately
Resolved in Pega Version 8.4.4
By default, all currently opened Work Objects Close icons have the label "Close Tab", but when moving across tabs while using the JAWS screen reader, reaching a work object tab caused JAWS to read the entire tab header as "S-123 close tab". In order to improve accessibility, aria-labels will be added while setting label to the tab so the header and close icon will be read separately.
INC-150875 · Issue 610717
Date field filtering changes maintained after logoff/login
Resolved in Pega Version 8.4.4
After hiding some date/time columns and logging off, when logging in again the filter overlay on the date/time columns were displayed differently. Initially the filter values were shown with the check boxes and a 'Choose Date' range drop down, but after the logoff and login search text was shown instead of the choose date range drop down. Investigation showed that the Datatype was not being captured correctly as part of ConstructGridHeaderMetaData function in GridUtilities.java file, which affected Date, DateTime, Integer & Decimal. This has been corrected.
INC-151050 · Issue 610678
Added check for empty string to custom Timeline Date Range
Resolved in Pega Version 8.4.4
When using the Timeline control and selecting Date Range as a custom value, the loading icon (busy indicator) showed continuously on the screen and no other operations were possible. Selecting any Date Range other than the custom field value worked as expected. Investigation showed that the Timeline control was not working when the Date Range value was empty, which in this case was traced to a value being entered at design time and then cleared. In timeline options, the Date Range end option was checking for the value being undefined and did not consider the empty string (""); this has been resolved by adding a condition to check if the Date Range option end is an empty string.
INC-151401 · Issue 615716
Context set for progressive scroll load of dynamic layout
Resolved in Pega Version 8.4.4
When setting pagination as 'Progressively load on scroll' for a repeating dynamic layout in a section with pagelist as the source, scrolling resulted in a null pointer exception and no further scrolling was possible. The issue was not seen when 'Progressively scroll on user action' was used. Investigation showed the activity Reload Section was failing because of the failure in the pre-processing activity, and this has been resolved by setting the correct context before making the pagination call.
INC-151418 · Issue 610229
Authentication updated for legacy activities
Resolved in Pega Version 8.4.4
Authentication updates have been made for several legacy activities invoked via URL by custom HTML.