INC-186072 · Issue 677409
Updated ClientDynamicData HTML Rule
Resolved in Pega Version 8.8
After upgrading from Pega 7 to Pega 8, attempting to open an assignment on the staging environment showed a blank page. This was traced to the system trying to open a declare expression of "PegaComm-" class, and has been resolved by updating the pzClientDynamicData HTML Rule handling for the top level page and enabling the expression calculation checkbox in the Advanced tab of the pyCaseManger7 harness.
INC-186081 · Issue 707804
Report filter popup displays correctly
Resolved in Pega Version 8.8
The filter popup was not displayed on the report column for which the filter was intended. This has been resolved by updating the popover js to fix the overlay issue.
INC-187756 · Issue 671837
Corrected close button screen reader accessibility
Resolved in Pega Version 8.8
The screen reader was reading 'close button' as 'close modal button'. This was traced to a lack of a visual focus indicator, and has been resolved by using the pyFlexModalTemplate for local action which uses close button and has the capability to set default focus on close button. This change affects all local actions in pyWorkCommonActions.
INC-188029 · Issue 691100
Rich Text Editor will pause until instance is ready for interaction
Resolved in Pega Version 8.8
Outbound email was intermittently appearing blank creating replies using pyReply section. This was traced to the Rich Text Editor not loading completely before the interaction, and has been resolved by adding a brief pause that will temporarily disable the Rich Text Editor until the instance is ready.
INC-188141 · Issue 678159
PD4ML upgraded
Resolved in Pega Version 8.8
Issues with PDF generation have been resolved by upgrading PD4ML to version 4.0.13.
INC-188644 · Issue 708960
Autocomplete cancel closes correctly
Resolved in Pega Version 8.8
Clicking on an autocomplete field and navigating to the next tab without selecting any values caused the autocomplete results to be displayed in the next screen until there was a click or an action was performed in that screen. This was due to the autocomplete not closing correctly, and has been resolved by removing the event.cancelBubble setting.
INC-189413 · Issue 701847
Moment timezone library updated
Resolved in Pega Version 8.8
After the Volgograd, Russia, timezone was changed, SA-103080 errors began to appear. This has been resolved by updating the moment timezone library to version 0.5.34.
INC-190708 · Issue 688135
Save works on Ajax container without Dynamic container
Resolved in Pega Version 8.8
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-190855 · Issue 718483
Duplicate items resolved for questionnaires
Resolved in Pega Version 8.8
When there was only one question page for a questionnaire, the question page title was being displayed twice and the breadcrumb showed duplicate steps. When there was only one step in the screen flow, the survey navigation was hidden. This has been resolved.
INC-191756 · Issue 718549
Corrected dashboard focus highlighting
Resolved in Pega Version 8.8
Dashboard links like "My activities"/"My cases"/"Recent"/"Search” were displayed with a yellow focus highlight even though the user was not currently in those screens. Investigation showed the data-menu-id for control_menu was being appended with the workid until selecting another tab caused it to reset to its original value without workid. This change in menu-id was responsible for the issue with focus, and occurred only when render as single checkbox was unchecked. This has been resolved by removing workid from menuid and adding a unique id for the outside menu and inside case same menu.