11.59 / 12.3 Harmony release notes

11.59 / 12.3 Harmony release

The 11.59 / 12.3 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.59 and Wevo iPaaS 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

• CRM Contact Agent
  The CRM Contact Agent, accessed from the Marketplace AI Agent category, uses AI to manage contact records for CRM systems such as Salesforce through a conversational interface, helping sales teams find, create, and update contacts more efficiently. To add it to your license, contact us.

• Competitor Intel Agent
  The Competitor Intel Agent, accessed from the Marketplace AI Agent category, automates market intelligence gathering by using AI-powered web search to identify, summarize, and deliver relevant industry news and competitor updates to your team. To add it to your license, contact us.

EDI

• EDI AI Assistant
  The EDI AI Assistant can be used to manage and configure Jitterbit EDI by interacting with an AI assistant using natural language. You can access it using the Jitterbit AI icon in the Harmony portal header on any Jitterbit EDI page. To add it to your license, contact your Customer Success Manager (CSM).

Studio SDK connectors

• Chroma connector
  The Chroma connector is now generally available. It can be used with cloud or private agents to search for, upsert, or delete records in a Chroma database collection.

• Wikipedia connector
  The Wikipedia connector is now generally available. It can be used with cloud or private agents to retrieve objects from Wikipedia.

Enhancements

Agent

• Improved performance and security
  Version 12.3 private agents include performance and security enhancements. These enhancements are not included in version 11.59, which is the final planned release for 11.x private agents. You can upgrade directly from an 11.x private agent to 12.3 (or later 12.x versions) using our upgrade instructions (Windows, Linux, or Docker).

  Actions required: Plugin updates and verification of custom connectors for 12.x private agents

  • Plugin updates for 12.x private agents
    Performance and security enhancements for 12.x private agents are incompatible with the Multipart Pipeline and AWS S3 Create Plugins. If you use these plugins, user action is required as described under Notices below.

  • Verification of custom connectors for 12.x private agents
    Connector SDK connectors that are provided by a third party must undergo development changes to be compatible with 12.x private agents. Before upgrading to 12.x private agents, verify compatibility with the connector developer, or operations using those connectors will begin failing at the time of upgrade.

• Private agent settings to mask custom request headers in logs
  A new [Masking] section in the private agent configuration file (jitterbit.conf) allows you to mask custom request headers in Studio HTTP activities and Design Studio HTTP sources and targets within runtime logs. Applies to both 11.59 and 12.3 private agents.

• Endpoints Usage proxy support
  The Management Console Endpoints Usage page now reports endpoint usage for private agents communicating via a proxy server. Applies to both 11.59 and 12.3 private agents.

• Improved agent sync error handling
  Agents now handle errors during sync operations more reliably, preventing database conflicts that could result in deadlocks. Applies to both 11.59 and 12.3 private agents.

Agent, Studio, and Design Studio

• Improved GetJSONString function with support for error handling
  The new GetJSONStringEx function, accessible in the JSON category of the Studio script component palette's Functions tab, has the same behavior as the GetJSONString function with added support to return a customizable value when a path doesn't match. This function requires agent version 11.59 / 12.3 or later and can also be used with Design Studio version 11.59 or later.

• Salesforce connector support for OAuth 2.0
  Jitterbit's Salesforce connectors now support using 2-legged OAuth 2.0:

  • Studio: A Salesforce connection has a new Authentication type menu where you select Basic Auth (default existing) or OAuth 2.0 Client Credentials (newly supported with agent version 11.59 / 12.3 or later). See OAuth 2.0 prerequisites.
  • Design Studio: A Salesforce Org has a new Select OAuth 2.0 Client Credentials checkbox that requires both Design Studio version 11.59 or later and agent version 11.59 / 12.3 or later. See OAuth 2.0 prerequisites.

Agent and Design Studio

