Skip to main content
Feedback

Connectivity Release Notes for January 2026

January 31 2026

Connector operations page

  • Fixed an issue where the Connector operations page failed to render the Object Type properly in the UI. (CON-10810)

Environment extensions page

  • Fixed an issue where the Environment extensions page failed to load for hidden connectors used in Integration packs. (CONC-14605)

REST Client connector

New
We added these features

  • Added support for the connector to use selectable request and response profiles for the following operations: GET, HEAD, POST, DELETE, PUT, PATCH, OPTIONS, and TRACE. The selectable profiles will use the default profileType, which is JSON or XML. (CON-10627)

  • Added support for the display of a new Client Assertion Type radio button field to add via the descriptor for the Client Credentials grant type. The new field has two selectable options:

    • Client Secret
    • JWT Token

Users can continue using the Client Secret option to use a shared password, which was the default or use the JWT Token option to use a digitally-signed token for advanced security and key-based authentication. Users can also provide <helptext> to these fields in the descriptor. (CON-10685)

  • Added client-side JWT ID (jti) claim support for the existing JWT Bearer grant type and the Client Credentials grant type, only if the Client Assertion type is JWT Token. This feature enables integration with third-party services that require jti claims for authentication. The client will generate unique jti values for each JWT assertion. Typically, these are UUIDs and can be selected in the ID Claim Generator field in the OAuth 2.0 tab. (CON-10596)

  • Added support for the following opt-in JWT parameter fields: (CON-10672)

    • kid (Key ID) Header Parameter
    • x5t#S256 (X.509 Certificate SHA-256 thumbprint Header Parameter)
    • x5t (X.509 Certificate SHA-1 thumbprint)
    • jku (JWK Set URL) Header Parameter
    • x5u (X.509 URL) Header Parameter

Refer to REST Client connector to learn more.

Platform Release

January 24 2026

Amazon Bedrock connector

New
We added these features
  • This connector is being released as General Availability (GA). All features are suitable for production use, are fully supported, and are available to all entitled accounts. (CONC-13799)
  • We added support for the Invoke Agent operation, which enables you to call Amazon Bedrock Agents from a Boomi process.
  • We added support for dynamic model discovery of OpenAI models - available for Generate and Converse actions.

Refer to Amazon Bedrock connector to learn more.

Amazon Selling Partner (Tech Preview) connector

New
We added this feature
  • The Amazon Selling Partner connector is now Generally Available (GA), with support for client secret rotation via an execute operation. (CONC-10776)

Refer to Amazon Selling Partner connector to learn more.

Box connector

New
We added these features

  • Support for full management of Box User objects, including the following capabilities: (CONC-13057)

    • Create new Box users
    • Read user details by ID
    • List the users by filtering name, login, external_app_userid, and user_type
    • Update user information
    • Delete users by ID

  • Extending the existing Box OAuth implementation to include permissions for accessing the User object. This feature will enable future features that need to retrieve user-specific details from Box, for example, user profiles, names, email addresses. (CONC-13258)

  • Support for full operations of Box Groups, including the following capabilities: (CONC-13058)

    • Create, update, delete, and retrieve Box Groups using Box's Groups API
    • List all groups by filtering with name

Refer to Box connector to learn more.

Coupa connector

New
We added this feature

  • Updated the Coupa connector to support reliable GET and UPDATE operations for Invoice Comments. (CONC-12582) (CONC-12581)

  • The Coupa connector has been updated to support Purchase Order status updates, ensuring accurate status transitions during the Update operation. (CONC-11415)

Refer to Coupa connector to learn more.

Database V2 connector

Fix
We fixed these issues

  • When an UPSERT operation is performed on the Oracle database using the Database V2 connector, the UPSERT operation no longer requires elevated database privileges, enabling standard users to perform upserts successfully. Additionally, UPSERT operations using the Database v2 connector on Oracle databases no longer require the elevated ANALYZE database privilege, allowing users to perform upserts successfully without this specific permission. (CONC-6022)

  • The Database V2 connector has been enhanced to handle double quotes or new line characters in text fields during Standard Update operations, across Oracle, MS SQL, MySQL, and Postgres databases. (CONC-5752)

  • The Database V2 connector now fully supports SMALLINT OUT and INOUT parameters when executing stored procedures on IBM DB2, ensuring successful execution. (CONC-11813) (CONC-12565)

  • The Database V2 connector uses Oracle table metadata to apply default values for NOT NULL columns when no value is provided, prevents insert, update, and upsert failures due to missing column values and aligns connector behavior with database-defined defaults. (CONC-2352)

Refer to Database V2 connector to learn more.

Disk V2 connector

