INC-161430 · Issue 627719
Accessibility Component/Widget role added to pyCaseErrorSection
Resolved in Pega Version 8.4.5
Page level errors were not accessible due to the error section being wrapped inside a dynamic layout whose contents were not readable. This has been resolved by updating dynamic layouts to use the correct accessibility roles.
INC-161682 · Issue 642604
Context check updated for Delegated Data Type error message
Resolved in Pega Version 8.4.5
Once error messages for some auto set by declare expression appeared on the delegated Data Type editing screen, they persisted even after these errors were fixed. This was traced to the pega.ctx.harnessID and body's harness-id not being in sync, and has been resolved by updating root contexts to look for the error.
INC-161757 · Issue 630689
CKEditor correctly formats copy and paste
Resolved in Pega Version 8.4.5
Formatted text from Micrtosoft Word was not retaining its format when pasted into the rich text editor. This was caused by the inch to px and pt to px conversions not happening properly for margins, and has been resolved by adding a margin fix for nested bullets and lists.
INC-161937 · Issue 640262
VMWare workspace One Mobile support added
Resolved in Pega Version 8.4.5
Support has been added for the VMWare workspace One Mobile app by updating the BrowserUtilsRuntime file to add the necessary user agent.
INC-161999 · Issue 632208
Correct operator time zone passed for offline mobile case
Resolved in Pega Version 8.4.5
After selecting a date on the UI for a date only property and submitting it, the date was automatically incremented to the next day when using the mobile offline app. No increment was seen in the mobile browser. This was traced to the operator time zone being overridden for date and date range properties in an offline case, and has been resolved by ensuring the correct operator time zone is passed when working offline.
INC-162054 · Issue 633081
Updated context switch handling for event fired on modal
Resolved in Pega Version 8.4.5
A modal window thread became inactive after switching out from a modal window to another tab and returning back. This was traced to the submit modal being called on the OpenPortal thread, and has been resolved by updating the harnessContextSwitchHandler method to update the current context when an event is fired on a modal.
INC-162122 · Issue 633065
Create modal is accessible when creating case from Create menu
Resolved in Pega Version 8.4.5
After creating a new case in the Cosmos User Portal, the “Create” screen Modal Dialog opened but focus did not move to any element within the modal dialog but instead stayed on the “Create” button on the left side menu of the User Portal. It required approximately 50 tabs to reach any actionable element within the modal dialog. Investigation showed that the create modal launched the section in an AJAX container that looked like a modal, but the focus was not being correctly set on the first element. This has been resolved by ensuring there is a focusable element when launching an AJAX container.
INC-162692 · Issue 629635
Added primary portal navigation role
Resolved in Pega Version 8.4.5
While in the User portal, Accessibility inspector displayed the warning "Primary Portal navigation may be missing a navigation role." This role has now been added to pzPortalNavigation.
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.