11.49 Harmony release notes

11.49 Harmony release

The 11.49 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.49 and Wevo iPaaS 11.49 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

AI Agents and Marketplace

• AI Agents: Jitterbit Sales Agent and Jitterbit Knowledge Agent
  A new type of asset is offered in Jitterbit Marketplace in the new AI Agent type category. Jitterbit offers two AI agents that can be added to your license:

  • Jitterbit Sales Agent: An AI chatbot for your internal Sales team to quickly get answers about real-time sales orders, pricing, and customer data.
  • Jitterbit Knowledge Agent: An AI chatbot for your internal team to get intelligent answers from your organization's internal data.

Harmony platform

• Jitterbit Cloud Datastore (Beta)
  Jitterbit Cloud Datastore (Beta) is now available to all organizations at the Basic tier, a free tier that offers a single storage. Cloud Datastore is a Harmony platform service that allows users to store, retrieve, and manage data natively within the Jitterbit cloud. To provide feedback, contact the Jitterbit Product Team.

Integration Studio

• Decision (Beta) tool
  The new Decision (Beta) tool can be used to create conditional logic with IF statements and nested IF statements. Each condition evaluates to true or false and routes processing to different operations or operation chains based on the evaluation results. To provide beta feedback, contact the Jitterbit Product Team.

Integration Studio SDK connectors

• Amazon Bedrock (Beta) connector
  The Amazon Bedrock (Beta) connector is now available to all organizations. It can be used with cloud or private agents to register tools or send a prompt to Amazon Bedrock. To provide beta feedback, contact the Jitterbit Product Team.

• PGP (Beta) connector
  The PGP (Beta) connector is now available to all organizations. It can be used with cloud or private agents to encrypt, decrypt, or sign files in compliance with the OpenPGP encryption standard. To provide beta feedback, contact the Jitterbit Product Team.

Enhancements

Agent and Integration Studio

• NetSuite connector search type for returning saved search fields as output
  A NetSuite Search activity has a new search type, Saved Search with result fields as output, available to select in activity configuration step 2. The new search type requires agents version 11.49 or later and a deployed Suitelet script to fetch the metadata needed to limit the response schema fields.

Agent and Management Console

• Endpoints Usage (Beta) reporting
  The Dashboard page's Licensing vs Actual Usage tile now reports the number of licensed endpoints compared with how many unique endpoints have been used in the current month on agents 11.49 or later in a production-class environment. Unique endpoints are determined by their Endpoint unique identifier values, shown on the new Endpoints Usage (Beta) page, where you can also see month-by-month usage.

  Agents version 11.49 or later are required for endpoints usage reporting. When upgrading to an 11.49 or later agent from an earlier version, you are notified that Connector SDK-based connectors will be updated to the latest version.

  To provide beta feedback, contact the Jitterbit Product Team.

API gateway

• Log rotation support
  The private API gateway now has log rotation enabled for NGINX logs. You can configure the log rotation settings in the /etc/logrotate.d/nginx file.

Integration Studio and Design Studio

• NetSuite WSDL version 2025.2 support
  Jitterbit has verified support for NetSuite WSDL version 2025.2 with the Integration Studio NetSuite connector and the Design Studio NetSuite connector. An agent or Design Studio upgrade is not required. In addition, the 2025.2 WSDL is now the default WSDL download URL for a new Integration Studio NetSuite connection.

Integration Studio

• New method to preserve JSON names
  The new setting Preserve JSON names in the Advanced tab of the project settings uses a new method to generate XSD schema structures from a JSON schema. The new setting is enabled by default for new projects using agent version 11.48 or later and is disabled for existing projects to retain existing behavior. Learn more in the documentation.

  Important

  Enabling the new setting for existing projects is not recommended unless advised by support. Toggling the setting on or off does not impact already configured project components.

• Transformation UX improved
  The user experience in transformations has been improved:

  • You can now resize the left panel (source fields and variables) and right panel (script component palette) on either side of a transformation.
  • The left and right panels can now be collapsed and expanded in any context, and never auto-collapse.
  • The user-defined state is saved on closing the transformation.

Integration Studio SDK connectors

• Microsoft Sharepoint 365 connector clarification of object type
  During configuration of Microsoft Sharepoint 365 Create, Query, Update, and Delete activities, object selection screens now show a Type column to differentiate between multiple objects that have the same Name and Description.

