The following new features are available:
Namespace support and XML/JSON conversion:
A new mapping table allows you to map an XML namespace to a JSON prefix that is added to the beginning of the JSON object name. The mapping works for XML to JSON as well as converting JSON to XML.
In order to customize the XML/JSON conversion, a new configuration table has been added which allows you to specify whether an XML element should always result in a JSON array type, even if the element occurs only once. In addition to that, logical data types are supported. In case that a value cannot be converted, a customizable default value can be used.
A new flag allows you to turn off logging of JSON messages.
Support for cross origin resource sharing (CORS) has been added.
REST adapter senders have now support for returning custom headers. The content of the header values can be static or extracted from the returned XI message.
Support for user filtering against the Access Control List (ACL) has been added.
Support for OAuth 2.0 Native Flow for Concur has been added.
treat as error (default)
skip current poll and retry later
use an empty token value
use the initial token value
use a custom token value
Custom error handling has been enhanced considerably. Also situations that are no errors can be handled; in particular, the following features have been added:
A new rule type Always has been added. This rule is always matching and will always be fired. Using this rule, you can, for example, set a customized HTTP success status code on sender side.
A new flag allows to inverse the rule expression. This allows rules like HTTP status code is not 200.
A new type of test has been added in order to match on an empty result. This allows rules like HTTP result is empty.
For receiver channels only, the following features have been added:
The result of the HTTP call is available in custom message text via variables (<http_status>, <http_status_text> and <http_result>).
All HTTP response headers are added now to the XI response message.
A new flag controls whether the receiver channel will follow redirects.
For sender channels only, the following features have been added:
All dynamic variables of the result message are available as variables and can be used in custom result messages.
The message result is available as variable (<message_result>) and can be used in custom result messages.
A new check box Allow public access has been added to the Channel Selection tab for sender channel configuration. If this checkbox is enabled, the sender channel allows all HTTP requests without requesting any authentication.
If a sender channel allows public access, it is possible to choose from which URLs CORS requests are allowed to come from.