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-124463 · Issue 186281
Customer Request Header mapping updated
Resolved in Pega Version 7.1.8
A Connect SOAP rule using Custom Request Headers to pass the wsse:Security, wsa:From, wsa:MessageID and wsa:Action fields was failing with the error "The server did not recognize the action which it received." Headers were mapped to a XML stream rule where the root node was mapped to a property, but the mapping was failing due to missing support to add the text node in addition to the elements. This has been fixed with code added to use getChildren() instead of getChildElements().
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.
SR-124620 · Issue 186205
Wild card support added to Elastic Search
Resolved in Pega Version 7.1.8
Elastic Search was not not working correctly for wild character search results. This was due to an error in the code and has been fixed.
SR-124631 · Issue 188702
Resolved class loading errors for XMLSignatureFactory
Resolved in Pega Version 7.1.8
Class loading issues caused errors when loading XMLSignatureFactory as an API. These have been fixed by adjusting the .jar file.
SR-124643 · Issue 188538
Added harness check for Live UI in UI Inspector
Resolved in Pega Version 7.1.8
Due to recent enhancements related to UI Inspector, the user interface (UI) was appearing distorted in the list view filter section. This was caused by a section not containing a required harness for the loaded library. Live UI Requires a harness, so code has been added to check if a harness is contained on the page, and if not it returns and the inspector does not initialize any logic.
SR-124683 · Issue 191853
Null check added to portal resizeActionIFrame API
Resolved in Pega Version 7.1.8
In some instances, the error "Unable to get property 'scrollHeight' of undefined or null reference" appeared when using a portal. This was due to a missing null check in the harness for the resizeActionIFrame API, which has now been added.
SR-124691 · Issue 186750
Resolved lost transaction ID while adding and deleting attachments
Resolved in Pega Version 7.1.8
When a file was attached and another one deleted at the same time from a work object, the session transaction was lost. Trying to approve the item generated the message "This action is not allowed as it is outside the current transaction". This was due to a stale transaction ID within the frame, and the FromFrame API has been updated to handle the delete attachment activity so the transaction session of parent frame does not get invalidated.
SR-124694 · Issue 186451
Added dynamic verification for XSD folder path
Resolved in Pega Version 7.1.8
An enhancement has been added to handle different URLs for schema definition XSD path in dev, test and production environments, allowing dynamic configuration of the XSD path in parse XML instead of requiring the absolute path.