New in this release
Fixed a bug that caused runtime errors when you added headers to a request or response (using actions like “AddHTTPHeader_ToRequest” and “AddSOAPHeader_ToResponse”) without calling “RegisterInspectHeaders” beforehand.
You can now pass arbitrary XML text in the Value input parameter of actions that add SOAP headers (“AddSOAPHeader_ToRequest” and “AddSOAPHeader_ToResponse”). This text will be included inside the SOAP header element.
Changes
Actions that return headers from the request/response now throw a descriptive runtime error message when the “RegisterInspectHeaders” action wasn’t previously called, which is mandatory. In the previous version of the component, this resulted in an unhelpful generic error.Updated the “RegisterInspectHeaders” action description, because it incorrectly stated that, if it was not called, you would get empty lists from actions returning headers from the request/response.
Breaking changes
Due to the new support for adding XML content in SOAP headers (mentioned above), the “AddSOAPHeader_ToRequest” and “AddSOAPHeader_ToResponse” actions now first try to parse and send the “Value” input parameter as XML. This might break some usages of these actions if you were previously sending XML as escaped, plain-text.
The component is now distributed as an OutSystems application package for easier installation.