You can now select the Validate input and Validate output options to specify whether you want Integration Cloud to validate the input and output to the Integration, against the service input or output signature.

Some Integration Cloud Applications, for example, Salesforce CRM version 44, now support connectivity with streaming APIs and processing of streaming API events.

You can create a Salesforce CRM listener, select a subscription channel, and specify the Integration to be invoked on the incoming events. Additionally, you can configure the headers and parameters as well as enable and disable the listener. Once enabled, the listener receives the streaming API events and processes the received events.

The Salesforce CRM listener can subscribe and listen to Salesforce events. Salesforce stores standard-volume events for 24 hours, so for versions of Salesforce later than v37.0, you can retrieve the events if they are within the retention window. You can replay the lost events by selecting the following replay options:

The Salesforce CRM listener can now subscribe and listen to all event types, for example, Salesforce Push Topic Event, Salesforce Platform Event, Salesforce Change Data Capture Event, and Salesforce Generic Event.

You can now create a Flat File Application by defining a flat file structure either manually or from a sample file. You can then convert an inbound flat file to a document by invoking the predefined convertFlatFileToDocument operation in an Integration, or convert a document to an outbound flat file by invoking the predefined convertDocumentToFlatFile operation.

Integration Cloud allows you to write integration logic to integrate different types of applications. This logic can now be exposed to the external world using SOAP APIs. You can create SOAP APIs by using an existing set of Integrations (from scratch) or by using a WSDL file.

A SOAP API exposes one or more Integrations as operations, so each operation in a SOAP API corresponds to an Integration.

Using a SOAP client, you can invoke the SOAP operation externally by using either Basic Authentication or 2-way SSL. When the SOAP operation is invoked, the associated Integration gets executed.

You can now connect to a database using the new Database Application and perform database operations with cloud databases.

You can now upgrade any product in a solution to the available higher fix version after you create the solution. The Upgrade option appears if a higher fix version is available for any of the products in the solution. The latest fix version will appear in the Fix version drop-down list.

While creating a solution, after you select a fix version, webMethods Integration Server packages such as WmCloudStreams and WmJDBCAdapter will appear in the Packages group box based on the selected fix version. You can select the packages that you want to enable.

Cloud Deployment capability is now enabled by default for all tenants. As soon as you register, 3 CPU cores and 6 GB memory are allocated for all tenants. Provisioning happens if you access Cloud Deployment for the first time using the application launcher. Solutions created using a trial account are deactivated daily. After you log in, you need to reactivate the solutions. All assets will be available after a short delay.

Deploy webMethods CloudStreams assets

You can now deploy CloudStreams provider packages, CloudStreams connector services, CloudStreams connection, and CloudStreams connector listeners to a solution in Cloud Deployment and view those assets. This is applicable only if you have selected WmCloudStreams as the package option while creating the solution.

Within a tenant, you can now promote assets from a solution to another solution, from a previous stage to the current stage, for the same runtime type. You can promote assets if the source runtime version is lesser than or same as the target runtime version.

When you run a service in Software AG Designer, you can save the pipeline data as an XML document to your local file system. After you deploy the service in Cloud Deployment, you can now click the Load Data option in the service editor in Cloud Deployment to load or update the pipeline data and test the service.

You can now download user deployed packages and configurations from the Assets page. The assets will be zipped and downloaded to your local storage space.

From the Asset Repository page, you can either download individual packages or download the whole repository for each product. The assets including ACDL files will be zipped and downloaded to your local storage.