The April 2026 release of Application Integration includes the following changed behaviors:
Deprecation of session ID for Salesforce Outbound Message calls
Salesforce no longer sends session IDs in outbound messages (OBM) calls that you make from a Salesforce organization to an Informatica Intelligent Cloud Services (IICS) organization. This change impacts how Salesforce OBM calls authenticate when you invoke processes.
As a result of this change, you must provide the tenant ID in scenarios involving multiple Salesforce organizations or multiple IICS organizations to ensure proper authentication without session IDs. No URL changes are required in OBM calls that you make from a single Salesforce organization to a single IICS organization.
Previously, you had to provide session IDs in the URLs to authenticate OBM calls.
For more information, see the Informatica Knowledge Base article 000257332.
Changes to the Applies To list
The options in the Applies To list in a process are rearranged to improve the usability. When you select the entity, you can select one of the following asset types to view the corresponding assets:
•Process Objects. Select a process object
•App Connections. Select an app connection, and then select an object.
Previously, there was no segregation of process objects and app connections. For more information, see Design.
Changes to the Custom and Connection Defined Types list in a process
When you create an input, output, or temp field in the Start step of a process, you must click Select corresponding to the custom and connection defined types to select the custom data types and connection types, respectively. This feature provides an organised and more focused interface by moving these lists to a secondary selection screen.
Previously, all available objects for Custom Types and Connection Defined Types appeared on the same interface.
For more information, see Design.
Enhanced util:toJSON XQuery function
The util:toJSON XQuery function doesn't remove the array brackets [] even when the input contains a single object in a list. This change preserves the array structure for downstream services.
The function has two arguments as shown in the following format:
toJSON(elements as element(), preserveSingleElementArray as xs:boolean?)
The first argument is the elements to be converted, and the second argument is a boolean value True or False.
If the second argument is True, the output of the function retains the array brackets [] even when the input contains a single object in a list.
Previously, you could only pass the elements as an argument in the util:toJSON XQuery function. The function removed the array brackets [] when the input payload contained a single object in a list.
For more information, see Design.
Process logging level change
When a process gets suspended due to a breach of the activity execution limit, the process logging level is automatically changed to FAULT to improve performance and reduce database storage spikes.
Previously, when a process got suspended under such circumstances, it remained in the database for 14 days before getting purged. This prolonged retention led to increased database storage usage and resource consumption, causing significant performance degradation.
For more information, see Design.
SAP IDoc reader property change
The Idle Time property is removed from the Reader Properties section in the SAP IDoc connection creation page because Application Integration always uses a default value of -1 for this property.
For more information, see SAP IDoc Connector Guide.
Support for dynamic dispatch queue configuration on Secure Agents
If Process Server runs on a Secure Agent, you can enable the dispatch service to dynamically create dispatch queue configurations and avoid deadlocks.
To enable dynamic dispatch queue configuration, in the Custom Configuration Details section of the agent details page, add the useDynamicDispatchService property and set the value to true.
Previously, you used the dispatch service to manually create dispatch configurations that throttle requests made to the Process Server.
For more information, see Secure Agent Services in the Administrator help.
RabbitMQ header format update in Apache Camel 4.x
In Apache Camel version 4.x, RabbitMQ message headers use the CamelSpringRabbitmq* format. This format applies only to connections that you publish on Cloud Server.
Previously, the headers used the rabbitmq.* format.
For more information, see RabbitMQ Connector Guide.
Inbound message rejections return HTTP 503 error to enable retry
You receive HTTP 503 errors for inbound messages that were rejected immediately due to reasons such as, dispatch queue size limits. You can retry the requests.
Previously, you received HTTP 500 errors and the messages were discarded without attempting a retry.