INC-181089 · Issue 673460
Corrected modal focus on assignment open
Resolved in Pega Version 8.7
After opening an assignment and using keyboard navigation, the focus was not set on the first focusable element as expected. Hitting "TAB" set focus to the second focusable element. This was traced to previous work done on focusing elements under the modal, and this has been resolved by removing the "document.activeElement.blur()" as it is no longer needed.
INC-171121 · Issue 648130
Filter popup persists correctly
Resolved in Pega Version 8.7
When the Apply filter option was selected for a table configured with a page list property as source, the filter popup appeared on the screen but disappeared after 3 to 4 seconds. This has been resolved by enabling the stretch for tabs option in the layout group.
INC-193775 · Issue 686645
Action Sets in Sections working as expected
Resolved in Pega Version 8.7
When adding actions to a table, the action sets were not always saved correctly. Sometimes actions from one actions set were moved to a new action set without any event, which seemed to occur when there were multiple actions defined for each action set. This was traced to the open of the table property panel in the activity Embed-Harness-SectionBody-Grid.pzGridActionSets activity. This activity sets data for the action set display, including setting a “pyKeyCode” property. The “pyKeyCode” property is not set correctly in certain scenarios, causing the selected action/behavior to not be saved correctly. This has been resolved by changing the local param-pzGridActionSets: TempKeyCode to string.
INC-167704 · Issue 671630
Email timing updated to ensure content captured
Resolved in Pega Version 8.7
Outbound email replies constructed using a pyReply section were intermittently blank if the 'Send' button was clicked immediately after adding text. This was traced to the blur not happening immediately on click of the submit button, and has been resolved by introducing window.blurDelay to ensure the data is captured. The delay time is configurable, and by default is set to 200ms.
INC-168414 · Issue 641036
Web Mashup works from nested iframe
Resolved in Pega Version 8.7
Web Mashup was failing with the error "Browser cookies must be enabled for PRPC Internet Application Composer to function" when it was configured within a nested iframe setup. This has been resolved by adding a cookie check and the appropriate handling for this usecase.
INC-176971 · Issue 658300
Web Mashup works from nested iframe
Resolved in Pega Version 8.7
Web Mashup was failing with the error "Browser cookies must be enabled for PRPC Internet Application Composer to function" when it was configured within a nested iframe setup. This has been resolved by adding a cookie check and the appropriate handling for this usecase.
INC-179752 · Issue 659880
Web Mashup works from nested iframe
Resolved in Pega Version 8.7
Web Mashup was failing with the error "Browser cookies must be enabled for PRPC Internet Application Composer to function" when it was configured within a nested iframe setup. This has been resolved by adding a cookie check and the appropriate handling for this usecase.
INC-171352 · Issue 653691
Focus set correctly on the modal window in theme-Cosmos
Resolved in Pega Version 8.7
In theme-Cosmos with touch enabled, clicking on a button to open a modal window set the focus on the background instead of in the modal window, forcing tabbing through the full page to reach the modal window. This was traced to the templates not using the pzModalCancel control which has the necessary container_close for the modal dialog close icon, and has been resolved by adding a check to set the focus correctly.
INC-175322 · Issue 658650
Focus set correctly on the modal window in theme-Cosmos
Resolved in Pega Version 8.7
In theme-Cosmos with touch enabled, clicking on a button to open a modal window set the focus on the background instead of in the modal window, forcing tabbing through the full page to reach the modal window. This was traced to the templates not using the pzModalCancel control which has the necessary container_close for the modal dialog close icon, and has been resolved by adding a check to set the focus correctly.
INC-179683 · Issue 664452
Handling added for decoding file names containing umlauts
Resolved in Pega Version 8.7
Two issues were seen with file names that contained an umlaut: When sending file with an umlaut in the name via PegaCHAT, the error "Failed to load resource: the server responded with a status of 404 (404)" appeared on the Client side and a preview was generated. On the Agent side, the message was sent but attempting to open it resulted in an error that the file did not exist. This was traced to the unescape javascript API returning the wrong decoded values if the encoded value of an umlaut character was sent, and has been resolved by adding a safe check to avoid a malformed URI. Second, an image was not displayed in the Rich Text Editor if the image name contained the ä or Ä character in it. Investigation showed the activity parameters were being changed when it was invoked from the script. If the file name sent was "aysnÄ1626292145235.png" it was encoded to "aysn%C3%841626292145235.png" as expected, but when the parameter was passed to the Activity the value further changed to "aysn%C3%83%C2%841626292145235.png", causing the file open failure because the names did not match. To resolve this, code has been added which will correctly decode the encoded values of umlaut characters.