Skip to main content
Feedback

Connectivity Release Notes for November 2026

Updated 

Platform Release

14 November 2026

Amazon DynamoDB (Early Access) connector

New Connector

note

This connector is available as Early Access.

  • The Amazon DynamoDB connector now features an updated user experience aligned with standard Boomi design patterns. It introduces comprehensive support for Create, Get, Query, Update, Delete, Upsert, and Execute operations across Items, Tables, and Transactions. Additionally, connection security has been enhanced with support for both AWS access keys and AWS IAM Roles Anywhere authentication. (CONC-17536, CONC-17537, CONC-17538, CONC-17539, CONC-17540, CONC-17541, CONC-7301)

Refer to Amazon DynamoDB (Early Access) connector to learn more.

Amazon EventBridge connector

Important

Subsequent to the November Platform Release, an issue was reported that required the Amazon EventBridge connector to be reverted back to version 10.

Fix

  • Resolved an issue where sending valid XML documents with double-quoted attribute values could result in a MalformedDetail error. XML payloads with double-quoted attribute values can now be sent successfully. (CONC-16233)

Refer to Amazon EventBridge connector to learn more.

Amazon Redshift connector

Fix

  • Resolved a Critical, High, and Medium severity vulnerability to improve the security of the connector. (CONC-18911)

Refer to Amazon Redshift connector to learn more.

Amazon S3 REST connector

Fix

  • Resolved a Critical, High, and Medium severity vulnerability to improve the security of the connector. (CONC-17550)

Refer to Amazon S3 REST connector to learn more.

Amazon SNS connector

Enhancement

  • Necessary runtime packages are now packaged with the connector. (CONC-19383)

Refer to Amazon SNS connector to learn more.

Amazon SQS connector

New Feature

  • Enabled live status reporting for the Listen operation on the Runtime Management → Listeners page. The status shows Listening when polling is healthy and Degraded, with error details, when polling fails. (CONC-16603)

Fix

  • Resolved an issue where the Listen operation redelivered a message when a worker was recycled. The Listen operation now completes message processing, so the message is no longer redelivered. (CONC-17423)

Refer to Amazon SQS connector to learn more.

Anaplan connector

Enhancement

  • Necessary runtime packages are now packaged with the connector. (CONC-7262)

Refer to Anaplan connector to learn more.

AWS Lambda connector

New Feature

  • The AWS Lambda connector is now Generally Available. The Function field in the Invoke operation can now be set through Environment Extensions, so the same process can be promoted from UAT to PROD without pointing production at a UAT function. (CONC-11865)

Fix

  • Repackaged the libraries to facilitate updating the connector. (CONC-18377)

Refer to AWS Lambda connector to learn more.

Ceres - Partner connector

Retirement

  • This connector is being retired and will no longer be available on the Boomi Enterprise Platform. For more information about the Retirement stage, refer to the Product and Feature Retirements page. (TPP-86)

Coupa connector

Fix

  • Resolved Critical, High, and Medium severity vulnerabilities in the connector. (CONC-18849)

Refer to Coupa connector to learn more.

Creatio - Partner connector

New Connector

  • Introduced the Creatio — Partner connector, enabling native integration between Boomi Enterprise Platform and Creatio, the AI-native no-code platform for CRM and workflow automation. (TPP-85)

Refer to Creatio - Partner connector to learn more.

Database connector

New Feature

  • Added support for DATETIMEOFFSET and JSONB datatypes across additional Database Connector operations:
    • DATETIMEOFFSET: Supported for INSERT, UPSERT, GET, UPDATE, DELETE, and Stored Procedure operations. (CONC-17392, CONC-16498)
    • JSONB: Supported for INSERT, UPDATE, DELETE, UPSERT, GET, and Stored Procedure operations. (CONC-17311, CONC-17310, CONC-16486)

