INC-154855 · Issue 616002
Updated expression handling when not using client side validation
Resolved in Pega Version 8.4.4
After upgrade, a declare expression used to calculate the end date when creating a schedule case was not populating the result. This was traced to a missed use case for evaluating expressions when 'Enable client side validation' is unchecked, and has been resolved.
INC-156992 · Issue 619707
Show-stream/html repaired for custom portals
Resolved in Pega Version 8.4.4
After upgrade, show-stream/html in activity was not getting executed properly on custom portals. ShowDesktop was modified in 8.1 for AssociateRequestor implementation. As part of that, the custom portal step was moved to the new activity pzPopulateRequestor which is invoked from ShowDesktop. The JUMP condition in step is exiting the pzPopulateRequestor activity, but not ShowDesktop as was the case in the previous versions. To resolve this, the JUMP condition (.pyDesktopType=="Custom") has been added in ShowDesktop at the pzPopulateRequestor call step.
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.