You can use Google BigQuery V2 Connector to connect to tables in Google BigQuery and perform CRUD operations. For CRUD operations that need a primary key, you can define custom keys to assign single or composite primary keys. You can also enable OData in a Google BigQuery V2 connection.
For more information, see Google BigQuery V2 Connector Guide.
CLAIRE Copilot supports Slack Connector
In CLAIRE Copilot, you can use a Slack application connection to create a process.
For more information, see CLAIRE Copilot for Application Integration.
New UI experience for Application Integration Console
The Application Integration Console user interface has a new look and feel that presents the features you'll use in greater clarity.
For more information, see Monitor.
Support of array inputs in processes running in the Turbo mode
In the Turbo mode, you can provide an array as input when you invoke a process with a whole JSON payload. You can include multiple items within square brackets [] in the request payload, enabling batch processing of multiple inputs in a single request and thereby improving data handling efficiency.
For more information, see Design.
New search options for processes in Application Integration Console
In the Application Integration Console Processes page, you can use the following new options to easily search for processes:
•Starts With. Use this option to search for processes whose names start with the defined search term.
Note:
To enable this option on a Secure Agent, restart the agent.
•Contains. Use this option to search for processes whose names contain the defined search term.
For more information, see Monitor.
Validation of SVG files during recipe submission
When users create and submit their own recipes, SVG files are validated and potential malicious SVG files are blocked for improved security.
For more information, see Getting Started with Recipes.
Improved service connector response parsing
Use the new Response Format field to define how service connector response payloads are parsed. This field gives you better control over response handling and provides clear error messaging.
Additionally, you can enable the Allow Multipart Response option to support multipart response data.
For more information, see Design.
Support for OData for data access service connectors with Snowflake databases
You can enable OData when you create a data access service connector to connect to a Snowflake database using OAuth 2.0.
For more information, see Design.
Support for new authentication methods in data access service connectors with Microsoft SQL Server databases
When you use a data access service connector to connect to a Microsoft SQL Server database, you can configure Active Directory password authentication.
For more information, see Design.
Support for attachments in SOAP API calls using XML-binary Optimized Packaging (XOP) mechanism
You can send and receive attachments in SOAP APIs using multipart/form-data requests or XML payloads with the XOP mechanism. XOP efficiently serializes XML data containing binary content by encoding files and including them through dedicated file transfer endpoints. This feature enables seamless, efficient, and secure attachment handling within SOAP API workflows for integration with external systems.
For more information, see Design.
Support for returning result sets in data access service connectors
A stored procedure in a data access service connector can now return a result set. You can configure the maximum number of rows that the SQL query must return in the SQL response payload. For a result set, the maximum number of rows that you configure applies to each SQL statement within the stored procedure.
For more information, see Design.
Support for a new Cursor data type in Stored Procedure Output Parameters
In data access service connection, you can use the new Cursor data type in the output fields of a stored procedure. Use this data type to return a result set with multiple rows and complex data structures rather than just a single value from the stored procedure.
For more information, see Design.
Support for Client Credentials grant type with OAuth 2.0 authentication
You can now select Client Credentials as the grant type when using OAuth 2.0 authentication to enable streamlined and secure access management.
For more information, see Design.
SAP BAPI Connector supports load balancing and secure network communication
You can now configure an SAP BAPI connection for load balancing and Secure Network Communications (SNC). In the SAP Additional Parameters property, configure properties related to the specific authentication type.
For more information, see SAP BAPI Connector Guide.
New SAP IDoc connection property
In the Connection Properties section of an SAP IDoc connection, you can choose to prefix metadata with the IDoc type to make process objects unique when processing multiple IDocs.
For more information, see SAP IDoc Connector Guide.
New SAP IDoc writer properties
In the Writer Properties section of an SAP IDoc connection, you can configure the following new properties:
•Destination Pool Capacity. Defines the maximum number of idle connections that can be retained in the destination pool for write operations. Increase this value for better performance under high concurrency.
•Destination Peak Limit. Defines the maximum number of simultaneously active connections to the SAP destination. This option helps in managing the SAP-side resource limits.
•Destination Expiration Time (ms). Defines the time in milliseconds before idle connections are closed.
•Destination Expiration Check Period (ms). Defines the interval in milliseconds for checking and cleaning up expired connections.
•Destination Max Get Client Time (ms). Defines the maximum time in milliseconds to wait for a connection from the pool.
For more information, see SAP IDoc Connector Guide.
REST API support for Universal Resource Name (URN) mappings
You can use REST APIs to perform the following tasks:
•Get details of all URN mappings
•Create a new URN mapping or update an existing one
•Delete a URN mapping
For more information, see Monitor.
Ability to export reports from Operational Insights
You can now export Application Integration usage reports from Operational Insights using a GraphQL API. The exported data uses your current page filters and includes process start and end times in Coordinated Universal Time.
You can export the following types of reports:
•Reports related to API calls, processes, connections, and licensing for a period of one month
•A full job report that includes the usage details of all processes, guides, and OData executions for a period of up to 13 months
These reports help you assess the status and usage of your Application Integration assets and take appropriate corrective actions as needed.
For more information, see Operational Insights.
Support for metering tags for Application Integration assets
In Administrator, you create and assign metering tags for Application Integration assets to organize and track IPU usage across various departments, projects, or initiatives. You can assign the tags to projects, folders, and assets.
After assigning metering tags to assets, you can view your IPU usage by metering tag on the Tag Breakdown tab on the Metering page.
For more information, see Organization Administration in the Administrator help.
Enhanced metering reports
In Administrator, the Metering page provides the following additional details to group and analyze the IPU usage:
•Project name
•Folder name
•Asset name
•Asset type
For more information, see Organization Administration in the Administrator help.