INC-161996 · Issue 636873
Mobile back button updated for case completed scenario
Resolved in Pega Version 8.6
In a scenario when a case was resolved and assignments were removed from user pages, the hitting the back button presented the error: "unable to open an instance using the given inputs". This was a missed use case for using the back button on the mobile app after a case is completed, and has been resolved by modifying the back button action in this scenario from "window.history.back" to Cancel action.
INC-161999 · Issue 632210
Correct operator time zone passed for offline mobile case
Resolved in Pega Version 8.6
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-162012 · Issue 633727
Leeway added for circular reference checks in nested section includes
Resolved in Pega Version 8.6
In the pyCaseMainInnerMobile(“work-“ class) section, attempting to apply a few changes for the pyMainCasePanelMobile section which was already included inside a pyCaseMainInnerMobile Section resulted in the submit button not working from the popup. This was an edge case where a deeply nested section include was referencing sections from a Pega marketing class as a result of backporting sections from the marketing application. To resolve this, constraints on circular reference checks have been loosened.
INC-162122 · Issue 633067
Create modal is accessible when creating case from Create menu
Resolved in Pega Version 8.6
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-162642 · Issue 636138
Show Stream activities updated
Resolved in Pega Version 8.6
Authentication requirements have been added to Show Stream activities.
INC-162692 · Issue 629636
Added primary portal navigation role
Resolved in Pega Version 8.6
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-162742 · Issue 630968
Repaired '+' icon for edit reports in Cosmos
Resolved in Pega Version 8.6
The + icon was not showing for edit reports due to missing styles for the icon in Cosmos. This has been resolved by adding the "background-image" styles for collapse and expand icons.
INC-163341 · Issue 637298
Discard functionality in dirty check confirm corrected
Resolved in Pega Version 8.6
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-163596 · Issue 636235
Checkboxes receive correct focus with accessibility
Resolved in Pega Version 8.6
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 636900
Cancel button in offline works as expected
Resolved in Pega Version 8.6
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.