Enhancements

  • Updated the SQL query tooltip for the Update statement to clarify that allowMultiQueries=true is MySQL only and does not apply to Oracle. (CONC-17506)

Fixes

  • Resolved an issue with Standard Insert operations on databases without auto-increment columns. Records can now be inserted successfully without requiring generated keys. (CONC-6373)
  • Resolved an issue with Dynamic Insert operations on databases without auto-increment columns. Records can now be inserted successfully without requiring generated keys. (CONC-14826)
  • Resolved an issue with Insert operations on Azure Synapse Analytics that failed with the [104162] 'SCOPE_IDENTITY' is not a recognized built-in function name error. Note that generated keys will not be returned for Azure Synapse connections. (CONC-11713)
  • Resolved an issue with Standard Get when Enable SQL Query is selected and the dynamically passed query contains double quotes or literal characters in schema and table names. Queries are now processed successfully without unintended backslashes. (CONC-16132, CONC-16139)
  • Resolved an issue where transaction processing generated excessive INFO-level messages in the container log. Transaction-related logging is now reduced to the appropriate level. (CONC-16207)
  • Resolved an issue where Dynamic Get operations made redundant metadata calls. Response times are now improved. (CONC-12730)

Refer to Database connector to learn more.

Disk connector

Fix

  • Resolved Critical, High, and Medium severity vulnerabilities to improve the security of the connector. (CONC-18850)

Refer to Disk connector to learn more.

Fiix - Partner connector

Enhancements

The following list of Objects and their fields has been amended for this release:

  • AssetCategory: cf_strBarcodeFormatType

  • AssetConsumingReference: intUpdated

  • AssetOfflineTracker: intUpdated

  • CycleCount: intUpdated, strAisle, strRow, strBin

  • File: intScheduledMaintenanceID, dv_intPurchaseOrderID, dv_intScheduledMaintenanceID

  • Project: bolIsActive

  • PurchaseOrder: dv_intLocationID

  • ScheduledMaintenanceAsset: intUpdated, cf_assetAddress, cf_bolIsOnline, cf_strAssetAddress

  • ScheduledMaintenancePart: cf_part, cf_partLocation

  • SiteUser: intUpdated

  • SiteUserGroup: intUpdated

  • StockCycleCount: intUpdated

  • TaskGroup: intUpdated

  • User: dblHourlyRate, cf_intSiteIDs, cf_intDefaultImageFileID, cf_intDefaultImageFileThumbnailID, dv_intCountryID

  • WorkOrderAsset: cf_getLatestReadingsFor, cf_intAddressAssetID, cf_assetAddressString, cf_getBolIsOnline, cf_getIntSuperCategorySysCode

  • WorkOrderTask: cf_bolIsCompleteable

(TPP-87)

Refer to Fiix - Partner connector to learn more.

Google Pub/Sub connector

New Feature

  • The Google Pub/Sub Listen operation now reports its live status on the Runtime Management → Listeners page. The status shows the failure reason when the connection is degraded and returns to Listening automatically when the connection recovers. (CONC-16604)

Refer to Google Pub/Sub connector to learn more.

HTTP Client connector

New Features

  • The HTTP Client connector now supports outbound distributed tracing. They automatically include trace headers on outbound requests, helping you track requests across connected systems. (RUN-11531)

  • The HTTP Client connector now adds traceparent and tracestate headers to outbound HTTP Get and HTTP Send requests. This enables distributed tracing and request correlation across the services you connect to. (RUN-11468)

Refer to HTTP Client connector to learn more.

HubSpot CRM connector

Fix

  • Resolved Critical, High, and Medium severity vulnerabilities in the connector. (CONC-17628, CONC-18092)

Refer to HubSpot CRM connector to learn more.

JMS connector

Fixes

  • Resolved an issue where tracking field values were not populated at the document level on the Process Reporting page for the Send action. (CONC-13167)

  • Resolved an issue where sending a message to a Dynamic Destination profile with JMS and Oracle AQ resulted in an error. (CONC-13564)