Fix
We fixed this issue
  • Disk V2 operations now honor a valid Directory value provided at the payload level, even if the connection-level directory is invalid, preventing unnecessary errors and improving runtime flexibility. (CONC-12779)

Refer to Disk V2 connector to learn more.

Event Streams connector

New
We added this feature

  • Updated the client library from v2.11.2 to v3.3.9 (ES-3340)

    note

    This feature was deferred to a future release.

IntegratD - Partner connector

New
We added these features
  • Updated the connector to use more secure Apache Commons libraries.
  • Updated JMS to use the latest version of the shared libraries.
Fix
We fixed this issue
  • Fixed an issue in the Execution ID parsing logic. (TPP-59)

Refer to IntegratD - Partner connector to learn more.

JMS V2 connector

New
We added this feature
  • The JMS V2 Listener now automatically retries lost connections up to six times at progressive intervals (immediately, then at 10s, 30s, 60s, 120s, and 300s) before requiring a manual restart, aligning its connection resilience behavior with JMS V1. (CONC-12853) (CONC-13549)

Refer to JMS V2 connector to learn more.

Kafka connector

New
We added these features

  • During misconfigured or unreachable connection scenarios, the Kafka Connector Listener now automatically retries connection failures up to six times at progressive intervals (immediately, then at 10s, 30s, 60s, 120s, and 300s) before stopping and requiring a manual restart, while logging a SEVERE-level error and preventing excessive log flooding. (CONC-11814)

  • The Kafka connector user interface now includes a Kafka Edition selection at the connection level, enabling users to choose the target Kafka platform. The Schema Registry tab has also been updated to Confluent Schema Registry for improved clarity. The PRODUCE action introduces automatic Client ID management for Confluent Kafka to ensure seamless tracking and compatibility. (CONC-12666)

  • The Kafka connector now supports Avro schemas for dynamic topics using Confluent Schema Registry, enabling efficient, schema-based message production, consumption, and listening. Users can select registered schemas during import to seamlessly work with Avro-encoded message values. (CONC-10438)

Refer to Kafka connector to learn more.

Kintone connector

New
We added these features

  • The AppID is now a dynamic operation property to enhance workflow portability across environments for the following operations:

    • Query
    • Create and Update
    • Delete

    With this change, workflows are no longer tied to a statically-bound AppID in the profile. Instead, the AppID is configurable at runtime, allowing seamless migration between environments without the need to reimport profiles. (CONC-14029)

  • Changed the connector icon in the platfrom from a global icon to a cloud icon.

Refer to Kintone connector to learn more.

KnowBe4 - Partner connector

New
We are releasing this connector
  • New connector release to support the integration between KnowBe4 and the Boomi platform. (TPP-60)

Refer to KnowBe4 - Partner connector to learn more.

MongoDB connector

Fix
We fixed this issue
  • The MongoDB connector successfully returns results when filtering on Integer, Boolean, and Decimal fields, as well as Nested Integer Arrays, ensuring reliable query behavior without impacting existing functionality. (CONC-12993)

Refer to MongoDB connector to learn more.

OData Client connector

New
We added this feature
  • The OData Client connector now supports API Key-based authentication, allowing secure access to OData services using API keys in addition to existing authentication methods. (CONC-9747) (CONC-11731)

Refer to OData Client connector to learn more.

OpenAI (Tech Preview) connector

New
We are releasing this connector
  • A new OpenAI (Tech Preview) connector is being released. It provides a seamless, secure, and robust integration point between the Boomi platform and the OpenAI API. It should not be used in a production environment or with production data. For more information, refer to the Feature release stages page.
  • The existing OpenAI connector is being retired with the release and is no longer supported. Existing integrations using this connector will continue to operate but we recommend you migrate to the new OpenAI (Tech Preview) connector for continued support and innovation. (CONC-13046)

Refer to OpenAI (Tech Preview) connector to learn more.

Oracle Database connector

Fix
We fixed this issue
  • The Oracle connector has been updated to support timestamp values with millisecond precision in Dynamic Insert, Dynamic Update, Dynamic Delete, and Stored Procedure operations, ensuring accurate data insertion and consistency with supported timestamp formats. (CONC-12875) (CONC-13205) (CONC-11935) (CONC-9296)

Refer to Oracle Database connector to learn more.

Oracle E-Business Suite V2 connector

Fix
We fixed these issues

  • The connector now supports successful profile imports for REST_EXECUTE operations when using SOA Gateway connections, allowing Interface APIs to be configured and executed successfully. (CONC-13571)

  • The Oracle EBS V2 connector PL/SQL Execute action now supports PL/SQL stored procedures that return Table Type and Record Type data, ensuring all returned values are correctly mapped to the corresponding Boomi profile elements. (CONC-820) (CONC-5822)

  • Update the connector Jackson version to v2.15.0. (CONC-12001)