• Salesforce API version 65 support
  The Design Studio Salesforce connector now supports Salesforce API version 65 with the use of both Design Studio version 11.59 or later and agent version 11.59 / 12.3 or later. When both these version requirements are met, an API upgrade dialog is shown when opening existing projects using this connector. New projects automatically use Salesforce API version 65 and must be configured with OAuth 2.0 authentication.

  Basic authentication no longer supported by Salesforce

  Starting with Salesforce API version 65, Salesforce no longer supports SOAP API login (basic authentication). To ensure continued operability with Design Studio Salesforce Orgs configured to use basic authentication, do not accept the prompt to upgrade your existing Design Studio projects to Salesforce API version 65. Before upgrading projects to Salesforce API version 65, you must reconfigure your Salesforce endpoints with the new Select OAuth 2.0 Client Credentials configuration option or your operations will fail.

API Manager, Management Console, and Studio

• Redesigned Analytics interface and API request data in operation logs
  Two new features are being rolled out gradually over the next month. If you're interested in early access, contact Jitterbit support.

  Redesigned Analytics interface

  The Analytics page in API Manager has a redesigned interface. The new interface includes:

  • New analytics views: Error breakdown by status codes (success vs. error), organization-level rate limit utilization (average calls per minute), policy violation tracking, and method-level insights. Existing charts now also include min/max response time and environment data.
  • Chart management: Charts can be reordered and expanded. Legends can be individually enabled or disabled, and are always fully visible regardless of the number of items. Hover over data points to view detailed metrics.
  • Updated filters: A new Methods filter is available. Active filters show a count badge and can be cleared individually or all at once with Clear filters.
  • Redesigned time period selector: Choose from preset relative ranges or specify an absolute date range using the new Relative and Absolute tabs.
  • Fix: 504 timeout errors are resolved in organizations with large numbers of APIs, particularly when filters are applied.

  Until your organization is upgraded, the previous interface remains available as the legacy Analytics interface.

  Important

  When the new interface is enabled for your organization, the retention period for analytics data and API logs changes from 90 days to 30 days.

  API request data in operation logs

  When an operation is triggered by an API Manager custom API or OData API, you can now see which API triggered the operation directly in the Studio operation log view and the Management Console Runtime page. Operation logs for API-triggered operations now include:

  • API information: API name, type, request method, API request ID, source IP, API gateway, API service URL, and source application.
  • Call information: HTTP request headers sent with the API call.
  • Call log: Detailed trace information about API request processing.

  When operation debug logging and API verbose logging are both enabled, request and response headers and body are also included. The amount of information logged varies by configuration.

EDI

• Trading partner EDI ID validation
  Jitterbit EDI now validates that EDI IDs follow the correct format for the trading partner's EDI standard (X12, EDIFACT, or TRADACOMS) and are not already assigned to another partner.

Management Console

• Organization policy to shorten session timeout and consolidation of TFA settings
  The User Management tab of the Organizations page's Organization Policies has the following enhancements:

  • A new Enforce shorter idle session timeout toggle allows you to shorten the amount of time after which users will be logged out of the Harmony portal, down to a minimum of 5 minutes. The maximum amount of time (and the existing default when the toggle is disabled) is 4 hours.
  • Two separate two-factor authentication (TFA) policy toggles have been consolidated into a single parent toggle with two sub-options: With token expiry (selected by default) and At every login. The functionality remains the same.

Studio and Design Studio

• Jitterbit variables for preserving whitespace in XML and JSON source data
  Two existing Jitterbit variables, jitterbit.source.xml.trim and jitterbit.source.json.trim, are now exposed in the Studio script component palette's Variables tab and Design Studio (11.59 or later) script builder's Data Elements tab. These variables can be set to false to prevent trimming of whitespace from XML or JSON source data respectively.

Studio

