SR-123961 · Issue 184528
New Stylesheets save to harness correctly
Resolved in Pega Version 7.1.8
Stylesheets added to the StyleSheetName pageList were not getting saved in Harness rule. This was traced to the process not updating the primary page on clipboard, and has been corrected.
SR-124004 · Issue 186135
Timing improved for delegated strategy rule editing
Resolved in Pega Version 7.1.8
After saving a strategy rule to an unlocked production ruleset and adding that version to My Favorites, it was not possible to checkout the rule. When the refresh/reload button (only button displayed on the rule toolbar) was clicked, a StringIndexOutOfBoundsException message was generated. The root cause was a timing issue due to system slowness that prevented the display of the toolbar icons, and code has been implemented to increase the timeout for 'openRuleINprogress'.
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-124198 · Issue 184897
Clarified messages for attachment deletion failure
Resolved in Pega Version 7.1.8
When trying to delete an attachment on the work item without proper authorization, the tracer shows a message being added on TempAttachmentPage in Work- DeleteAttachment activity reading "You are not authorized to delete instance DATA-WORKATTACH-FILE ATPEGA-TASK ". However, this message was not being propagated to the screen and the screen was refreshing as if it worked despite the failure. To clarify the actual results, the DeleteAttachment Activity has been modified to present any messages and to avoid page removal of the TempAttachmentPage and TempLinkPage if there is a message.
SR-124206 · Issue 186503
Clarified handling of unlocked work objects in multinode environments
Resolved in Pega Version 7.1.8
Release lock was not working correctly on a multinode environment. When trying to release the lock from same operator different requestor from different nodes, the error "Unable to unlock this work object" was generated. In a multinode environment, system pulse takes time to update the cache across the nodes, hence the option is not effective immediately. Messaging has been updated to reflect this delay. Once System pulse executes then other requestor will be able to work on this item.
SR-124232 · Issue 185697
Addressed issue with Advanced Notes attachments reopening the work object
Resolved in Pega Version 7.1.8
When a user attaches a note using the "Advanced" option, as part of the out-of-the-box activity it is recreating/retrieving the work object back from the database and causing any changes to the work object done prior to attachment to be lost. The issue was that the SaveNote activity InsHandle parameter was set but the PageName parameter was not, and the system would reopen the workobject assuming it was not in the workobject context. To solve this, the PageName parameter is now set in the SaveNote activity so that the AttachNote does not do an open of the workpage.