Deferred

note

Subsequent to the Runtime release, the fix for CONC-11189 has been removed from the November release and deferred to a future release.

  • Deferred an issue where WebSphere MQ truncated the queue:// or topic:// value from the destination name when a query parameter was included with the Queue/Topic, causing an error. (CONC-11189)

Refer to JMS connector to learn more.

Kafka connector

New Feature

  • Added OAuth 2.0 Client Credentials authentication for the Confluent Schema Registry connection, alongside Basic Authentication. You can use a dedicated OAuth client or reuse the Kafka OAuth 2.0 credentials. (CONC-18310)

Fix

  • Resolved an issue with the connector when using Snappy compression in the public test cloud. Messages can now be processed successfully without permission errors. (CONC-12991)

Refer to Kafka connector to learn more.

Laserfiche - Partner connector

Fix

  • Resolved security vulnerabilities by upgrading the jackson-databind library from 2.18.2 to 2.18.11. (TPP-82)

Refer to Laserfiche - Partner connector to learn more.

Live Optics connector

Enhancement

  • Necessary runtime packages are now packaged with the connector. (CONC-5337)

Refer to Live Optics connector to learn more.

Magento connector

Enhancement

  • Updated the connector for Java 8 and local dependencies. (CONC-3391)

Refer to Magento connector to learn more.

ManageEngine ServiceDesk Plus - Partner connector

New Connector

  • Introduced the ManageEngine ServiceDesk Plus — Partner connector, enabling native integration between Boomi and ManageEngine ServiceDesk Plus Cloud. Use it to integrate your IT service management data with other business systems from a Boomi process. (TPP-83)

Refer to ManageEngine ServiceDesk Plus - Partner connector to learn more.

Microsoft Azure Cosmos DB connector

Enhancement

  • Necessary runtime packages are now packaged with the connector. (CONC-19302)

Refer to Microsoft Azure Cosmos DB connector to learn more.

Microsoft Azure Data Lake Storage connector

Important

Subsequent to the November Runtime Release, two issues were reported that required the Microsoft Azure Data Lake Storage connector to be patched to version 6.

  • Resolved an issue where the Create operation response was returning raw Java field names (filesystem, path, status) instead of the profile-defined field names (File System, Path, Status) (CONC-19699)

  • Resolved an issue where a leading / in the target directory was being encoded to %2F causing an error. (CONC-19759)

New Feature

  • Added Azure Entra ID client certificate authentication for Azure Data Lake Storage connections, while preserving client secret-based authentication for existing connections. (CONC-13905, CONC-17732)

  • Azure Data Lake connector now supports the standard SDK OAuth 2.0 setup (CONC-18474)

Fixes

  • Resolved an issue where the Read List operation returned inconsistent batch sizes smaller than the specified Max Results value. (CONC-17896)

  • Resolved an issue where file names and object names with spaces were not honored in the Get and Create operations. Existing custom encoding of spaces for these operations should be reviewed. Other operations are unchanged. (CONC-12771)

Enhancements

  • Added a configurable Read Timeout to prevent the connector from waiting indefinitely. (CONC-17323)

  • Necessary runtime packages are now packaged with the connector. (CONC-3167)

Refer to Microsoft Azure Data Lake Storage connector to learn more.

Microsoft Azure Service Bus connector

Important

Subsequent to the November Runtime release, an issue was reported that required this connector to be rolled back. If you applied the new version 26.11.3 during the Runtime release, you will be reverted back to the previous release version 26.05.0.

New Feature

  • Added container properties to tune session handling for the Listen operation. SessionIdleTimeout is supported as an operation property and is available on all runtimes. PrefetchCount and MaxConcurrentSessions are available as container properties on private runtimes only. MaxConcurrentSessions defaults to 1. (CONC-18291, CONC-19160)