• Variable support in additional connector fields
  The following connector activity fields now show a variable icon and support using global variables, project variables, and Jitterbit variables. In addition, Private Key connection fields for the Cloud Firestore, DocuSign, Gmail, Google BigQuery, Google Docs, Google Drive, Google Pub/Sub, Google Sheets, and Workday connectors also now support variables.

  Connector	Activity	Field
  Amazon Bedrock	Prompt, Register Tools	Prompt
  Amazon Lambda	Invoke Function	Client Context
  Azure OpenAI	Prompt, Request Image	Prompt text
  BMC Helix Business Workflows	Search Cases, Create Case, Update Case	Search parameters (in JSON format), Create parameters (in JSON format), and Update parameters (in JSON format)
  BMC Helix Operations Management	Create Event, Search Events, Update Event	JSON input
  Email	Send Email	Mail Body
  Gmail	Send Email	Message
  Google BigQuery	Execute Custom Query	SQL Query
  Google Gemini	Prompt, Register Tools	Prompt
  OData	Update	Request Headers
  OpenAI	Create Image, Create Transcription, Create Translation, Prompt	Prompt text
  PGP	Encrypt	Recipient public key, File content, Sender public key

• Autoselect dependencies toggle for selective transfer
  The selective transfer feature has a new Autoselect dependencies toggle (enabled by default) that controls whether required dependencies are automatically included when selecting components. Disable it to select components individually without including their dependencies.

• Publish as an API UX redesign
  The Publish as an API option now opens an API details drawer with tab-based steps along the bottom of the project designer instead of a separate configuration modal.

Studio SDK connectors

• HTTP v2 connector support for NetSuite REST web services via 3-legged OAuth
  NetSuite's SuiteTalk REST web services are now supported using an HTTP v2 connection's OAuth 2.0 authentication type with the Authorization Code Grant option (3-legged OAuth). For setup instructions, see Connect to NetSuite with HTTP v2 to configure the NetSuite integration record and Management Console app registration.

• EDI for Cloud v2 Get Documents and List Transactions enhancements
  The EDI for Cloud v2 connector has the following enhancements:

  • The Get Document activity has a new Enable Max Documents checkbox to limit the number of documents retrieved per operation run. When enabled, you specify the limit in the Max documents field.
  • The List Transactions activity request structure has a new additionalFields node where you can specify a list of additional fields that you want included in the response. Refer to the list of supported additional fields. Note that existing activities will return an extra subelement warning (which can be ignored) until schemas are regenerated.

• MCP Client connector support for 3-legged OAuth
  In an MCP Client connection, the Authentication mechanism menu has a new Authorization Code Grant option (3-legged OAuth). For setup instructions, see MCP Client 3LO prerequisites to configure an application or integration record and Management Console app registration.

• OData connector support for OData V2
  An OData connection now has an OData Version menu to select V4 (default existing) or V2 (newly supported).

• Workday connector API version 45.1 support
  A Workday connection now has Workday Web Services (WWS) API version v45.1 available to select in its Version menu. For new connections, v45.1 is selected by default.

Changes

API gateway

• General changes
  The API gateway has general changes for maintenance and performance.

Fixes

Agent

• Windows private agent PostgreSQL fixes
  Two fixes have been made to improve stability of the PostgreSQL service on both 11.59 and 12.3 Windows private agents:

  • When upgrading, entering an incorrect PostgreSQL service account password at the installer prompt now shows a validation error and allows re-entry. Previously, this could cause the upgrade to fail without rolling back. If you have already encountered this issue, see recovery steps.
  • Fresh installations now correctly set a dependency on the PostgreSQL service for agent services, preventing agent services from starting before PostgreSQL is ready.

API Manager

• API creation permissions now reflect highest role access
  Permissions are now evaluated across all of a user's assigned roles, with the highest level of access applied. Previously, users assigned to multiple roles had their API Manager permissions restricted to the most restrictive role, preventing API creation even when another assigned role granted the necessary access.

Platform

• Schedules can now be deleted from the Management Console
  Schedules listed on the Management Console Projects page's Schedules tab can now be deleted even if the schedule was previously removed from the project in Studio or Design Studio. Previously, attempting to delete such schedules returned an unknown exception error.

Studio

• Global endpoints no longer fail after project deletion
  Deleting a project using a global endpoint no longer causes operations using the same global endpoint in other projects to fail until redeployed.

Studio SDK connectors

