INC-150039 · Issue 608044
Adjusted validation of literal value of a parameter
Resolved in Pega Version 8.4.4
When mapping a parameterized when rule to the proposition filter, parameters passed from the proposition filter page were not getting flown to the when rule. This was caused by special character validation for a literal value of a parameter which necessitated putting the parameter value within quotes and which resulted in a parameter value mismatch at run time. To support this use, this validation has been disabled as parameter values would not get included within quotes. This change does not have any impact on when rule or proposition filter rules java generation.
INC-130090 · Issue 573263
Added handling for sourced radio-buttons group rendered in an inner iframe
Resolved in Pega Version 8.2.8
When using a radio button sourced with a pxTextinput using a Local List 'Yes' and 'No', the Assertion conditions were populated with incorrect data while a test scenario was being recorded, causing the test case run to fail. This was traced to the radio buttons being inside an iframe (dynamicContainer): when the scenario test was run, the radio-buttons group was rendered in an inner iframe that caused the document to refer to the outer document on the webpage instead the inner document. This has been resolved by adding handling to get the OwnerDocument of the DOMElement in domUtils's getDOMElementValue() and call getElementsByName on itso the references are correct.
INC-127347 · Issue 568022
GenerateAttachControl updated for iOS 13 compatibility
Resolved in Pega Version 8.2.8
It was not possible to upload files from an iPad using the Google Chrome browser when the "Attachments" control was used in the application. The attach control flowaction was not opening to select any files, and attempting to directly open the folder to add attachments showed them as grayed out. This was traced to the "Accept" tag not being supported in iOS 13, and has been resolved by removing accept= / from pzGenerateAttachControl .
INC-142557 · Issue 600532
Accessibility added to Recents
Resolved in Pega Version 8.4.4
Under all recent items, the work object was not opened when using the keyboard and the focus was on the work object. Clicking with the mouse worked. Investigation showed that on pressing the enter key, actions were not triggered because the action string was not on the same SPAN tag (but in child node). This has been resolved with an update to add tabindex on the same span where action-string is added. In addition, accessibility was not enabled on the out-of-the-box Recents table because the work object elements in the table used a formatted text control; this has been updated to use a link control which will enable the accessibility feature while using keyboard navigation.
INC-142557 · Issue 600529
Accessibility added to Recents
Resolved in Pega Version 8.4.4
Under all recent items, the work object was not opened when using the keyboard and the focus was on the work object. Clicking with the mouse worked. Investigation showed that on pressing the enter key, actions were not triggered because the action string was not on the same SPAN tag (but in child node). This has been resolved with an update to add tabindex on the same span where action-string is added. In addition, accessibility was not enabled on the out-of-the-box Recents table because the work object elements in the table used a formatted text control; this has been updated to use a link control which will enable the accessibility feature while using keyboard navigation.
INC-131151 · Issue 572831
Resolved empty body for Reject email
Resolved in Pega Version 8.2.8
When using the pzEmailActions Section in Correspondence for Approve/ Reject functionality via email, there was no reply body in the email for Reject Option. This was due to the flow action for the Reject email being different than that of the Approve email, and has been resolved.
INC-153537 · Issue 614847
Corrected popup placement for Microsoft Edge browser
Resolved in Pega Version 8.4.4
Autocomplete, date control and SmartInfo pop-ups were not displayed correctly when using the Edge browser. This was due to Javascript behavior differences with that browser, and has been resolved by updating the system to ignore the scrolltop if browser is Microsoft Edge.
INC-144311 · Issue 601110
Updates for nested "Append And Map To"
Resolved in Pega Version 8.4.4
Nested actions "Append And Map To" in Data Transforms were producing incorrect results when offline. This was traced to all operations being performed on the Page List which was on first level of nesting, which was caused by changing the Data Transform into JavaScript form for offline use. The JavaScript form of DataTransform uses variable the "targetListObj" to represent the Page List, and this same name was reused regardless of the "Append And Map To" nesting. An additional problem was seen with the "Update Page" Data Transform action when used with conjunction with a nested "Append And Map To" action: the action assumes that top level Pages exists, but "Update Page" did not create them. This caused the "Append And Map To" action to fail. To resolve this, the "Append And Map To" action will use suffixed variable names to reference nested PageLists, and "Update Page" will create the Page if it doesn't exist.
INC-134188 · Issue 576731
XML Parse handles dates with time zone correctly
Resolved in Pega Version 8.4.4
Due to a difference in data mapping behavior for Date values, the Parse XML new assembler implementation was incorrectly applying the DateTime type of processing for Date inputs when using timezones and silently ignored the exceptions reported. This has been resolved.
INC-139086 · Issue 597144
"Show next error" correctly displayed on user portal
Resolved in Pega Version 8.4.4
In the Case Worker user portal, the Show Next Error link was not shown when the layout group had a validate rule in the flow action. The same configuration worked as expected in Case Manager. This was a missed use case, and has been resolved.