11.47 Harmony release notes

11.47 Harmony release

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

App Builder 4.47 and Wevo iPaaS 11.47 have separate release notes.

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. Docker private agent, private API gateway, and App Builder images are available at Jitterbit's Docker Hub. The end-of-life date for these components (except App Builder) is one year after the release date.

New features

Agent

• Agent observability metrics
  Private agent observability metrics for both native monitoring and third-party platforms are now generally available:

  • Native monitoring: Once configured and enabled, shows agent metrics in the Metrics tab of the Management Console Agents page.
  • Datadog or Elasticsearch: Shows agent metrics in your configured observability platform.

EDI

• Analytics
  A new EDI page, Analytics, allows you to view and export EDI transaction data in an environment.

Integration Studio

• Selective Transfer (Beta)
  The new Selective Transfer (Beta) option allows you to transfer project components from one environment to another without migrating the entire project, enabling the ability to:

  • Make changes in a development environment that you can omit from promotion to a target environment.
  • Promote changes you want to move individually without affecting components that other collaborators may be working on.

  To provide feedback on this beta feature, contact the Jitterbit Product Team.

Integration Studio SDK connectors

• Amazon Bedrock (Beta) connector
  The new Amazon Bedrock (Beta) connector can be used with cloud or private agents to register tools or send a prompt to Amazon Bedrock. For beta access and to provide feedback, contact the Jitterbit Product Team.

• Amazon Lambda connector
  The Amazon Lambda connector is now generally available. It 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.

• Microsoft Azure Files connector
  The Microsoft Azure Files connector is now generally available. It can be used with cloud or private agents to get a file or list, create, move, or delete files in Microsoft Azure Files.

• PGP (Beta) connector
  The new PGP (Beta) connector can be used with cloud or private agents to encrypt or decrypt files in compliance with the OpenPGP encryption standard. For beta access and to provide feedback, contact the Jitterbit Product Team.

Enhancements

Agent, Integration Studio, and Design Studio

• Salesforce API version 64 support
  Salesforce API version 64 is now supported for these connectors:

  • The Integration Studio Salesforce, Salesforce Service Cloud, and ServiceMax connectors automatically use this API version with 11.47 or later agents.
  • The Design Studio Salesforce connector supports this API version with the use of both 11.47 or later agents and an 11.47 or later version of Design Studio. When both these version requirements are met, an API upgrade dialog is shown when opening existing projects using this connector.

API Manager

• UX updates for API and security profile configuration
  Updates to improve the user experience have been made in these areas:

  • The Security Profiles page has been redesigned with an updated look and feel.
  • Editing an API or security profile now takes place in an API details drawer instead of a modal.

• Analytics health filter controls
  The API Health Monitoring table on the Analytics page has a new Filter columns icon to change the visibility of columns shown in the table.

EDI

• Ability to search for and filter connections
  The Admin page's Communication settings tab now has a search bar and menus to filter by communication type or status.

• Display of user-defined statuses and transaction counts in the filters pane
  The Transactions and Archive pages' Filters panes now show all user-defined statuses. On the Transactions page, you can also see the number of transaction instances for each filter selection.

Harmony portal

• Menu navigation redesign
  A redesigned Harmony portal menu improves the experience of navigating within and between applications.

• Dropdown menu typeahead support
  Dropdown menus across all Harmony web applications now support the ability to begin typing to filter the menu selections.

Integration Studio

• Invoke Operation (Beta) tool option to use the operation name
  The Invoke Operation (Beta) tool has a new Use operation name checkbox that gives the name of the tool the same name as the operation being invoked.

• Transformation UI improvements
  Transformations have the following improvements to their user interface:

  • A redesign of the area where you specify a source or target schema in a transformation, including support for dragging and dropping files to upload them.
  • A View menu in the transformation toolbar that provides the option to hide or show mapping lines, mapped source fields, node lines, cardinality (now hidden by default), and field type.
  • New target field options: Toggle to hide/show an individual mapped source field, toggle to expand/collapse the script editor, or click to add a custom value.

