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.
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.
SR-124700 · Issue 187999
Removed white space from edit data table
Resolved in Pega Version 7.1.8
The pop up to edit data table was displaying white space at the top left corner due to the CSS style pageTabLeft in file listvieweditor.CSS using a background-image with a width of 12px while the area to cover is 27px. This has been corrected.
SR-124747 · Issue 186549
Added fallback keyinfo handling
Resolved in Pega Version 7.1.8
When a SAML assertion response is received in the authentication activity, an error indicated the KeyInfo was missing in the signature. This was caused by a lack of redundancy in the keyinfo handling that caused an exception when keyinfo was not included in the SAML response. Support has now been added to check the certificate in the truststore where the certificate from IDP metadata would have been imported, and there is an added null check in the debug logs.
SR-124751 · Issue 186945
Element substitution corrected for Parse XML
Resolved in Pega Version 7.1.8
Element substitution was not working as expected on elements properly generated in the Element Substitution section of the XML tab of the Parse XML rules. This was an error in the multi-level element substitution where the Parse XML rule didn't execute because it as expecting to find another rule which isn't needed, and has been corrected with added code to build the node path and remove clearing of substitutable elements in cases of multiple nodes configured for substitution.
SR-124751 · Issue 188572
Element substitution corrected for Parse XML
Resolved in Pega Version 7.1.8
Element substitution was not working as expected on elements properly generated in the Element Substitution section of the XML tab of the Parse XML rules. This was an error in the multi-level element substitution where the Parse XML rule didn't execute because it as expecting to find another rule which isn't needed, and has been corrected with added code to build the node path and remove clearing of substitutable elements in cases of multiple nodes configured for substitution.