SR-130352 · Issue 199182
Corrected Microsoft Internet Explorer error for opening harness in a popup
Resolved in Pega Version 7.1.8
Configuring a button click to launch a harness in a pop-up with the Microsoft Internet Explorer 11 browser caused the error "Internet Explorer cannot display the webpage." The cause was an errant space included in the pega.u.d.url for this browser, and the GenerateHarnessHTML and GenerateLayout RUFs have been updated.
SR-131269 · Issue 200188
Fixed Harness buttons and screen resize issue
Resolved in Pega Version 7.1.8
Harness buttons were not fixed, and the screen was resizing to unviewable height on changing to screen layout. To resolve this, CSS changes have been applied to the pzbase-browser - CSS and pzbase-ie9 - CSS files to include selector for dynamicContainer div inside workarea div in not size to content mode. The rule applied is position: absolute.
SR-122860 · Issue 183998
Added conversion of Turkish characters for Google Chrome
Resolved in Pega Version 7.1.8
Google Chrome was not correctly converting Turkish characters, causing JSON parse exceptions. In order to handle this localization, the system will check whether Google Chrome is being used, and if so will replace selective characters ( Turkish - İIŞĞÜÇÖ ) using a regex. Letters replaced are { "İ": "i", "I": "ı", "Ş": "ş", "Ğ": "ğ", "Ü": "ü", "Ö": "ö", "Ç": "ç" }. Other browsers are not affected.
SR-122860 · Issue 182083
Added conversion of Turkish characters for Google Chrome
Resolved in Pega Version 7.1.8
Google Chrome was not correctly converting Turkish characters, causing JSON parse exceptions. In order to handle this localization, the system will check whether Google Chrome is being used, and if so will replace selective characters ( Turkish - İIŞĞÜÇÖ ) using a regex. Letters replaced are { "İ": "i", "I": "ı", "Ş": "ş", "Ğ": "ğ", "Ü": "ü", "Ö": "ö", "Ç": "ç" }. Other browsers are not affected.
INC-186072 · Issue 678753
Updated ClientDynamicData HTML Rule
Resolved in Pega Version 8.7.2
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-188141 · Issue 678158
PD4ML upgraded
Resolved in Pega Version 8.7.2
Issues with PDF generation have been resolved by upgrading PD4ML to version 4.0.13.
INC-188644 · Issue 708959
Autocomplete cancel closes correctly
Resolved in Pega Version 8.7.2
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-190233 · Issue 675485
Production check removed for Get Action Details API
Resolved in Pega Version 8.7.2
After creating an assignment for a case and calling the Get Action Details Applied Assignment API, the name tag for views was not included in the returned JSON. This has been resolved by removing a check for production level.
INC-190855 · Issue 681092
Duplicate items resolved for questionnaires
Resolved in Pega Version 8.7.2
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-194415 · Issue 710824
Improvements for dirty popup
Resolved in Pega Version 8.7.2
Multiple issues have been addressed for dirty popups. 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. 2) Attempting to work around the previous issue by clicking "Do not display dirty warnings" only worked the first time it was tried. With this change in place, opening the assignment, making a change, then clicking Home, caused the pop up to appear as desired, but opening the assignment again and making a change, then clicking Home again did not prompt the dirty pop up. This was due to the click handler getting hit twice, leading to the already open dirty dialog being closed during the second call to the function 'isFormDirty' in pzpega_ui_doc_actionRouter.js file, and this has been resolved. 3) When attempting to close the case as a draft, clicking the save button caused the system to keep loading for a few minutes without sign of completing the save process and eventually the browser had to be closed. The content was saved, but the system was not able end the loading screen. This was caused by an incorrect harness context which caused the "SubmitInProgress" flag to be true on the incorrect harness context so the modal was not dismissed. To resolve this, on clicking the "Save" button, after the confirmation modal is closed, the pega.u.d.isDirtyDialogOpen will be reset to false.