Integration Studio SDK connectors

• Azure OpenAI connector support for Azure Cosmos DB, citations, and registering tools with cloud agents
  The following enhancements to the Azure OpenAI connector have been made:

  • A connection now has Azure Cosmos DB for MongoDB vCore available to select as a data source in its Optional settings.
  • When using a connected data source, a Prompt activity now has a citation field in the message field in its response schema.
  • The Register Tools activity is now supported on cloud agents. Chat history management is not available on cloud agents and remains a private agent-only capability.

• Cloud Datastore (Beta) Query Items activity redesign
  The Cloud Datastore (Beta) connector has a newly designed Query Items activity whose response schema has a flattened structure compared with that of the old Query Items activity (now shown as Deprecated in the UI), whose response returns nested fields. This change in structure makes it so the individual fields you define in the Management Console Cloud Datastore (Beta) page are returned directly at the top level of the response.

  Important

  The deprecated Query Items activity remains available in the UI to retain compatibility with existing operations; however, you should review your operation design and replace it with the newly designed activity as soon as possible, as the deprecated activity is no longer supported.

• OpenAI connector support for registering tools with cloud agents
  The OpenAI Register Tools activity is now supported on cloud agents. Chat history management is not available on cloud agents and remains a private agent-only capability.

• PagerDuty connector support for OAuth 2.0
  A PagerDuty connection has a new Authentication menu to select either API Token (default existing) or OAuth 2.0 (newly supported). To set up a PagerDuty app and obtain credentials needed to configure an OAuth connection, see PagerDuty OAuth 2.0 prerequisites.

Management Console

• New licensing metric for agent grouping
  The new Agent grouping for HA (high availability) metric on the Dashboard page's Licensing vs Actual Usage tile gives you greater visibility into how your agent group usage aligns with your license. This metric reports the number of licensed HA agent groups compared with how many are in use, based on the number of agent groups with two or more agents used over the past 12 months in a production-class environment. With this change, the former Agent Groups metric shown on the Dashboard tile has been removed.

Fixes

API gateway

• Status code of 0 no longer returned
  In certain situations when an API gateway timeout occurs, a proper 504 status code is now returned instead of a status code of 0.

Integration Studio

• Activity saving error no longer occurs
  An issue no longer occurs where some activities could not be saved, returning the error Item size has exceeded the maximum allowed size.

• Valid scripts no longer incorrectly marked as invalid
  An issue no longer occurs where some mapping scripts referencing source objects were incorrectly identified as invalid with an error reporting incorrect occurrence.

Notices

Agent

• User action required: New APAC cloud agent IPs
  If you use APAC region cloud agents to access endpoints within your network behind a firewall, you must allow three additional IP addresses by August 18, 2025:

  • 16.50.32.215
  • 16.51.140.139
  • 16.51.180.48

  The new IPs will go into effect with the 11.48 Sandbox Cloud Agent Group and Production Cloud Agent Group upgrades. If you don't add these IPs by August 18, 2025 for the Sandbox Cloud Agent Group or August 26, 2025 for the Production Cloud Agent Group, dependent integration operations will stop functioning as intended.

  After August 26, 2025, you may also remove the following IP addresses, which are being decommissioned:

  • 3.0.141.187
  • 13.251.231.2
  • 52.220.155.2

  For additional information, see APAC IP changes FAQ. All IP addresses that must be added to ensure communication inbound to your network from cloud agents are listed in Jitterbit allowlist (whitelist) information.

Agent, API gateway, and Design Studio

• End of life for version 11.29
  As of July 25, 2025, these product versions have reached end of life and are no longer supported:

  • Private agent version 11.29
  • Private API gateway version 11.29
  • Design Studio version 11.29

  We recommend that users of these versions 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.