Announcing the January 2020 release of Cloud Application Integration

Posted by Luc Clement Jan 14, 2020

We’re delighted to announce the January 2020 release of the Cloud Application Integration service. This release is feature rich. It is being rolled out across IICS regions on the following schedule:

14 Jan 2020 - North America NA1 and Asia Pacific APSE1
15 Jan 2020 - North America NA2 and EMEA EMW1
11 Feb 2020 - North America USW3
12 Feb 2020 - North America USE4 and USE6

Making it easier to implement and debug

Creating process objects had been tedious. We’ve made it easy to create multiple and hierarchical process objects simply by importing WSDL, XSD, or Swagger interface documents from a file, a zip or a URL. This will save you time and effort that previously required manual creation of process objects.

To help you debug processes the Assignment step now gives you access to field values controlled by a process’s tracing level. To turn up tracing without redeploying a process a new X-Debug HTTP header has been introduced. A value of “true” for this header enables you to debug a single process instance on the fly.

Tools like Postman, SOAPUI or RESTclient are great but require you to leave Process Designer to initiate a process. You can now create and associate with a process one or more JSON or XML process inputs and run a process with one or all inputs. You can then use the new process instance debugging capabilities to better analyze and identify the root cause of errors.

Making it easier to consume databases

We’ve turned your OData-enabled database into a fully-fledged REST API by not only exposing the power of OData v4 to perform paged queries, create, read, update and delete operations simply by enabling the OData service on the connection, but also by auto-generating a Swagger interface to this database's schemas. This makes it possible for developers to use the same approach to interact with databases as they do for any other REST API. You can also control where your OData-enabled APIs are accessible from now either from the Cloud, on premises or both.

We’ve also enhanced our JDBC connector’s query capabilities by allowing you to leverage database specific WHERE Clause syntax. This will allow you to leverage your database’s nested query and other database-specific query capabilities. You are no longer limited to the use of simple AND or OR WHERE Clauses.

Making it easier to consume JSON and XML content-types

Prior to this release unless the content type of responses was application/json or text/xml but considered to be XML or JSON, the payload was treated as an attachment. We’ve enhanced content type processing such that for example application/vnd.api#json;charset=UTF-8 is now processed as JSON content. We now process content types containing xml and json identifiers as XML and JSON respectively. This update is backwards compatible but we recommend you review the release notes for guidance.

Making it easier to work with attachments and multipart responses. We’ve added multi-attachment support for service connectors. This includes multipart responses containing both the body and attachments. Several new functions have been introduced to make this possible.

Making process recovery easier with Process Restart provides administrators and operators the ability to restart a process from the Application Integration Console.

Unique API name override for processes and taskflow now allows users to override the auto-generated API name with an API endpoint name of your choosing.

Please see the What's New document for details (also attached with this post).