12.6 Harmony release notes

12.6 Harmony release

The 12.6 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.62 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

• Document Compliance Agent
  The Document Compliance Agent, accessed from the Marketplace AI Agent category, automatically extracts text from PDFs using Amazon Textract OCR and applies Amazon Bedrock AI analysis to detect and remove personally identifiable information (PII), helping organizations meet data privacy requirements without manual document review. To add it to your license, contact us.

• Security Alert Agent
  The Security Alert Agent, accessed from the Marketplace AI Agent category, reduces redundant security alerts and accelerates threat response by automatically receiving, analyzing, and routing security events from Wazuh and Tenable via Slack and email notifications. To add it to your license, contact us.

Studio SDK connectors

• Anthropic Claude (Beta) connector
  The Anthropic Claude (Beta) connector can be used with cloud or private agents to send prompts to and register tools with Claude models hosted by Anthropic directly or through Amazon Bedrock. For beta access and to provide feedback, contact the Jitterbit Product Team.

• ZoomInfo (Beta) connector
  The ZoomInfo (Beta) connector can be used with cloud or private agents to enrich, search, and look up records from ZoomInfo. For beta access and to provide feedback, contact the Jitterbit Product Team.

Enhancements

Agent

• Configurable consecutive CPU check threshold for private agent capability
  A new CpuConsecutiveFailureThreshold setting in the [AgentCapability] section of jitterbit.conf lets you require a specified number of consecutive CPU threshold violations before the agent transitions from Capable to Incapable. The default value of 1 preserves existing behavior; the default will increase in a future release. Recovery to Capable remains immediate once CPU drops below the IncapableCpuUsage value.

API Manager

• APIM AI Assistant option to copy the conversation
  The APIM AI Assistant now includes a Copy Chat icon in the assistant options. Clicking it copies the full conversation, including all user prompts and assistant responses. Starting a new chat resets the scope so that only the new chat's content is copied.

EDI

• Customer-specific AS2 Receiver URL
  The AS2 connection configuration now includes a read-only Receiver URL field that displays the partner-specific receiving URL for the connection. The URL is generated from the account's region and the configured AS2 Company ID and AS2 Partner ID values, and can be copied using the adjacent Copy receiver URL icon to share with the trading partner.

• EDI AI Assistant enhancements
  The EDI AI Assistant supports the following new capabilities:

  • Advanced search: Search transactions by all standard and advanced fields, request specific result columns, and view paginated results in chat or refreshed in the UI.
  • Non-acknowledged documents: Search for outbound transactions missing expected acknowledgments, with optional filtering by partner, document type, date range, and custom fields.
  • Acknowledgment time: Calculate acknowledgment time statistics, such as averages, for outbound documents across a filtered result set.
  • Transaction actions: Archive, reprocess, or resend acknowledgments for transactions using the same advanced search filters.
  • PII guidance: Ask how to display PII data and the assistant directs you to Enable PII.

Management Console

• Role access assignment and deletion enhancements
  The User Management page has two new tabs in its Role Assignments drawer: Project Access and API Access, where you can assign and unassign Studio projects and APIs to a role individually or in bulk. When deleting a role that has project or API access assigned, a confirmation dialog now requires selecting an Unassign all project and API access checkbox before deletion can proceed.

Studio

• Labels filter on the Projects page
  The Projects page has a new Labels filter. Select one or more user-created labels to show only projects that have at least one of the selected labels assigned, or select No Labels to display only projects with no labels assigned.

Studio SDK connectors

• Google Gemini connector Vertex AI and RAG corpus support
  A Google Gemini connection has a new Platform menu where you can select AI Studio (default existing, authenticates using a Gemini API key) or Vertex AI (newly supported, authenticates using a Google Cloud service account). The Prompt activity also has a new Use RAG Corpus (Vertex AI) option that enables Retrieval-Augmented Generation (RAG) grounding by allowing you to select a RAG corpus and configure vector search settings. See the Gemini Enterprise Agent Platform prerequisites for Vertex AI setup requirements.

• MCP Client connector prompt and resource activities
  The MCP Client connector has four new beta activity types for working with MCP server resources and prompts. To provide beta feedback, contact the Jitterbit Product Team.

  • The List Prompts (Beta) activity retrieves all prompts available on the connected MCP server.
  • The Get Prompt (Beta) activity retrieves a specific prompt by name, either typed manually or selected from the discovered list, and returns its resolved messages along with any arguments.
  • The List Resources (Beta) activity combines static resources and URI template resources from the MCP server into a single response.
  • The Read Resource (Beta) activity retrieves the content of a chosen resource, supporting manual URI entry, selection from a static resource list, or selection of a URI template with automatic parameter substitution.

Changes

Agent

