INC-153163 · Issue 615113
Header present in timeout modal window
Resolved in Pega Version 8.4.5
After upgrade, the header was missing in the session timeout modal dialog when using the pzDisplayModalDialog FlowAction with the pzDisplayModalDialog HTML Rule. This was traced to the title value fetched from HTML not being set for use in the onload function of iframe, and has been resolved by ensuring it is handled by the pzDisplayModalDialog HTML rule.
INC-153318 · Issue 621363
Check added to match time zone for Time Picker
Resolved in Pega Version 8.4.5
Time picker popup was showing minus 5 hours from the actual value in the time input field, though the value was updated correctly in the clipboard. The console error "Unchecked runtime.lastError: Could not establish connection. Receiving end does not exist." was seen. This only happened when using the non-template mode of the Datetime control and configuring it with TimeOfDay property with the combination of Allow text entry as "No" and onchange event as Refresh-Section. The issue was not seen if Allow text entry was "Yes" from the presentation tab or if the event action "Refresh-section" was removed. This was caused by the markup process using the operator time zone to format the value but the default time zone (GMT) for the data-value. This has been resolved by adding a check in non-template mode so the value markup will be generated using defaultTimeZone.
INC-153643 · Issue 621713
Dynamic layout group text area correctly rendered as editable for page list type
Resolved in Pega Version 8.4.5
A text area configured in one section with Edit Options set to 'Auto' had the text area field appear as Read Only at runtime. The section included an embedded sub-section where a Dynamic Layout Group (Tab) was configured with Source set to "Property", and the text area correctly appeared as editable in the wrapper section if the Dynamic Layout Group (Tab) was removed from the sub-section. This was caused by the section content for the dynamic layout group not being handled for page list type, and has been resolved.
INC-154824 · Issue 620921
Check added for hidden field during validation
Resolved in Pega Version 8.4.5
When using custom validation for a future date, after certain steps the message "value cannot be blank" was displayed even though there was a value in the date control. This was traced to the validation also being performed on a hidden field, and has been resolved by adding a condition in pega_validators to check for hidden fields when running the validation.
INC-154860 · Issue 626098
Corrected extra space from harness child elements
Resolved in Pega Version 8.4.5
After upgrade from v7 to v8, extra space was seen at the bottom of harness content. This was caused by the header and footer heights being included two times while calculating mashup height, and has been resolved by updating the postMashupHeight method to skip including the header and footer height while iterating child elements for harness-content-workarea-view.
INC-154977 · Issue 622802
Added hidden field validation for offline app
Resolved in Pega Version 8.4.5
An enhancement has been added to handle the usecase of offline apps needing to validate hidden fields. This will be handled through the new flag "pega.u.d.validateHiddenFieldsInOffline".
INC-155070 · Issue 637578
PDF generation corrected
Resolved in Pega Version 8.4.5
Issues with PDF generation have been resolved by upgrading the PD4ML libraries to version 4.0.9fx5.
INC-155406 · Issue 638702
Clipboard security updated
Resolved in Pega Version 8.4.5
Security has been enhanced for clipboard properties by restricting registration for readonly properties.
INC-155855 · Issue 620575
Safe check added to modal window pop-up cancel
Resolved in Pega Version 8.4.5
On click of a link to add items to the rows by selecting the page list from pop-up window, clicking on the cancel button generated a node name undefined error after which clicking the link would not open the pop-up window at all. This was traced to the pre-processing activity in the flow action used to copy page list from one page to other, and has been resolved with the addition of a safe check.
INC-156826 · Issue 625436
Logic updated for adding new child/sibling to hierarchical paginated tree/grid
Resolved in Pega Version 8.4.5
When using a hierarchical table with pagination enabled, navigating to the last page and attempting to add a new child or sibling produced unexpected results. Navigating to the last row, selecting child, and clicking 'add sibling' caused a new row to be added. Adding a child caused the child elements to be added on top instead of at the bottom. This was a missed use case for adding a child/sibling when using a paginated tree/tree grid, and has been resolved.