SR-132880 · Issue 201431
Design time clarification for radio button configurations
Resolved in Pega Version 7.1.8
Previously, it was possible to configure an on-click event on a radio button in a repeating grid. This configurability was an error - although it was possible to set it up, the actions would not actually fire as intended due to the way the radio buttons work. In order to remove confusion, the actions tab for radio buttons has been removed from design time and checkboxes should be used if on-click actions are desired.
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-131217 · Issue 199744
Stopped unexpected trigger caused by attaching note with gadget
Resolved in Pega Version 7.1.8
Declarative rules were being fired every time a note was attached to a work object using the "Notes" gadget (not advanced notes link). To fix this, the pxAttachNote activity has been updated to not trigger the declarative chaining in this scenario.
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-131612 · Issue 200253
Handling added for accent characters in DataTable editing
Resolved in Pega Version 7.1.8
When a DataTable had a key value with an accented character like "é", clicking on the "Open this item" icon to edit the row displayed a blank page in the editor. This was caused by the escape method of native JavaScript being deprecated, and the system has been updated to use encodeURIComponent method instead.
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.