Enhancements

  • Upgraded the Send (AMQP), Receive (Session Aware), and Listen operations to the Microsoft azure-messaging-servicebus SDK, and applied the latest patch updates to Microsoft azure-core and azure-messaging-servicebus. Microsoft retired the legacy Microsoft Azure Service Bus SDK on September 30, 2026. (CONC-17545, CONC-17546, CONC-17547, CONC-17630, CONC-16859)

  • Renamed the Receive (Session Aware) operation to Receive (AMQP) (CONC-17525)

Refer to Microsoft Azure Service Bus connector to learn more.

Microsoft Dynamics 365 F&O connector

New Feature

  • Added Azure Entra ID client certificate authentication for Microsoft Dynamics 365 F&O connections. (CONC-13904)

Refer to Microsoft Dynamics 365 F&O connector to learn more.

Microsoft Dynamics CRM connector

Important

Subsequent to the November Runtime Release, an issue was reported that required the Microsoft Dynamics CRM connector to be rolled back to version 25.03.1.

Enhancement

  • Necessary runtime packages are now packaged with the connector. (CONC-18684)

Refer to Microsoft Dynamics CRM connector to learn more.

Microsoft SharePoint connector

New Feature

  • Added support for Test Query, Update, and Search Files actions. (CONC-18526)

Refer to Microsoft SharePoint connector to learn more.

Microsoft Windows SMB connector

GA Release

  • Introduced the Microsoft Windows Server Message Block (SMB) connector, now generally available. Provides core file operation support and Managed Cloud Service (MCS) compatibility. (CONC-18528)

Refer to Microsoft Windows SMB connector to learn more.

MQTT connector

New Feature

  • Enabled live status reporting for the MQTT listener on the Runtime Management → Listeners page. The status shows Listening when subscribed and Degraded, with error details, when the broker connection drops. (CONC-16607)

Refer to MQTT connector to learn more.

NetSuite REST connector

New Features

  • Added Attach support. Attach links an existing record, such as a Contact, to a target record, such as a Vendor Bill or Customer, without opening NetSuite. (CONC-16714)
  • Added a TCP Keep-Alive setting to keep connections open until NetSuite responds and prevent idle connection drops. (CONC-18349)
  • Added Detach support. Detach removes an existing link between records, such as a Contact from a Customer or Vendor Bill. (CONC-18776)

Fix

  • Resolved an issue where profile re-imports failed with a date parsing error when NetSuite returned timestamps without milliseconds. (CONC-17867)

Refer to NetSuite REST connector to learn more.

Oracle Database connector

Fixes

  • Resolved an issue where trying to perform an Insert operation by passing in a NULL value for the NUMERIC column, an “Embedded message: Input was lost during operation execution” message was returned. The connector is now able to insert a NULL value for non-null NUMERIC columns. (CONC-13325)
  • Resolved an issue where CLOB input parameters containing JSON were sent with invalid characters, which caused APEX_JSON.PARSE to fail. (CONC-13573)
  • Resolved an issue where stored procedures with OUT parameters containing nested collections of objects (3 or more levels of nesting) failed with Invalid column index: getValidColumnIndex. (CONC-14202, CONC-16633)
  • Resolved an issue where an Insert operation passing a NULL value into a NUMERIC column returned an Embedded message: Input was lost during operation execution error. The connector can now insert a NULL value into non-null NUMERIC columns. (CONC-13325)

Refer to Oracle Database connector to learn more.

Oracle E-Business Suite connector

Enhancement

  • Necessary runtime packages are now packaged with the connector. (CONC-19408)

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

REST Client connector

New Features

  • The REST Client connector now honors your observability trace context setting when exporting trace headers on outbound requests. Disabling the setting stops the connector from exporting tracestate and traceparent headers, while other headers remain unaffected. (RUN-11494)

  • The REST Client connector now support outbound distributed tracing. They automatically include trace headers on outbound requests, helping you track requests across connected systems. (RUN-11531)

  • The REST Client connector now forwards W3C trace context on outbound requests. Downstream services can correlate their own traces with the originating Boomi process. (RUN-11489)

