SR-124473 · Issue 186179
Added handling for unauthenticated asynchronous SOAP service
Resolved in Pega Version 7.1.8
After implementing changes to work around an error with SOAP authentication, the unauthenticated asynchronous SOAP service generated an error and failed to complete. This was due to the changes to the authentication process omitting the asynchronous mode case when a SOAP service that intended to not use authentication ends up calling a sub-activity that requires authentication. This use case is now covered.
SR-124477 · Issue 187138
Logic updated for Ruleset Refactor - Merging Ruleset
Resolved in Pega Version 7.1.8
When using the rule set refactor wizard to merge the rule set from lower version to higher version, the wizard did not show the rules in the source rule set on the second screen (Rules Impacted are "0") which had a number of rule conflicts. In addition, the error "StringIndexOutOfBoundsException" was logged. This was caused by the RuleSetMaintImpl buildRuleSetInventory method not filtering out data instances correctly, causing errors when trying to validate a Data instance as a rule. This has been corrected.
SR-124580 · Issue 192241
Changes made to Save preferences option in SummaryView to retain filter values
Resolved in Pega Version 7.1.8
In the reports filter section, even after clicking on save preferences button the selected filter values were not retained the second time. In the SavePreferences activity, pyAdvicetext was set to pyLabel and caused the selected filter value to not be stored. To correct this, changes were made to the SavePreferences and getPreferences activities: In getPreferences, pyAppName is set to advicetext if its length is more than zero or set to pyAppname from primary page if not. Also, in the SavePreferences activity, pyAdvicetext is set to local.adviceText (previously it was set to pyLabel).
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-124676 · Issue 186204
Save As' for Declare Expressions with IF corrected
Resolved in Pega Version Pega Platform, Resolved in Pega Version 7.1.8
The IF conditions were collapsed or vanished when attempting to use the 'Save As' functionality for Declare Expressions. To correct this, the Embedded Rule data transforms which were unintentionally calling superclass data transform have been modified.
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.