Release 10.5
Added Services
pub.client:restClient Creates and sends REST API requests over HTTP or HTTPS. Integration Server generates the REST connector services while creating a consumer REST API descriptor and calls this service while executing any REST connector service.
pub.compress:compressData Compresses the data before sending the HTTP request using any of the specified compression schemes.
pub.compress:decompressData Decompresses the data based on the response header of the HTTP response.
pub.datetime:build Builds a date/time string using the specified pattern and the supplied date/time elements.
pub.datetime:increment Increments or decrements a date and time by a specified amount of time.
pub.graphql:load Loads data for a single key using Dataloader.
pub.graphql:loadMany Loads data for multiple keys using Dataloader.
pub.mqtt:publish Publishes an MQTT message to an MQTT server.
pub.mqtt:triggerSpec Specification for the signature of an MQTT trigger service.
Deprecated Services
pub.date:dateBuild Use pub.datetime:build.
pub.date:dateTimeBuild Use pub.datetime:build.
pub.date:incrementDate Use pub.datetime:increment.
Changed Services
pub.client:http The default value of the Accept header is now controlled by the watt.net.default.accept server configuration parameter. Previously, the default value of the Accept header was: "image/gif, */*"
pub.xml:documentToXMLString Adds the input parameter preserveRefs which indicates whether the leading & (ampersand) of a well-formed entity or character reference is left as & or further encoded as & when the data is to be HTML-encoded.
pub.xml:xmlStringToXMLNode Adds input parameter validateXML which indicates whether the service validates the incoming XML document to ensure it is well-formed XML before converting it to a node.
pub.client:restClient The service now includes “OAUTH” and “APIKEY” fields as “type” for the “auth” input parameter. For this purpose, the service now includes the support of “token” and “apiKey” fields as “type” while using “OAUTH” and “APIKEY”.
The service also includes the support of the “secure” input parameter and the “trustStoreAlias” field so that users can specify the truststore information for certificate validation.