SR-124005 · Issue 185470
Fix inserted for CaseWorker portals using Microsoft Internet Explorer 8
Resolved in Pega Version 7.1.8
CaseWorker portal links to open and interact with cases were not working in the Microsoft Internet Explorer 8 browser. This was caused by the method used to get the dynamic container not being supported by Microsoft Internet Explorer 8, and has been resolved by changing the querySelector to get the proper class names.
SR-124007 · Issue 187210
Added handling for NPEs on mobile devices
Resolved in Pega Version 7.1.8
Answering a questionnaire on a mobile device was generating the error "NullPointer in SafeURL.put()" due to the source element being a radiobutton div and not sending the request for postvalue. This was a missing condition in the initiatepost method of pega_ui_events for handling NPEs on mobile and the system has been modified to correct this.
SR-124007 · Issue 187611
Added handling for NPEs on mobile devices
Resolved in Pega Version 7.1.8
Answering a questionnaire on a mobile device was generating the error "NullPointer in SafeURL.put()" due to the source element being a radiobutton div and not sending the request for postvalue. This was a missing condition in the initiatepost method of pega_ui_events for handling NPEs on mobile and the system has been modified to correct this.
SR-124011 · Issue 184792
Repaired Case Designer rendering for Microsoft Internet Explorer 8
Resolved in Pega Version 7.1.8
When using the Microsoft Internet Explorer 8 browser, opening a case type in Case Designer which has steps in the stages did not render the steps. This was caused by a CSS file fragment that was not picking up the proper base styles, and has been fixed.
SR-124151 · Issue 184994
Next button behavior in a modal dialog corrected
Resolved in Pega Version 7.1.8
A workflow issue was found with the 'Next' button on a last row of a repeating grid where clicking on the 'Previous' button would then improperly make available a previously grayed out 'Next' button. Similarly, clicking the 'Next' button on the next-to-last row fired the validation but then disabled the 'Next' button. This was traced to the "NextDisabled" parameter being set incorrectly in case of server side errors, and has been fixed.
SR-124382 · Issue 187227
Corrected image resize for RTE
Resolved in Pega Version 7.1.8
In some cases, it was not possible to resize an image in RTE. This was traced to the image plugin setting the height and width for auto resize, and has been changed so the setup and commit function in ckeditor_extras do not set dimensions for auto resize and retain the width and height if specified.
SR-124382 · Issue 185471
Corrected image resize for RTE
Resolved in Pega Version 7.1.8
In some cases, it was not possible to resize an image in RTE. This was traced to the image plugin setting the height and width for auto resize, and has been changed so the setup and commit function in ckeditor_extras do not set dimensions for auto resize and retain the width and height if specified.
SR-124420 · Issue 187126
Flow actions resolved for hidden buttons passing parameters
Resolved in Pega Version 7.1.8
After upgrading, parameter passing to activities from button controls no longer worked and passed an empty string which made other functionality relying on it fail. This occurred due to the default flow action buttons being configured to be hidden, and affected scenarios where a mix of auto and non-auto generated controls existed in old containers. This has been resolved by adding HTML code that specifies inclusion in case of default buttons being hidden.
SR-124450 · Issue 188191
Added alternate method for sorting and filtering listview fragments with Microsoft Internet Explorer 9
Resolved in Pega Version 7.1.8
Using Microsoft Internet Explorer 9, sorting and filtering were not working after upgrade in ListView using the WorkListViewSelector in the Fragment tab of the ListView. This was due to the version of EventListener not being supported for Microsoft Internet Explorer 9 and lower browsers so a check has been added that will call the old methodology of calling window.attachEvent for these functions.
SR-124602 · Issue 188311
Page scroll reset to top for next page
Resolved in Pega Version 7.1.8
When a screen in a flow was scrolled to the bottom and the "next" button clicked, the next screen was displayed with the page already scrolled to the bottom. This unexpected behavior was caused by the flow being executed on a page inside an iframe, and the parent page was unaware of any changes made in the iframe. To correct this, the ui_doc initialize API has been updated to set the scroll top.