INC-152283 · Issue 626399
Added handling for switching table context in a section
Resolved in Pega Version 8.6
After configuring multiple tables in a section with row-editing on master-detail, opening the detail section of one of the tables and clicking inside it and then trying to open the details of another table generated the error "Can not render section'. The section would render correctly if the browser was refreshed. Investigation showed this was due to the new section opening in the wrong context, and the system has been updated to support this use case.
INC-152340 · Issue 610909
Scrollbar consistent on switching between grids in tabs
Resolved in Pega Version 8.6
On switching between two grid tabs configured in a layout group of tabs, the scrollbars intermittently disappeared or doubled. This was traced to the initscrollbars function being called multiple times and adding hScrolldiv and vScrolldiv each time. To resolve this, the logic has been updated to recalculate the position style.
INC-152547 · Issue 619032
Check added for SPA portal
Resolved in Pega Version 8.6
When using the FlowAction "ToCancel" to proceed to the "Withdrawn" stage, the "Confirm" Harness was not opening in a custom Portal. This was traced to a missing NO_UI configuration for FlowAction, which for SPA portal meant its single page caused doc.submit to repaint the whole window/portal. This has been resolved by adding a check for the SPA case.
INC-152945 · Issue 613932
Skin rule applied correctly post-upgrade
Resolved in Pega Version 8.6
After upgrading from v7 to v8.5, attempting to apply the previous skin to the new application resulted in a java exception while saving. This was caused by null or empty values for the horizontalDividerHeight and verticalDividerHeight variable which were parsed as double values and led to a null pointer exception. To resolve this, null and empty checks have been added to GenerateFlexScreenLayout.java.
INC-153108 · Issue 614359
Added check to maintain disabled textarea 'when'
Resolved in Pega Version 8.6
The disabled text field became editable when the "Run required condition on client" checkbox was enabled. This has been resolved by adding a check for pyDisabled property to get the correct status for textarea control.
INC-153109 · Issue 611353
Validation error messages correctly cleared in nested markup
Resolved in Pega Version 8.6
A UI Freeze issue was seen whenever mandatory input was missed and the form was submitted. Continuing was possible after browser refresh, but a new Next>> button appeared. This was an unintended side effect of work done to correctly clear validation messages when areas had captions, and has been resolved by modifying that work so it performs as expected on nested markup.
INC-153152 · Issue 613686
Privilege on table cells updated for non-template mode
Resolved in Pega Version 8.6
When using a table sourced from a report definition where certain cells were hidden or shown based on privilege, the configuration worked as expected in regular tables but did not work correctly for optimized tables. This was traced to an issue with image control rendering in non-template mode related to privileges for the image, and has been resolved by updating the pzgenerateicon RUF.
INC-153163 · Issue 615112
Header present in timeout modal window
Resolved in Pega Version 8.6
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-153249 · Issue 614899
Check box group links and buttons made clickable
Resolved in Pega Version 8.6
After upgrading from v8.4 to v8.5, click actions did not have the same behavior when using the standard template pyCheckboxGroupTemplate section. In v8.4, clicking anywhere in the card body triggered the checkbox, but in v8.5 only clicking on the checkbox itself triggered it. This was due to the CSS for checkbox templates (in the py-design-template-styles CSS rule) being updated, and has been resolved by making the links and buttons clickable.
INC-153266 · Issue 630851
Error message after submit persists appropriately
Resolved in Pega Version 8.6
When a template grid was in a section of flow action that performed validation and then populated an error message on a primary page post-processing, the messages were unexpectedly cleared after a very brief period. Investigation showed the network request made by the template grid created a state page on server which was being cleared, and this has been resolved by adding an update that will pass pzKeepPageMessages as true in the network request so the error message will persist as expected.