INC-189748 · Issue 701458
Websocket disconnect code logged
Resolved in Pega Version 8.7.1
An update has been added which will log the websocket disconnect code for additional diagnostic information.
INC-190609 · Issue 681324
Added null check for routeToParent in Mashup
Resolved in Pega Version 8.7.1
After update, mashup was loading in a different context. This has been resolved by adding a null check in routeToParent in webwb_pega_desktop_support.
INC-190708 · Issue 695488
Save works on Ajax container without Dynamic container
Resolved in Pega Version 8.7.1
After opening a work object and making changes to a required field, pressing the save button did not give any visual indication that the save was performed. Hitting cancel generated a dirty pop up saying changes will be discarded, indicating no save was done. When an Ajax container is configured without a Dynamic Container, all the content is rendered inside a fieldset tag instead of a form tag. While performing the save, the API was looking for the form element in the document and could not find any, and the save failed. This has been resolved by updating the submitWhenFail() API to handle both fieldset and form elements in the dom.
INC-191160 · Issue 685378
Empty caption value not shown in dropdown list
Resolved in Pega Version 8.7.1
An update has been made to template_dropdown to restrict an empty value from being added to the list.
INC-191785 · Issue 680930
Edit Validate Rule works after mobile section collapse
Resolved in Pega Version 8.7.1
It was possible to collapse a section of the UI on the mobile app and then proceed to the next page without entering valid data. This has been resolved by updating the validation condition to handle the mobile sections edit validate rule correctly.
INC-192813 · Issue 684735
Corrected unexpected page refresh
Resolved in Pega Version 8.7.1
When a value was changed in a section where the source of the section was defined as a property, the page refreshed without any announcement and focus was disrupted. Investigation showed this happened when using paragraph control where an anchor tag was used without any Name attribute. An update has been made to explicitly set the gFocusElement property after the processAdditionalFields activity to resolve this issue. Because the Name attribute is needed to query the particular element from the DOM to focus back, there were also intermittent issues when using the Microsoft Edge browser with Windows OS even after adding Name in the paragraph control link. A setTimeout has been added before focusing the element to resolve this.
INC-193047 · Issue 697578
Added handling for nested clipboard pages
Resolved in Pega Version 8.7.1
On save of sections that have items (cells) nested more than one layer deep and have either "Show menu" or "Run data transform" actions, silent errors were found in the tracer indicating "Attempting to access a rule with a bad defined-on class: Trying to open rule ... of class "Rule-Navigation", but no defined-on class (pyClassName) was specified". This was due to the pzActionShowMenu Rule-Utility-Function and pzActionRunDataTransform Rule-Utility-Function assuming the clipboard page structure was only one layer deep, and has been resolved by using findRulePageFromCurrentPage from SectionUtils.java
INC-194239 · Issue 685735
JAWS reads characters limits in grid text area
Resolved in Pega Version 8.7.1
A text area in a grid with a character limit was not reading the maximum characters and remaining characters when using JAWS. This has been resolved by adding the necessary aria attributes to the non-template text area control.
INC-194415 · Issue 692824
Visibility improvements for dirty popup
Resolved in Pega Version 8.7.1
While working on an assignment, making a change and then clicking on the left navigation (Home, Dashboard) did not show the dirty pop up as expected, and the change was lost. The dirty pop up did appear on the Cancel button and Actions within the case. This has been resolved by improving the context switching for visibility of the dirty pop up.
INC-195321 · Issue 684971
Check added for readonly header control
Resolved in Pega Version 8.7.1
After configuring an optimized grid and adding a checkbox control in the header with editable options, when the control in corresponding column was configured as Auto, the checkbox in the header was rendered as read-only. When the control in the corresponding column was configured as "Read-only always" or displayText control was used, the checkbox was rendered as editable control. This was traced to a missing check for pyEditOptions = "Read-only", and has ben resolved.