Refer to REST Client connector to learn more.

Salesforce Apex connector

Enhancement

  • Downgraded the parent POM from version 4.0 to 3.2 to align with platform compatibility requirements. (CONC-19354)

Refer to Salesforce Apex connector to learn more.

Salesforce Marketing Cloud connector

Enhancement

  • Necessary runtime packages are now packaged with the connector. (CONC-18685)

Refer to Salesforce Marketing Cloud connector to learn more.

Salesforce Platform Events connector

Fix

  • Repackaged the libraries to facilitate updating the connector. (CONC-19219)

Refer to Salesforce Platform Events connector to learn more.

Salesforce Platform Events Pub/Sub (Early Access) connector

New Connector

  • Introducing the Salesforce Platform Events Pub/Sub (Early Access) connector that uses gRPC to send and listen for Salesforce platform events in real time. (CONC-17972)

Refer to Salesforce Platform Events Pub/Sub (Early Access) connector to learn more.

Salesforce REST connector

New Feature

  • Added a Query Parameters field to the Upsert operation for REST API and Composite REST API modes (not Bulk API V2.0). Set updateOnly=true to return an error instead of creating a record when no match exists. This requires an External ID Value and a Service URL on Salesforce API v61.0 or later. A blank External ID Value with updateOnly=true returns an application error. You can override parameters per document with the Query Parameters dynamic operation property. In Composite REST API mode, only the first document in each batch is used. (CONC-16611)

Enhancement

  • Updated the Parent Entities Depth and Child Entities labels, options, and help text in the Query operation, so you can see how each setting affects parent and child data in your profile. (CONC-18840)

Fixes

  • Resolved an issue where the connector did not honor the Batch Count configuration for more than 100 documents in the Create, Update, Upsert, and Delete operations. (CONC-17640)

  • Resolved an issue where the Query operation omitted direct parent objects from the Fields tab when Parent Entities Depth was 1 and child entities included parents. The Fields, filter, and sort panels now show all profile relationships. (CONC-18293)

Refer to Salesforce REST connector to learn more.

SAP JCO connector

Fixes

  • Resolved an issue where the SAP JCo connector did not recognize new IDoc fields until you restart the runtime or runtime cluster. (BSAP-673)
  • Resolved an issue where listeners failed to register on a fixed Central Gateway when you used the Message Server Host connection type. (BSAP-1013)
  • Resolved an issue where the SAP JCo connector added a space to the database name in SAP HANA and Microsoft SQL Server connection URLs, which caused TID management connection errors. (BSAP-765)
  • Resolved an issue where TID management setup failed on Microsoft SQL Server. (BSAP-1003, BSAP-1004, BSAP-1018)

Refer to SAP JCO connector to learn more.

SFTP connector

New Feature

  • The SFTP Listen operation now reports its live connection health on the Runtime Management → Listeners page, instead of only reflecting execution failures. (CONC-18836)

Fix

  • Resolved an issue where SFTP listeners beyond the 10-connection pool limit failed with a NullPointerException instead of a descriptive error. (CONC-16138)

Refer to SFTP connector to learn more.

Snowflake connector

New Features

  • Added OAuth 2.0 client credentials as an authentication type, alongside username and password and key-pair authentication. (CONC-18106)
  • Updated the tooltip for the Passphrase field. (CONC-19251)

Fix

  • Resolved an issue where GET operations ran an unnecessary COMMIT statement. (CONC-16032)

Refer to Snowflake connector to learn more.

Symitar - Partner connector

New Connector

  • Introduced the Symitar — Partner connector, enabling native integration between Boomi and Symitar®. Brings member data from the Symitar® core processing platform into the Boomi Enterprise Platform. (TPP-84)

Refer to Symitar - Partner connector to learn more.

On this Page