The April 2025 release of Application Integration includes the following new features and enhancements:
New recipes
Application Integration provides the following new recipes:
AI Agent for Dynamics 365 using Azure OpenAI
Use the recipe to autonomously interact with Dynamics 365 and address user queries.
Automobile Insurance Claim Processing with Amazon Bedrock
Use the recipe to evaluate a claim request, assess the vehicle damage, and estimate the insurance payout based on the uploaded images using Amazon Bedrock.
Automobile Insurance Claim Processing with Azure OpenAI
Use the recipe to evaluate a claim request, assess the vehicle damage, and estimate the insurance payout based on the uploaded images using Azure OpenAI.
Automobile Insurance Claim Processing with Google Gemini
Use the recipe to evaluate a claim request, assess the vehicle damage, and estimate the insurance payout based on the uploaded images using Google Gemini.
For more information about these recipes, see the corresponding recipe guides.
New connectors on the Cloud Server
Application Integration provides the following new connectors on the Cloud Server:
Azure Data Lake Storage Gen2 Connector
Use Azure Data Lake Storage Gen2 Connector to write flat files with any content type to a blob container. You can perform create, append, and delete operations to manipulate data in the blob container.
Azure Event Hubs Connector
Use Azure Event Hubs Connector to stream millions of events per second with low latency, enable businesses to ingest and store streaming data, and enhance efficiency and customer experience by providing real-time analytics.
For more information about these connectors, see the corresponding connector guides.
New Java Message Service Connector on Secure Agent
Application Integration provides support for Java Message Service (JMS) Connector on a Secure Agent. You can use JMS Connector in enterprise environments to integrate distributed systems and establish reliable, asynchronous message communication.
JMS Connector replaces the traditional method of creating a messaging service in Application Integration Console and then establishing the connection between Java applications and messaging brokers.
For more information, see JMS Connector Guide.
Ability to disable HTTP port for Process Server
You can disable non-secure connections by leaving the Process Server http-port property value as empty on the Runtime Environments page in Administrator. You must restart the Secure Agent for the change to take effect. After this configuration, when you invoke a process using the HTTP endpoint URL, an error occurs.
For more information, see Secure Agent Services in the Administrator help.
Cross-Origin Resource Sharing support for OData connections
In OData-enabled connections, you can specify Cross-Origin Resource Sharing (CORS) properties, such as the allowed domains and verbs. The CORS properties will be applied when API consumers invoke the associated APls. With this feature, API consumers running a web application running at one origin can access selected resources from a different origin.
For more information, see OData Connector Guide.
New Turbo mode to run processes
You can choose to run processes in the new Turbo mode. The Turbo mode offers high throughput, improved performance, and low latency.
Enable the Turbo mode in the Settings page of Administrator. You can enable the Turbo mode for new jobs or for all the existing and new jobs that are run within an organization.
The processes that run on the Turbo mode will be metered based on the number of process instances that are run for a specific time period.
For more information, see Organization Administration in the Administrator help.
New XQuery function under the Miscellaneous section
You can use the new removeSystemNamespaceXML XQuery function under the Miscellaneous section to remove system namespaces from an XML document and get a more simplified and readable XML structure.
Use the following syntax for the removeSystemNamespaceXML function:
util:removeSystemNamespaceXML(currentElement)
For more information, see Design.
Support for a list of simple types in service connectors created with WSDL, Swagger, and OpenAPI files
When you create a service connector using a WSDL, Swagger JSON, or OpenAPI 3.0 file, you can configure the following list of simple data types:
•Checkbox
•Date
•Date Time
•Integer
•Number
•Text
•Time
You can configure a list of simple types for input fields, output fields, and process object fields in the file before importing it.
For more information, see Design.
Support for output fields in stored procedures of data access service connector
When you use a stored procedure in a data access service connector, you can configure the output fields depending on the database management system (DBMS) that you use, such as MySQL, SQL Server, Oracle, PostgreSQL, or DB2.
You can use the output fields in stored procedures to return data back to the calling application. The stored procedure might return a single value or multiple values.
For more information, see Design.
Kafka supports OAUTHBEARER SASL mechanism
Kafka supports OAUTHBEARER SASL mechanism to authenticate the Kafka producer and the Kafka consumer.
For more information, see Kafka Connector Guide.
Support for keyCharset argument in HMAC signature functions
You can configure the new keyCharset argument in the existing Hash-based Message Authentication Code (HMAC) functions. You can use the optional argument to specify the character set of the secret key that you pass as an argument in the following HMAC signature functions:
Functions
Syntax
hmacSignature
dsig:hmacSignature( $data as xs:string, $key as xs:string, $algorithm as xs:string, $encoding as xs:string?, $keyCharset as xs:string ) as xs:string
hmacSHA1signature
dsig:hmacSHA1signature( $data as xs:string, $key as xs:string, $encoding as xs:string?, $keyCharset as xs:string ) as xs:string
hmacSHA256signature
dsig:hmacSHA256signature( $data as xs:string, $key as xs:string, $encoding as xs:string?, $keyCharset as xs:string) as xs:string
hmacSHA512signature
dsig:hmacSHA512signature ( $data as xs:string, $key as xs:string, $encoding as xs:string?, $keyCharset as xs:string) as xs:string
hmacSHA512signatureforList
dsig:hmacSHA512signatureforList( $data as xs:string, $key as xs:string, $encoding as xs:string?, $keyCharset as xs:string) as xs:string