Application Integration includes the following new features and enhancements in this release:
Watch the following What's New video to learn about the new features and enhancements in the October 2023 release:
Ability to create process objects by importing JSON files
You can import JSON files to easily create multiple large and hierarchical process objects that cover the data types used in the JSON payload.
With this feature, you can save time and effort because you do not have to manually create process objects.
For more information about creating process objects by importing JSON files, see Design.
Apache Camel for Application Integration
Application Integration has updated Apache Camel to version 3.14.
After your POD (Point of Deployment) is upgraded to the October 2023 release, you don't need to take any action.
My Processes page
The My Processes page includes the following changes:
•The Actions menu is added to the process instance row. It contains options to restart, delete, resume, suspend, and stop process instances.
•In the Process View Detail page, the Log area contains the Start Date and End Date fields.
•In the Process View Detail page, the Parallel Path step shows the sequence for each path.
The following image shows the changes on the Process View Detail page:
Stored procedure and multiple SQL query support in data access service connectors
When you create a data access service connector, on the SQL Binding tab, you can define multiple SQL queries and stored procedure calls per action to access the data from the data source.
For each of the SQL entries, you can define the name, SQL query, column case, type of SQL query, maximum number of rows, and maximum wait time in seconds.
For more information about creating multiple SQL queries, see Design.
Support for OData expand functionality
In data access service connectors, after you publish an app connection, you can use the OData expand parameter to perform nested queries on the data. You can query up to one level of a navigation property in a service call.
For more information about the OData expand parameter, see Design.
New XQuery functions in Miscellaneous section
You can use the following new XQuery functions under the Miscellaneous section:
XQuery function name
Description
Syntax
getOrganizationName
Returns the organization name in the context of the executing process, guide, service connector, or data access service connector.
Note: If the process is published on a Secure Agent, you must restart the Process Server to get the organization name in the context of the executing process.
util:getOrganizationName()
getAssetName
Returns the name of the process or the guide that uses the function.
util:getAssetName()
getAssetLocation
Returns the location where the process or the guide that uses the function is stored. You can use the getAssetLocation function only in processes that run on the Cloud Server.
util:getAssetLocation()
getInstanceStartTime
Returns the start time of the running instance of the process or guide.
util:getInstanceStartTime()
For more information about these new XQuery functions, see Design.
Load balancing support for RabbitMQ connections
You can configure load balancing for RabbitMQ connections that run on a Secure Agent cluster.
For more information about configuring load balancing in a RabbitMQ connection, see RabbitMQ Connector Guide.
Support for extraction of JMS headers when invoking a process
When you invoke a process, in addition to the HTTP headers, you can use the following request context functions to get the header details from JMS messages:
•getAllHeaders
•getDateHeader
•getHeader
•getHeaderNames
•getHeaderOrDefault
•headerExists
When you use these functions to get the header details, the output will be the same for both HTTP headers and JMS headers.
For more information about these function, see Design.
Support for Kafka connections on the Cloud Server
You can create a Kafka connection on the Cloud Server and configure SSL and SASL authentication by uploading the SSL truststore file and keystore file.
After you publish the Kafka connection on the Cloud Server, you can start and stop event sources from the Connections page in Application Integration Console.
With this feature, you can save time and effort because you do not have to unpublish and republish the connection to stop and start the event-based processes.
For example, if the event source points to or returns corrupted data, and you do not want processes to consume that data, you can stop the event source associated with that endpoint. Thereafter, the processes published on that event source will not consume new messages. However, if you stop an event source when a process is running, the process continues to run in the background and completes gracefully.
Note: This feature is available only on the AWS PODs.
For more information about starting and stopping event sources in a Kafka connection that runs on the Cloud Server, see Connectors for Cloud Application Integration and Monitor.
