INC-211253 · Issue 711280
Improvements for dirty popup
Resolved in Pega Version 8.8
Multiple issues have been addressed for dirty popups. 1) While working on an assignment, making a change and then clicking on the left navigation (Home, Dashboard) did not show the dirty pop up as expected, and the change was lost. The dirty pop up did appear on the Cancel button and Actions within the case. This has been resolved by improving the context switching for visibility of the dirty pop up. 2) Attempting to work around the previous issue by clicking "Do not display dirty warnings" only worked the first time it was tried. With this change in place, opening the assignment, making a change, then clicking Home, caused the pop up to appear as desired, but opening the assignment again and making a change, then clicking Home again did not prompt the dirty pop up. This was due to the click handler getting hit twice, leading to the already open dirty dialog being closed during the second call to the function 'isFormDirty' in pzpega_ui_doc_actionRouter.js file, and this has been resolved. 3) When attempting to close the case as a draft, clicking the save button caused the system to keep loading for a few minutes without sign of completing the save process and eventually the browser had to be closed. The content was saved, but the system was not able end the loading screen. This was caused by an incorrect harness context which caused the "SubmitInProgress" flag to be true on the incorrect harness context so the modal was not dismissed. To resolve this, on clicking the "Save" button, after the confirmation modal is closed, the pega.u.d.isDirtyDialogOpen will be reset to false.
INC-211492 · Issue 725341
Archived cases open correctly in new window
Resolved in Pega Version 8.8
Attempting to open archived cases from the search results using “Show results in a new window” generated an error. This was a missed use case and has been resolved by updating "pyShowResultsInNewWindow" to have a table to open archived items in a new window.
INC-211589 · Issue 710335
App-alias URL shown correctly on app definition rule after switch
Resolved in Pega Version 8.8
When using Cosmos React as the default app, switching from the react-based application to a non-react application resulted in a blank app-name in the application definition URL. Investigation showed the UI was not refreshing correctly on updating values in the app alias pop-up window, and this has been resolved by calling close work before harness unloads if no pending calls are present.
INC-211590 · Issue 711020
Auto-complete and calendar popover alignment corrected
Resolved in Pega Version 8.8
An issue with the container alignment of the auto-complete and calendar dropdown popovers has been resolved by removing styling in the pyReportEditorStyling .css which was causing the issue.
INC-211655 · Issue 712351
Added handling for Malaysian locale date/time
Resolved in Pega Version 8.8
When using the "ms_MY" locale for Malaysia, entering ‘14/02/2022 13:00’ in the displayed DateTime input field generated the error "14/02/2022 13:00 is not a valid date / time value." This was due to differences in the underlying Java version: in Java 8, the API PRDateFormat.getShortDateTimeFormat returns "dd/MM/yyyy h:mm" and the PRDateFormat.getAmPmStrings returns [AM, PM], but in Java 11, the API returns "d/MM/yyyy h:mm a" with PRDateFormat.getAmPmStrings returning [PG, PTG]. For the Malaysian locale ms_MY, the clock format is 12 hour and AM/PM Strings are PG, PTG. This caused environments running JDK11 to fail client side validation for date time when PTG (a 3-char AM/PM string) was selected. This has been resolved by adding handling for this usecase.
INC-211743 · Issue 711670
PD4ML upgraded
Resolved in Pega Version 8.8
Issues with PDF generation have been resolved by upgrading PD4ML to version 4.0.13.
INC-211911 · Issue 713053
Able to expand rows when other rows are expanded
Resolved in Pega Version 8.8
When multiExpand, threadProcessing, and readonly flags were true, attempting to expand multiple rows at the same time collapsed already opened rows and generated an error indicating "target is not defined". This was caused by 'handleEditItem' not calling the collapse functionality for an opened row correctly, and has been resolved by adding a check which allows the expansion of multiple rows for readOnly details.
INC-212623 · Issue 709551
Dropdown label is accessible when combined with placeholder or tooltip
Resolved in Pega Version 8.8
The screenreader was not reading the dropdown label if tooltips or placeholders were added to the dropdown. This was caused by the label of the element being overwritten, and has been resolved by replacing aria-label with aria-describedby on the input element.
INC-213247 · Issue 708868
Title attribute added for disabled icons
Resolved in Pega Version 8.8
The disabled icon control in non-template mode used the tempTitle attribute instead of title, interfering with accessibility because no information was available to screen readers. This has been resolved by adding the aria-disabled attribute to the disabled icon control.
INC-213717 · Issue 724533
Flag added to allow disabling copy/paste style formatting
Resolved in Pega Version 8.8
Copy/pasting text from Outlook or another external application caused formatting issues in the Rich Text Editor. To address this, the flag "window.disablePasteFromWord" has been introduced which allows turning off the feature of retaining formats when copying from Word or Outlook. This flag can be set to 'true' in UserWorkForm to disable this default feature.