Version 5.1.0 (February 2019)

Item	Description
Support for multi-part request body	For some Applications and Operations, for example, for the CloudStreams Connector for Salesforce(R) Bulk v2 Data Loader Application and Create Job and Upload Job Data Operation, Integration Cloud supports multipart request body.
User Interface changes due to performance enhancements	The following user interface changes are made to enhance the performance and reduce the wait time for user actions: Applications are now listed under different categories such as Predefined Applications, REST Applications, On-Premises Applications, and SOAP Applications. The Integrations list page (Develop > Integrations) now shows a basic view of all the Integrations. To view the references (Uses column), select the Show Advanced View check box available on the Integrations list page.
Mapping enhancement	While doing pipeline mapping, you can now view only the mapped fields by selecting the Show Only Mapped Fields check box.
Support for viewing Integration Cloud Capabilities	The new Capabilities page allows you to view the status of some of the system capabilities, based on your license offering. To access this page, from the Integration Cloud navigation bar, click and select Licensing > Capability.
Support for invoking deployed services from Integration Cloud	Integration Cloud Integrations can now invoke Cloud Deployment webMethods Integration Server Flow and Java services for the same tenant. A new pre-defined Application, Cloud Deployment, is added in Integration Cloud. Using this Application, you can select the solution webMethods Integration Server services that you want to call from Integration Cloud.
OAuth 2.0 enhancements	The following OAuth 2.0 enhancements have been implemented in this release: From the Client Registration page, you can now associate scopes with a client as well as create a new scope and associate it with a client by clicking the Associate Scopes option. Support is added for Client Credentials Grant and Resource Owner Password Credential Grant types as part of OAuth spec for OAuth token generation flow. After you select the Enable Integration to be invoked over HTTP option on the Integration Details page, OAuth Scopes containing the exposed Integration URL appears. Clicking the OAuth Scopes option displays the OAuth Scopes which contain the exposed URL of the Integration. You can add the exposed URL of the Integration to an existing scope or add a new Scope which will contain the exposed URL of the Integration. From the REST API Resources page for a REST API which is created from scratch, you can now click the OAuth Scopes option to view the OAuth Scopes which contain the REST Resource path with Method. You can add the REST Resource path with Method to an existing scope or add a new scope which will contain the REST Resource path with Method. While creating or updating a scope, you can now select the exposed Integrations and REST Resources that you want to add as Service URLs from the Services dialog box. Enhanced the OAuth Approval page generated in the OAuth token generation flow. SSO support for authentication during OAuth token generation flow. Support for auditing OAuth Client, Scope, and Token CRUD operations.

Item	Description
Support for usage based license monitoring of CPU and Memory capacity	You can now view the cumulative usage of CPU and Memory for all the active solutions in all the stages from the Usage page. To access this page, from the Cloud Deployment navigation bar, click and select Licensing > Usage. Further, on the Cloud Deployment landing page, you can see the current usage (CPU and Memory) for the tenant.
Continuous Integration/Continuous Deployment (CI/CD)	You can now build user-created assets and configurations using webMethods Asset Build Environment (ABE), retrieve those assets and configurations from a VCS by using ABE or an automated tool like Jenkins, and then deploy those assets and configurations to the Integration Cloud Development Stage using ABE. Note: For information on CI/CD and how to promote assets across stages, see the Deploying to webMethods Integration Cloud document.
Landscape component status	You can now see the status of a solution landscape component whether it is Ready or Not Ready on the landscape page.
Support for stateless cluster of webMethods Integration Servers	In addition to supporting stateful webMethods Integration Server clusters, you can now define that a cluster is stateless from the Landscape page for a solution. The deployment of a solution will therefore not need a Terracotta Server Array.
Support for viewing more assets	You can now view more on-premises assets for Cloud Deployment.
Deployment Status Tracking	You can now type a message to describe the rollback. The rollback message appears on the History page. The History page shows the Trace ID, that is, the tracking ID, which is automatically generated on every successful or unsuccessful promotion or rollback, or deletion, the Deployment, Rollback, or Deletion Action, Date when the asset was promoted, rolled back, or deleted, the User who promoted, rolled back, or deleted the asset, and the commit Message for the selected instance. You can click on a Trace ID to see the Track History for the specific action.
Support for deleting assets	You can now delete assets from all stages from the Deploy page for a solution.
Support for viewing Cloud Deployment Capabilities	The new Capabilities page allows you to view the status of some of the Cloud Deployment capabilities, based on your license offering. To access this page, from the Cloud Deployment navigation bar, click and select Licensing > Capability.
Support for webMethods Adapter KPI monitoring	You can now monitor the following details of all the installed Adapters: Total number of enabled and disabled connection pools Total number of enabled and disabled listeners Total number of enabled and disabled notifications
Duplicate low severity alerts	In earlier releases, along with critical alerts, redundant alerts of lower severity like warning and info alerts were also displayed. From this release, if there are critical alerts, lower severity alerts will not be displayed.