The October 2026 release of Application Integration includes the following new features and enhancements.
Application Integration Console enhancements
You can view the input, output, and temporary field values directly when you view a process instance in Application Integration Console.
Note:
You can view these fields only when you set the process tracing level to Normal or Verbose.
You don't need to open the process instance in the advanced view to inspect these values. You can trace step-by-step behavior, verify results, and troubleshoot completed runs faster.
Under process properties, you can also view the Target Namespace field, which uniquely identifies the process executed by the instance.
For more information, see Monitor.
Swagger definitions with enhanced error reporting
Auto-generated OpenAPI 3.0 process specifications in Application Integration now automatically include seven standard HTTP application failure fault status codes.
This feature enables upstream API gateways and consumer clients to automatically parse, validate, and handle process error responses. As a result, you can streamline API gateway onboarding without manual specification edits or security exceptions, enforce built-in compliance across process assets, and improve runtime reliability through precise payload and error validation.
For more information, see Invoke.
Support for publishing multiple messages to Google PubSub
You can use the event target in a Google PubSub app connection to publish multiple messages in a single Service step. The PubSubMessage element is a repeatable list type. Use it to bundle multiple payloads, each with its own headers, attributes, and body.
For more information, see Google PubSub Connector Guide.
New XQuery function
In the Miscellaneous section of the Expression Editor's Functions list of Process Designer, use the new util:toJSONWithSchema XQuery function to convert the XML data structures and process objects inside a process into the JSON format with a defined schema. The schema enables the parser to identify array fields and preserve single-element arrays as arrays. Defining the schema ensures consistent array structures regardless of the payload size.
For more information, see Design.
OAuth 2.0 authentication through a Secure Agent
You can perform OAuth 2.0 authentication through a Secure Agent when you configure service connectors and application connections. Use a Secure Agent or Agent Group to authenticate with private OAuth providers in isolated networks that Informatica Cloud can't access directly.
For more information, see Design.
OAuth 2.0 PKCE support for service connectors and Email connections
You can configure OAuth 2.0 connections using the Proof Key for Code Exchange (PKCE) grant type in service connectors and Email connections. PKCE is an OAuth 2.0 security enhancement that eliminates the need to transmit client secrets during authentication, helping you meet stricter security and compliance requirements when connecting to external services.
For more information, see Design.
Hierarchical Mapper transformations on Secure Agents
Application Integration can route the Hierarchical Mapper transformation execution to a Secure Agent instead of to the cloud-hosted service. You activate agent-based execution by pointing a URN at the Secure Agent endpoint, which gives you control per organization and per environment.
For more information, see Design.
XQuery Update Facility support
Query expressions now support the XQuery Update Facility, a standard W3C extension to XQuery that adds copy-modify-return operations to insert, delete, rename, or replace nodes and node values directly within an expression without creating intermediate copies. This simplifies expression authoring and improves processing efficiency.
For more information, see Design.
Support for OData views in data access service connectors
You can now expose database views as OData entities through a data access service connector and read data from them. Use views to model and query your data with more flexibility through OData.