11.40 Harmony release notes

11.40 Harmony release

The 11.40 Harmony release is staggered based on the dates and times as listed below by component and region. For a more detailed explanation of the release cadence by component category, see the release schedule.

The 11.40 Harmony release also includes the release of App Builder 4.40.0, whose release notes are provided separately. Jitterbit also released Wevo iPaaS 11.40 during this timeframe.

Compilations of release notes for Production Cloud Agent Groups, Sandbox Cloud Agent Groups, and private agents are also available.

You can subscribe to maintenance notifications for web-based components at Jitterbit Trust. Locally installed components are available from the Downloads page (except for the Docker private agent and Docker private API gateway, which are available at Docker Hub). The end-of-life date for these components is one year after the release date.

New features

Integration Studio

• Connector Builder AI assistant (Beta)
  Create a custom connector with Connector Builder by interacting with a chatbot using natural language. If enabled for your organization, you can access the Connector Builder AI assistant (Beta) with the Build Connector with AI button on the Connector Builder page. For access to this beta feature, contact the Jitterbit Product Team.

Enhancements

Agent

• Microsoft Windows Server 2025 support
  The Microsoft Windows Server 2025 operating system is now supported for private agents 11.40 and later. Also beginning with this release, Amazon Linux AMI 2 is no longer supported, as described under Notices below.

Integration Studio

• New UI default for new projects
  The Try the new UI toggle that shows a redesigned user interface is now enabled by default for new projects. The new UI is selected per user rather than per organization. To provide feedback on the new design, contact the Jitterbit Product Team.

Integration Studio SDK connectors

• Azure OpenAI connector support for tools
  The new Azure OpenAI Register Tools activity allows you to add tools such as file search, code interpreter, and function calling to an existing chatbot assistant. In addition, the Prompt activity has a new Role menu where you can select the type of prompt: Assistant, System (default existing), Tool, or User.

• Microsoft Entra ID and D365 Business Central v2 Update activity support for OData type annotations
  The Microsoft Entra ID Update activity and Microsoft Dynamics 365 Business Central v2 Update activity each have a new Optional setting in step 1 of their configuration: Set OData type on payload. When selected, @odata.type annotations are automatically added to applicable properties in the JSON payload. Enabling this setting can resolve errors related to incompatible data types.

Fixes

API gateway

• EMEA domain corrected
  The private API gateway now uses emea-west.jitterbit.com to connect in the EMEA region as listed in Jitterbit's allowlist information. Previously, emea.jitterbit.com was being used.

• APIs no longer fail after their creator is deactivated
  Deactivating a Harmony user that created an API Manager API no longer causes the API URL to stop working.

Integration Studio

• Transformation output corrected for #text nodes
  Transformation mappings that use #text nodes now generate the expected output, as they now take into consideration that those nodes may contain different value types (for example, an object structure value or a simple text value). To apply this fix in existing transformations, first redeploy the operation before executing it.

• Projects page environments filter now pins the All Environments selection
  The Filter by menu on the Projects page now always shows All Environments at the top of the list. Previously, environment names that were alphabetically ordered before the words All Environments were appearing first.

• Changing the WSDL of an API SOAP Request and Response activity can no longer prevent project deployment
  After changing the WSDL of an existing API SOAP Request or API SOAP Response activity, you must use the Next button to regenerate schemas; it is no longer possible to use the Save & Exit button at that point. This resolves an issue where the project could get into a state where it could not be deployed. If you are already in this situation, see recovery steps.

Integration Studio SDK connectors

• Microsoft Entra ID Query pagination issues resolved
  Microsoft Entra ID Query activity pagination issues have been resolved so that it is now possible to retrieve all records. By default, 100 records are returned. To retrieve more, use the Top attribute to fetch up to 999 values. If more than 999 values need to be fetched, use the Page Size parameter.

• Microsoft SharePoint Server whitespace issue resolved
  The Microsoft SharePoint Server connector now handles whitespace in table and column names as expected.

Notices

Agent and API gateway

• Update to supported operating systems
  Amazon Linux AMI 2 is no longer supported with 11.40 and later private agents and private API gateways. This version may still work but is no longer tested by Jitterbit. See the currently supported private agent operating systems and private API gateway operating systems.

Agent and Design Studio

• End of life for versions 10.84 / 11.22
  As of March 1, 2025, these product versions have reached end of life and are no longer supported:

  • Private agent versions 10.84 and 11.22

  • Design Studio version 10.84

  We recommend that all users of these versions upgrade to the latest version as soon as practicable.

Agent

• Private agent versions 10.x are no longer updated
  Private agent version 10.87 was the last 10.x agent version distributed by Jitterbit and is intended to be the final supported 10.x agent version.

  Since Harmony release 10.63 / 11.1, both a 10.x and 11.x private agent version had been distributed with these differences:

  • 11.x versions: In 11.1 and later versions, the PostgreSQL database bundled with the private agent is now version 14.5-1.

  • 10.x versions: Supported 10.x versions are packaged with the existing 9.6.24-1 PostgreSQL. The distributed 10.x versions will continue to be supported in accordance with Jitterbit's end-of-life policy.

  Important

  To continue to receive private agent updates, including new features, enhancements, security patches, and fixes, upgrading to an 11.x private agent is required.

  Follow the instructions to upgrade from 10.x to 11.x agents:

  • Windows agent upgrade instructions (requires a complete uninstall)

  • Linux agent upgrade instructions

Design Studio

• User action required: Salesforce retirement of API versions 21 to 30
  Salesforce has announced the upcoming retirement of Salesforce Platform API versions 21.0 through 30.0 in its Summer '25 release (May or June 2025).

  As the Design Studio Salesforce connector has a feature that allows users to defer an upgrade of the Salesforce API version when opening an existing project that uses an earlier API version, it is possible that you may have projects using a Salesforce API version that is being retired. Any affected projects would have been originally created using Design Studio and agent versions earlier than Harmony 8.8 (released in March 2016).

  We recommend following these steps to verify each Design Studio project uses a supported Salesforce API version as soon as possible to avoid issues with those integrations.

Design Studio and Integration Studio

• User action required: Snowflake user TYPE property must be updated and future deprecation of single-factor authentication
  Snowflake has announced the upcoming deprecation of single-factor authentication, which affects Integration Studio and Design Studio integrations that connect to Snowflake using a password.

  For those affected, user action is required in two phases:

  1. By March 31, 2025, the TYPE property of the user account you use to connect to Snowflake must be set to LEGACY_SERVICE in order to continue using password-based authentication (see Types of users). Without user action, existing integrations using Snowflake single-factor password authentication are expected to begin failing in April 2025.

  2. By November 2025, you must update the type of authentication used to connect to Snowflake to OAuth or key-pair authentication. At this time, password-based authentication will no longer be supported. In an upcoming release, the Integration Studio Snowflake connector will be updated to add support for the newly required authentication methods.