Item | Description |
Integration workspace enhancements |  On the Integrations page, you can now click the  icon to see the details of an Integration, click the ellipsis  icon to delete or copy an Integration, point to the  icon to view the scheduled status, scheduled type and when is the next scheduled execution date and time, and to the  icon to view the request URL.The look and feel of the blocks have been enhanced and the size of the blocks reduced to increase the work space.You can now copy a block from an integration and paste that block in another integration across projects. Currently, blocks cannot be pasted across different browsers or across domains.The  icon has been removed from the blocks. The Copy, Delete, Comment, Disable, and Duplicate options are now available by right-clicking on a block.The Modify Mapping ( ) option now opens the pipeline data window for mapping. Further, mapping arrows have been removed from the source and target fields in the mapping window. |
Monitor page enhancements | On the Dashboard page, you can now filter the execution details of Integrations based on the invocation channel, for example, Scheduler, User Interface, HTTP Interface, REST APIs, SOAP APIs, and Listeners. The in-progress executions can also be filtered based on the invocation channels.You can now terminate multiple in-progress integration executions from the Dashboard page by selecting the in-progress integration executions and clicking Terminate.On the Execution Results page, you can now select the Invocation channel for which you want to view the integration execution results. You can select All Invocations, All Projects, and All Integrations, if you want to view the execution details of Integrations based on all the invocation channels, for all integrations, and in all projects in the active stage, for the specified time period.The performance and responsiveness of the Monitor screen to high volume of data have been enhanced. |
Flat File enhancements | Integration Cloud now supports flat files that do not have a record identifier. You can select the Yes or No options on the Flat File Definition page depending on whether the flat file contains or does not contain a record identifier. The following options appears on the Flat File Definition page if you select Yes: Start at position - Identifies the character position in the record (counting from zero) where the record identifier is located.Nth field - Identifies the field in the record (counting from zero) that contains the identifier. |
Support for changing the Authentication Type | While editing an Account in any stage, you can now select a different Authentication Type without impacting any integrations. So if an integration is using an Account with a specified Authentication Type, the integration will now run with the changed Account configuration. Further, while editing or creating an Integration, after you select the Operation, the Account field now lists all the Accounts that are supported for the execution of the selected Operation. While testing the Operation, you can select another Account created with a different Authentication Type, if the Account is supported for the execution of the selected Operation. |
Support for clearing storage locks | If the environment goes down while an integration is running, the lock taken on the integration will not be automatically removed immediately, so any scheduled executions for the same integration will be skipped. You can now remove the locks from the Monitor > Clear Storage Locks page. |
SOAP API enhancements | Integration Cloud now allows you to export and import SOAP APIs. |
Recipes page enhancements | You can now search a recipe by the recipe name.If the main integration created out of a recipe does not have Applications but has sub-integrations, and if the sub-integrations have Applications, then the Applications are now pulled from the sub-integrations. The logos of the Applications in the sub-integrations will now appear on the Recipes page.You can now see the details of a recipe when you click Use. Further, the recipe configuration page now shows only the Applications and not the Operations for each Application. Also, now you do not have to configure each integration and sub-integration individually.If you have already used a recipe, Integration Cloud now prompts you if an integration with the same name already exists in your selected project and also whether you want to overwrite the references and changes made in the existing integration. |
New Account Configuration fields | You can now set the following fields while configuring an Account: Block Timeout is the number of milliseconds that Integration Cloud will wait to obtain a connection with the SaaS provider before the connection times out and returns an error.Expire Timeout is the number of milliseconds that an inactive connection can remain in the pool before it is closed and removed from the pool, if connection pooling is enabled.Idle Timeout interval in milliseconds defines the interval for which a connection will be kept alive if it is not in use.Keep Alive Interval in milliseconds defines the interval for which a connection will be kept alive, if the back end does not respond with a Keep-Alive header. |
REST Resource Operation enhancements | You can now modify a REST resource even if the resource has an operation with a deleted integration mapped to the operation. |
Project permission changes | To create projects, you must now have the Administrator Access Profile as well as the Developer project permission assigned. |
New Applications | webMethods Cloud Container: You can now use this Application to invoke Java and Flow services for any Cloud Container solution. |
Support for Keyboard shortcuts for workspace and debug operations | You can now click the Show Keyboard Shortcuts icon available above the integration workspace area and view the available shortcut keys.  |
JSON Web Token support | For some Applications, for example, Salesforce CRM v44, Integration Cloud will now get an Access Token using the JSON Web Token (JWT) flow after you save the Account. You can generate OAuth 2.0 tokens using either the Authorization Code flow or the JSON Web Token (JWT) flow approaches. |