• PGP (Beta) connector Sign activity
  The new PGP (Beta) Sign activity can be used to sign files in compliance with the OpenPGP encryption standard. To provide beta feedback, contact the Jitterbit Product Team.

• Shopify connector API 2025-07 and 2025-04 support
  A Shopify connection's API Version menu now has REST Admin API versions 2025-07 and 2025-04 as selections. If updating an existing connection, see steps for changing the API version.

Management Console

• Cloud Datastore (Beta) usage reporting
  The Cloud Datastore (Beta) page has a new Usage tab that shows storage usage for the selected month. In addition, the Dashboard page's Licensing vs Actual Usage tile has a new Cloud Datastore storages metric reporting the number of licensed storages compared with how many storages have been used in the current month.

• Environment refresh option on the Message Queues page
  The Message Queues page settings drawer has a new Sync updated environment names option to refresh the list of environments available to select.

Fixes

Integration Studio

• Transformation performance improvements
  Transformations with large JSON schemas (many nodes and fields) no longer result in the transformation page freezing when interacting with the user interface.

• Duplicating a node no longer corrupts a transformation
  Duplicating a node in a transformation can no longer cause issues in the transformation that require it to be rebuilt.

• Unused global variables no longer appear
  Unused or duplicate global variables that are not referenced by any other project components no longer automatically and persistently appear in the project pane's Components tab even after manual deletion.

• Shopify Query activity special characters in node and field names now supported
  When the new Preserve JSON names Integration Studio project setting is enabled, a Shopify Query activity's request schema field name location_ids[] is no longer incorrectly sent as location_ids__ at runtime. Note that the schema will continue to show location_ids__ in the schema at design time but at runtime the expected JSON name will be processed. Note that you must reconfigure the operation after enabling the new project setting to apply this fix. To verify or troubleshoot this behavior, see Special characters in connector-provided JSON schemas in Operation troubleshooting.

Integration Studio SDK connectors

• BigCommerce V2 API relabeled
  A BigCommerce connection's API Version menu now shows the selection V2 instead of V2 (Deprecated). The original label was misleading, as only some of BigCommerce's V2 APIs are deprecated by BigCommerce, and not the entire V2 API.

• HTTP v2 connector retry logic fixed
  An issue has been fixed with the HTTP v2 connector that resulted in indefinite retry attempts. The response is now properly closed so that the configured retry settings are honored.

Management Console

• Jitterbit Multipart Pipeline Plugin fix for header processing
  A new version of the Jitterbit Multipart Pipeline Plugin (deprecated) (version 1.0.9.0) ignores filename* provided in a Content-Disposition header. This resolves an issue where passing the encoded payload to another transformation was resulting in the error Failed to convert JSON file to XML. The new version is associated with cloud agents and can be associated with private agents from the Customizations > Plugins page.

• Cloud Datastore (Beta) empty storages can now be deleted
  In the Cloud Datastore (Beta) page, you can now delete custom fields on storages that are not in use and have no data.

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:

  • 16.50.32.215
  • 16.51.140.139
  • 16.51.180.48

  The new IPs will go into effect for the APAC Sandbox Cloud Agent Group with its 11.51 upgrade on October 21, 2025. The new IPs went into effect for the APAC Production Cloud Agent Group with its 11.48 upgrade on August 26, 2025. If you don't add these IPs, dependent integration operations will stop functioning as intended.

  On October 21, 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 and API gateway

• End of life for version 11.31
  As of September 5, 2025, these product versions have reached end of life and are no longer supported:

  • Private agent version 11.31
  • Private API gateway version 11.31

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

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. The Integration Studio Snowflake connector supports both OAuth and key-pair authentication as of the 11.48 release.

Integration Studio SDK connectors

• User action required: Upcoming removal of deprecated Cloud Datastore Query Items activity
  In an upcoming release, the deprecated Query Items activity in the Cloud Datastore (Beta) connector will be permanently removed. This activity was replaced in the 11.47 release by the redesigned Query Items activity, whose flattened response 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

  If you are using the deprecated Query Items activity in any operations, you must review your operation design and replace it with the redesigned Query Items activity as soon as possible, as the deprecated activity is no longer supported and will be removed in the future.