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-C60247 · Issue 413680
pzRuleFormToolbarPopulateActions works when @ is present in the operator ID
Resolved in Pega Version 8.1.3
Using pzRuleFormToolbarPopulateActions to get all the versions of the rule was not working as expected if the '@' symbol was present in the user ID. This was caused by the Rule-.pzRuleFormToolbarPopulateActions activity not forming the private rules correctly in this use case, and has been fixed.
SR-C65381 · Issue 415189
Added check for pyType when refreshing the Declare_pyDisplay Page
Resolved in Pega Version 8.1.3
The standard behavior of clicking a link in the left navigation of the Pega Diagnostic Cloud manager portal is to open a new thread which automatically adds/updates the Declare_pyDisplay Page. However, in some circumstances opening the work items and clicking the navigation link followed by a refresh/F5 from the Google Chrome browser caused the Declare_pyDisplayDatapage to become corrupted and either froze the screen or caused a new popup window to open. This was traced to a situation where the parameter "pyType" was not present in one of the cases, causing the system to rely on "harnessName" instead. To resolve this, a check has been added that will retrieve pyType from the docObj parameter page of the pzpega_ui_dynamiccontainer.js file if needed.
SR-C67397 · Issue 416252
Added check for missing rule data when using abstract class in CSS
Resolved in Pega Version 8.1.3
Including CSS optimization with abstract class in the Advanced tab of the 'Add Optimization' Screen resulted in a Null pointer exception error. This has been resolved by adding a check for missing data from a rule to make the system more resilient in its handling of a corrupt flow-action clipboard page.
SR-C68069 · Issue 416698
Page group use added to referenced properties context for RDL
Resolved in Pega Version 8.1.3
After upgrade, a stack mismatch error was generated by a previously-working configuration that used a nested RDL with a section under Work- class that itself contained an RDL with Data- property that then included a section from Data -- class which contained another RDL that referred to the Work- Page Group. This error was caused by the use case of page group being missed during implementation of referenced properties in ContextProcessor processListNode, which has now been resolved.