11.45 Harmony release notes

11.45 Harmony release

The 11.45 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.

Release notes are provided separately for App Builder 4.45 and Wevo iPaaS 11.45, which were also released 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 SDK connectors

• SugarCRM v2 connector
  The SugarCRM v2 connector is now generally available. It can be used with cloud or private agents to query, create, update, or delete records in SugarCRM.

Enhancements

Agent

• Microsoft Entra authentication and cloud agent support for Microsoft SQL Server
  Microsoft Entra authentication is now supported with the SQL Server Microsoft JDBC driver in an Integration Studio Database connection or a Design Studio Database source or target. This driver is newly provided on cloud agents.

• Windows quiet installer support for private agent monitoring
  Quiet Windows private agent installations can now have Jitterbit private agent metrics automatically enabled when the new parameter $Organization_id is set in the config64.ps1 file.

API Gateway

• Support for underscores in headers
  The API gateway now accepts headers with underscores.

EDI

• Support for user-defined statuses
  The Transactions page's Status column now shows user-defined statuses set through the EDI for Cloud v2 Set Status activity.

Integration Studio

• Visual indications of how an operation is triggered
  Icons indicating how an operation is triggered, including by schedule, API, or listener, have been added directly on operations in the design canvas.

• Improved use of visual space in transformations
  The vertical spacing between items in transformations and the script component palette has been reduced to allow more items to fit on the screen at once. In addition, you can now hide the display of source objects within mapped target fields by toggling off the new Show mapped source fields toggle (enabled by default).

Integration Studio SDK connectors

• Azure OpenAI connector support for custom data sources
  An Azure OpenAI connection's Optional settings has a new Add a data source checkbox that shows additional settings that enable you to interact with Azure OpenAI models using data in your Azure AI Search service. Once selected, you can use the new Select an Index checkbox in an Azure OpenAI Prompt activity to make selections based on the connected data source.

• BigCommerce connection default API version of V3
  New BigCommerce connections now have V3 selected as the default API Version. The selection V2 (Deprecated) remains available.

• Coupa connector R42 support
  The Coupa connector now uses version R42 of the Coupa Core Platform API. With this upgrade, the Coupa Pay Base and Worker Management objects are now supported. To use them with existing activities, refresh the schema.

• EDI for Cloud v2 connector ability to set a user-defined status
  The EDI for Cloud v2 Set Status activity request schema has a new user_defined_status field that can be used to set the status to one of the following: Warning, Pending, In progress, Validated, Rejected, Completed, On hold, Acknowledged. The status will appear in the status column on the EDI > Transactions page.

• Magento connector support for OAuth
  A Magento connection has a new Authentication type menu to select either OAuth-based authentication (newly supported) or Token-based authentication (default existing). To create and activate an integration in your Magento Admin panel and obtain credentials needed to configure an OAuth connection, see the Magento OAuth prerequisites.

Management Console

• Monitoring of licensing usage for API monthly calls
  The Dashboard's Licensed vs. Actual Use panel now shows the number of licensed API Manager API monthly calls and how many have been consumed in the current month. The license limit is not system-enforced.

• Private agent groups UX improvements and agent count
  These enhancements are available in the Private tab of the Agents page:

  • New menus allow you to filter agent groups by Status, Agent group, Agent name, or Environment name.
  • An explicit Add agent group button replaces the icon to add an agent group, whose configuration now opens in a side drawer instead of as an editable row in the table.
  • A new Agents count column shows the number of agents in each agent group.

Fixes

Agent

• JSONStringify support for null data and reserved JSON characters
  The JSONStringify function now handles null data and reserved JSON characters such as " and \ as expected.

  Warning

  If you previously implemented a workaround to escape reserved JSON characters, you must make updates to accommodate this fix or your operations dependent on this function may stop functioning as expected.

• Wildcard proxy exclusions now honored
  Wildcards (* or ?) included a private agent's proxy exclusion list (set by the jitterbit-utils --set-http-proxy-exceptions option) are now supported.

• FTP files no longer have unexpected prefixed timestamps
  In certain scenarios, files retrieved using the Integration Studio FTP connector or Design Studio FTP source no longer have unexpected timestamp prefixes requiring a workaround using the Jitterbit variable jitterbit.source.ftp.enable_regex_parser.

• Salesforce Bulk operations issue fixed
  A database error has been resolved with operations that use Bulk activities provided by the Integration Studio Salesforce, Salesforce Service Cloud, or ServiceMax connectors or the Design Studio Salesforce Bulk Process Wizard.

• Salesforce erroneous SOAP fault fixed
  An issue has been resolved with Salesforce operations where the operation status could report a SOAP fault when none occurred.

API Manager

• Migrated projects now retain API links
  After migrating a project with API Manager APIs and importing those APIs to the migrated project's environment, the API assignments now correctly link to the migrated project and its operations.

Integration Studio SDK connectors

• Stripe connector metadata structure corrected
  The structure of the metadata node in the request schema of Stripe connector activities has been corrected to properly handle metadata input. This resolves an error indicating Metadata values must be strings.

Notices

Agent

• End of life for version 11.27
  As of June 13, 2025, private agent version 11.27 has reached end of life and is no longer supported. We recommend that users of this version upgrade to the latest version as soon as practicable.

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.