11.43 Harmony release notes

11.43 Harmony release

The 11.43 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.43.0 and Wevo iPaaS 11.43, 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

Harmony Platform, Integration SDK connectors, and Management Console

• Jitterbit Cloud Datastore (Beta)
  Jitterbit Cloud Datastore (Beta) is a new Harmony platform service that allows users to store, retrieve, and manage data natively within the Jitterbit cloud. For beta access and to provide feedback, contact the Jitterbit Product Team.

  • The new Management Console Cloud Datastore (Beta) page provides the ability to create and manage status storage or key storage for your data.

  • The Management Console Access Tokens page has a new Cloud Datastore scope to allow you to access your cloud storage within Integration Studio.

  • The new Integration Studio Cloud Datastore (Beta) connector can be used with cloud or private agents to create or delete storage; query, insert, update, or delete items; or get metrics about your cloud storage usage.

Integration Studio SDK connectors

• Amazon Lambda (Beta) connector
  The new Amazon Lambda (Beta) connector can be used with cloud or private agents to get a function, or list or invoke functions in AWS Lambda. The connector also supports getting an asynchronous response from an Amazon SQS queue with private agents that have been enabled for event listening. To provide beta feedback, contact the Jitterbit Product Team.

• Microsoft Azure Files (Beta) connector
  The new Microsoft Azure Files (Beta) connector can be used with cloud or private agents to get a file or list, create, move, or delete files in Microsoft Azure Files. To provide beta feedback, contact the Jitterbit Product Team.

Enhancements

Agent and Management Console

• Jitterbit private agent metrics (Beta)
  Private agent monitoring can now be done directly within the Management Console (in addition to existing beta functionality via third-party observability platforms). To provide feedback on these beta features, contact the Jitterbit Product Team.

  • The Management Console Agents page has a new Metrics (Beta) tab that reports agent and agent group metrics such as health, capability, and data on each of an agent's services.

  • The Management Console Dashboard page has a new Agents Health (Beta) tile that shows a summary of agent health.

  • The Management Console Access Tokens page has an Agent Metric scope used to set a default access token for each Harmony organization. (Generating an additional metrics access token is required only if you use auto-registered private agents.)

  • A private agent's jitterbit.conf configuration file has a new [AgentMetrics] section to configure the Jitterbit metrics service. To start generating metrics, you must set these parameters for every private agent you want to monitor.

  • Additional supporting agent changes, such as new commands in a private agent's jitterbit utility program, metrics.log and metrics_service.log log files, Docker agent ENABLE_JITTERBIT_METRICS environment variable, and Docker agent register.json file agentMetricsToken field.

EDI

• New dialog for adding an existing trading partner
  When creating a trading partner, a message now prompts you to add an existing trading partner to your environment if the provided qualifier and ISA ID match one that already exists.

• Manual assignment of new connections
  New FTP and AS2 connections are no longer automatically assigned to trading partners. Now, once you create one, you must manually assign it to a partner.

• Additional X12 and EDIFACT document type support
  A workflow's Document Type menu supports additional document types for X12 and EDIFACT standards.

• Additional FTP filename parameter support
  An FTP connection's Remote upload file name field supports using additional parameters enclosed in braces.

Integration Studio

• Invoke Operation (Beta) tool support for asynchronous operations and error handling
  The Invoke Operation (Beta) tool now has a Run type option to select Synchronously (default existing) or Asynchronously. In addition, new Error handling options have been added, including Raise error if operation fails and Cancel operation chain if operation fails. The new settings are available only for new instances of this tool; for an existing tool, replace it with a new instance.

• Optional auto-numbering of operations
  A new project settings tab, Designer, contains a new setting that can be enabled to show a sequential number preceding each operation name on the design canvas.

• General availability of updated UI
  The new version of the Integration Studio user interface, which features condensed components on the design canvas and improved readability, is now used for all projects. The toggle that was previously available to switch to the legacy UI has been removed.

Integration Studio SDK connectors

• BigCommerce connector support for additional Catalog sub-objects
  When the API Version selected in a BigCommerce connection is V3, the following additional Catalog sub-objects are now supported: brands_catalog, categories_catalog, category-trees_catalog, product-modifiers_catalog, product-variant-options_catalog, and product-variants_catalog.

• Epicor Kinetic connector support for Kinetic 2025.1
  The Epicor Kinetic connector has been verified to be supported with Kinetic version 2025.1 (ERP build version 12.0.100).

Changes

Integration Studio

• Global endpoints terminology updated
  An endpoint that can be configured and used across projects in an environment is now referred to as a global endpoint (previously called a global connection) throughout the product.

• Move to trash action relocated
  In project list view, the option to move a project to the trash has been moved from an item within the actions menu to a Move to trash icon directly within the Actions column.

• Operation status bar UI changes for debug logging
  The operation status bar now shows a green icon instead of blue when debug logging is enabled, and you can now click it to open the operation debug log settings in a side drawer. Previously, a Disable button was shown in the operation status bar.

Management Console

• Dashboard licensing tile renamed
  The Dashboard's tile that shows information about a Harmony organization's licensed limits has been renamed to Licensed vs. Actual Use.

Fixes

Agent

• IfNull and IsNull functions now have expected behavior
  When the Jitterbit variable jitterbit.target.xml.include_nil_attribute is set to true upstream of the IfNull or IsNull functions, the functions will evaluate an empty string as a non-null value.

Integration Studio

• Searching an operation's log now returns child operation results
  When viewing an operation log for a specific operation, searching within the log now also returns logs for child operations.

• Testing an ODBC Database connection no longer fails
  Testing a Database connection that uses an ODBC driver no longer erroneously returns an error indicating keys and value arrays have different sizes.

Integration Studio SDK connectors

• Amazon S3 Put Object activity support for large files
  An Amazon S3 Put Object activity now properly handles uploading files larger than 5 MB.

• Microsoft Azure Service Bus connection error resolved
  Testing a Microsoft Azure Service Bus connection no longer results in an error indicating the connector is partially loaded. Instead the connection will either be successful or return an appropriate error message indicating the reason for the error.

Notices

Agent, API gateway, and Design Studio

• End of life for versions 10.87 / 11.25
  As of May 2, 2025, these product versions have reached end of life and are no longer supported:

  • Private agent versions 10.87 and 11.25
  • Private API gateway version 10.87
  • Design Studio version 10.87

  We recommend that 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.