• Microsoft Teams Send Message activity UTF-8 encoding fixed
  The Microsoft Teams Send Message activity now properly encodes message content using UTF-8 when message content is passed through global variables.

Notices

Agent

• Retirement of 11.x private agent versioning
  This release includes the final 11.x private agent version (11.59) and the first available 12.x private agent version (12.3). Note the following regarding future releases:

  • Final 11.x version: 11.59 is the final planned 11.x private agent version. The next version following 11.59 will be 12.4, and all future enhancements, new features, and security updates will be delivered through 12.x private agents. While 11.x agents may receive rare critical fixes for production-impacting issues, no ongoing releases are planned.

  • Recommendation: We strongly recommend upgrading to 12.x private agents, starting with 12.3, as soon as possible to benefit from the latest performance, security, and feature improvements.

  • Upgrade path: You can upgrade directly from 11.x to 12.3 (or later 12.x versions) using our documented upgrade instructions: Windows, Linux, or Docker.

Agent and Design Studio

• End of life for version 11.41
  As of April 4, 2026, these product versions have reached end of life and are no longer supported:

  • Private agent version 11.41
  • Design Studio version 11.41

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

Harmony platform

• Action required: Upcoming sunset of legacy SSO redirection URLs
  Jitterbit is retiring legacy redirection URLs for Harmony single sign-on (SSO) in the upcoming 12.4 release. Since our June 2024 (11.28) announcement that SSO URLs had changed, new and updated SSO configurations require the new URLs. However, your organization may still be using legacy URLs if you configured SSO prior to June 2024 and its configuration has not yet been updated.

  Organization administrators must reconfigure their existing SSO configuration to use the new URLs, or user logins to Harmony will begin to fail on the following dates:

  	12.4
  APAC	April 28, 2026 (12 AM AEST)
  EMEA	April 28, 2026 (9 PM CEST)
  NA	April 29, 2026 (12 PM PDT)

  How to check if you need to take action

  Log in to the Harmony portal, navigate to Management Console > Organizations, and select your organization. In the User Management tab under the Enable SSO toggle, click Configure SSO.

  Your organization requires reconfiguration if any of these fields contain the string jitterbit-cloud-mgmt-console:

  • OAuth 2.0: The Client ID or Client Secret fields.
  • SAML 2.0: The Identity Provider Metadata or Service Provider Metadata fields.

  Required action

  If your organization is using legacy redirect URLs, an organization administrator must reconfigure them:

  1. Under the Enable SSO toggle, change the selection to None to remove the existing SSO configuration using the legacy redirect URLs.

  2. Recreate the SSO configuration using the latest redirect URLs following the documentation. This must be done in both Harmony and your identity provider:

     1. Under the Enable SSO toggle, select the authentication type: OAuth 2.0 or SAML 2.0. Then click Configure SSO.

     2. Update the redirect / ACS URLs in your identity provider.

  3. Test authentication to confirm successful login.

  For assistance, contact Jitterbit support.

Plugins

• Action required: Plugin updates for 12.x private agents
  Performance and security enhancements for 12.x private agents are incompatible with the following plugins. New, compatible versions of these plugins are already available:

  Plugin name	Incompatible versions	Required version
  Jitterbit Multipart Pipeline Plugin (deprecated)	1.0.9.0 1.0.8.0	1.0.10.0
  Jitterbit AWS S3 Create (deprecated)	1.0.1.0 1.0.0.0	1.0.2.0

  Private agent impact

  Before you upgrade to 12.x private agents, you must complete the required user action, or operations will begin failing at the time of upgrade. The new plugin versions are backward-compatible with 11.x agents, so you can update the plugins at any time.

  Required user action

  You must replace any existing uses of the incompatible plugin versions with the new, required versions:

  1. (Private agents only) Associate the new plugin version to the private agent group in the Management Console Customizations > Plugins page.
  2. Unassign the incompatible plugin from the activity in your Studio or Design Studio projects.
  3. Assign the new, compatible version.
  4. Test and deploy the operation.

Studio SDK connectors

• 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.