• PostgreSQL encryption defaults to SCRAM for fresh Linux agent installs
  Fresh installations of Linux private agents now use SCRAM-SHA-256 password encryption for the bundled PostgreSQL instance by default. Agents upgraded from a previous version retain their existing MD5 encryption. To switch an upgraded agent to SCRAM-SHA-256, see SCRAM on PostgreSQL.

API gateway

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

• Major version number increased to 12.x
  The versioning of the private API gateway has been increased from 11.x to 12.x. This is a change in version numbers only. Private API gateway 12.x is compatible with existing APIs. You can upgrade to 12.x directly from an 11.x private API gateway version following our upgrade instructions (Linux or Docker).

Fixes

Agent

• API-triggered operations no longer stay in Running status
  API-triggered operations no longer intermittently get stuck in an indefinite Running status until cancelled by the cleanup process.

• Agent sync during active deployments fixed
  Agents no longer load incomplete project data when a sync occurs during an active deployment. Previously, if an agent sync started before a deployment had finished, partial data could be loaded, causing operations to fail.

• Multibyte character fixes
  The following fixes related to multibyte characters resolve issues with operation failures, incomplete logs, failure to deploy, and incorrect output:

  • Project and component names that contain multibyte characters no longer cause operations using them to fail at runtime or produce incomplete logs.
  • Projects containing file formats that use multibyte characters as field delimiters can now be deployed successfully.
  • String comparisons using == in condition scripts now return correct results when the strings contain multibyte characters.
  • Transformations no longer fail or produce incorrect output when source data or schema node names contain multibyte characters, or when multibyte characters are hardcoded as values in a transformation.
  • String columns in ODBC-connected databases now correctly return multibyte characters in transformation output. To enable this fix, set jitterbit.scripting.db.multibyte.enable to true.
  • Multibyte characters in scripts are now preserved when restoring a Design Studio project from the Harmony cloud.
  • Email notifications now correctly transmit multibyte characters in the subject and body at operation runtime.
  • The Shopify connector no longer displays multibyte characters as ? symbols in data exchanged with Shopify.
  • API responses now correctly encode multibyte characters passed through a transformation or script. Previously, these characters were corrupted in the response. To ensure browsers render the characters correctly, set jitterbit.api.response.headers.content_type to text/html; charset=utf-8.

API Manager

• CSV download restored for charts on the Analytics page
  Charts on the redesigned Analytics page now include a Download as CSV icon to export chart data as a CSV file. This functionality was available in the legacy Analytics interface but was inadvertently removed in the new interface.

Design Studio

• Validation error fixed for older Salesforce projects using basic authentication
  Design Studio projects that use an older Salesforce API version (earlier than v65) and basic authentication no longer show a validation error on the Salesforce Org item. Previously, Design Studio 11.59 or later incorrectly flagged these projects as invalid even when the project had not been upgraded to Salesforce API version 65, which is the version that requires OAuth 2.0 authentication.

Management Console

• Runtime status filter now works as expected with execution tree view disabled
  The Runtime page now returns correct results when the Execution tree view toggle is enabled and a status filter is applied. Previously, status filters returned incomplete results and pagination was unavailable when the result set included failed child operations such as SOAP Fault entries.

Studio

• Database connector CLOB data type display fixed
  Database connector fields with the CLOB (Character Large Object) data type now display correctly in the transformation UI and are handled as string type. Previously, these fields appeared with an empty () data type label.

• Operation log message filter fixed
  The operation log Message filter now returns results correctly and supports the # character in the search term. Previously, including # in a message filter query returned HTTP 500 errors, and message searches returned no results even when matching logs existed.

Studio SDK connectors

• HTTP v2 POST activity redirect handling fixed
  The HTTP v2 POST activity now correctly follows server-initiated 3xx redirects. Previously, POST requests that received a redirect response would fail with an error instead of following the redirect.

• ServiceNow, Snowflake, Google BigQuery, and Amazon Redshift query filter fix
  The ServiceNow, Snowflake, Google BigQuery, and Amazon Redshift connectors now correctly wrap filter values in single quotes for string-type fields (string, char, varchar, nvarchar, text, date, time, datetime, timestamp, uuid, json, xml, and enum) when building query conditions. Previously, these values were not quoted, causing queries to fail or return no results.

• ShipStation Query activity fix for shipment response schema
  The ShipStation Query activity now generates the correct response schema when querying shipment objects (shipment_by_id and shipment_by_external_id) using the ShipStation API V2.

Notices

Agent

• Retirement of 11.x private agent versioning
  The 11.59 / 12.3 release included 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: The 11.x private agent version has reached the end of its planned development. 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 as soon as possible to benefit from the latest performance, security, and feature improvements.

  • Upgrade path: You can upgrade directly from 11.x to any 12.x version using our documented 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 in the upgrade instructions.

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

• End of life for version 11.44
  As of June 5, 2026, private agent version 11.44 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.

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