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.
INC-164311 · Issue 635785
Correct datetime target property used
Resolved in Pega Version 8.6
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-169907 · Issue 648484
Handling added for element outside viewport in overlay
Resolved in Pega Version 8.6
The left attribute from overlay styles was changing from "0" to a negative value (dynamically depending on screen size) while scrolling the results up and down. This caused issues such as attempting to view the duplicate case analysis screen or having the tool tip move to the extreme left when hovering the mouse on a link and scrolling. This was traced to an overlay launched from a table: if client.left was zero, the overlay left was given a negative value which causes the overlay to be shifted towards left side of the screen. To resolve this, an extra condition has been added to check if the associated element is outside the viewport when an overlay is launched from a table, and if so apply a flippedX value for left property.
SR-69015 · Issue 619995
Unescaping characters implemented for expressions
Resolved in Pega Version 8.3.6, Resolved in Pega Version 8.4.4, Resolved in Pega Version 8.5.3, Resolved in Pega Version 8.6
An issue where expression builder statements were evaluated differently at runtime than at testing has been resolved. Pega Platform expressions with String literals(that is, sequences of characters enclosed in quotation marks) now unescape characters in strategy shapes such as Set Property or Filter.
SR-C81829 · Issue 419227
pxCoveredCountOpen value decrease corrected
Resolved in Pega Version 8.2.1
When a flow reached the resolved stage (Resolved-Withdrawn), pxCoveredCountOpen was reducing the count by 2 instead of 1, eventually causing the value to go negative and prevent any further work objects from being marked as Withdrawn. Investigation showed the "Update status" activity was being called twice due to the Temporary WorkPage used to delete assignments persisting and appearing as a duplicate pyWorkPage. This caused an issue when using findPage by pzInsKey. To correct this, the "pxDeleteAssignmentsForWork" activity for Step-15 has been modified to explicitly remove the temporary WorkPage after the assignment is deleted.
SR-C85035 · Issue 421947
Added getIfPresent check for Field Value parameters with pzAPICreateJsonForView
Resolved in Pega Version 8.2.1
Calling pzAPICreateJsonForView was altering case values if localized field value parameters were added. This has been corrected by performing a getIfPresent and getIfString on the property pyFieldValueParams so field value parameters will not be added to the main page if they're not present.