New
We added this feature
  • The connector now logs connection pooling details in the runtime container logs, aligning its behavior with that of the Oracle EBS Legacy connector. (CONC-14014)

Refer to Oracle E-Business Suite V2 connector to learn more.

RabbitMQ connector

New
We added these features

  • The RabbitMQ connector now supports temporary queues via ReplyTo header for publish operations, enabling native request-reply messaging without custom scripting. Users can enable temporary queues via an operation setting, configure a dedicated timeout, and rely on automatic cleanup when the connection closes. (CONC-12467) (CONC-9627)

  • The RabbitMQ Listener now supports configurable concurrent message processing via MCE operation property (set between 1 to 5), enabling improved throughput by processing messages in parallel. By default, the listener continues to process messages one at a time, maintaining the existing behavior and compatibility. (CONC-11489) (CONC-10208)

Refer to RabbitMQ connector to learn more.

REST Client connector

note

Subsequent to the Runtime Release, the following feature has been deferred to a future release.

New
We added this feature
  • Added support for the connector to use selectable request and response profiles for the following operations: GET, HEAD, POST, DELETE, PUT, PATCH, OPTIONS, and TRACE. The selectable profiles will use the default profileType, which is JSON or XML. (CON-10627)

SAP S4/HANA OData connector

Important

Subsequent to the January Runtime Release, an issue was reported that required version 5 to be rolled back. If you applied version 5, you will be reverted back to version 4.

Fix
We fixed this issue
  • Fixed an issue where array elements were incorrectly formatted; array elements including nested elements now match the data types defined in the response profile across GET, QUERY, CREATE, UPDATE, and DELETE operations. (CONC-4687)

SFTP V2 (Retired) connector

New
We have retired this connector
  • The SFTP V2 connector has been retired and is no longer supported. Existing integrations using this connector will continue to operate but we recommend you migrate to the SFTP connector for continued support and innovation. (CON-10726)

Refer to SFTP V2 (Retired) connector to learn more.

Snowflake connector

Important

Subsequent to the January Runtime Release, an issue was reported that required version 29 to be rolled back. If you applied version 29, you will be reverted back to version 26.

Fix
We fixed these issues

  • The Snowflake connector has been updated to restore create and delete performance impacted in version 27. (CONC-12789) (CONC-12439)

  • The Snowflake connector now supports Dynamic Operation Properties for database and schema selection during insert operations, ensuring consistent behavior across environments. When dynamic values are not provided, the connector defaults to the operation-level settings. (CONC-11137)

  • The Snowflake connector now supports default values for missing fields during CREATE operations, including scenarios with multiple inputs and database or schema overrides. (CONC-10125)

  • The Snowflake Connector has been updated to address the NullPointerException in the Create action when the connection schema is empty and database/schema overrides are provided at the operation level. This has been addressed in version 29. (CONC-14449)

Solace PubSub+ - Partner connector

Important

Subsequent to the January Runtime Release, an issue was reported that required version 337 to be rolled back. If you applied version 337, you will be reverted back to version 326.

New
We added these features
  • Added OpenTelemetry distributed tracing support for all Solace messaging operations with automatic trace context propagation. Refer to the documentation for configuration details.
  • Added support for general HTTP proxy configuration. The connector now automatically uses proxy settings configured at the basic runtime/runtime cluster level.
  • Added standard OAuth configuration tab supporting Client Credentials and Authorization Code grant types. This provides a more streamlined OAuth setup, with platform-managed token handling. Previous custom OAuth configuration remains supported.
  • Enhanced existing custom OAuth2 configuration to be proxy-aware, automatically using configured proxy settings for OAuth token requests and refresh operations.
Fix
We fixed this issue
  • Fixed an issue where Listen operations could remain active after connection failures, causing continuous error messages in the logs. (TPP-58)

Workday connector

Fix
We fixed these issues

  • The Workday connector now automatically retries Test Connection and Execute operations when OAuth 2.0 tokens expire. This will depend on the token expiry configuration in Workday. (CONC-12873) (CONC-12791)

  • The connector now detects HTTP 401 (Unauthorized) responses, refreshes expired access tokens, and automatically retries the request. (CONC-11979)

Refer to Workday connector to learn more.

Workday Prism Analytics (Tech Preview) connector

New
We have retired this connector

The Workday Prism Analytics (Tech Preview) connector has been retired and is no longer supported. Customers should use the supported Workday Prism Analytics connector. (CON-10726)

On this Page