12.12 Harmony release notes

12.12 Harmony release

The 12.12 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.68 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

• Sales Quote Agent
  The Sales Quote Agent, accessed from the Marketplace AI Agent category, orchestrates the end-to-end quote creation process in Salesforce through a conversational Slack interface, applying uplift percentages, proration, and multi-year renewal logic to generate quotes and quote PDFs. To add it to your license, contact us.

MCP

• Jitterbit MCP (Beta)
  The new Jitterbit MCP application lets you expose your Harmony integrations and APIs as Model Context Protocol (MCP) tools, resources, and prompts that AI assistants and agents can discover and use.

  MCP servers are governed centrally: you control authentication, access, and rate limits, and the credentials used to reach the underlying integrations and APIs are never exposed to MCP clients. You can run MCP servers on Jitterbit's cloud, or on a private MCP runtime and MCP gateway that you deploy.

  To open Jitterbit MCP, click the MCP Servers tile in the Harmony portal, or use the Harmony portal menu to select MCP. Jitterbit MCP includes these pages:

  • Servers: Create, configure, test, and publish MCP servers and their tools, resources, and prompts.
  • Logs: Trace MCP requests and their related API and operation executions to troubleshoot failures.
  • Analytics: Monitor request volume, success and failure rates, and usage by server, tool, resource, and prompt.
  • Service Tokens: Create and manage the service tokens that private MCP runtimes and MCP gateways use to authenticate.

  To connect a Studio operation to a Jitterbit MCP server, see Connect to a Jitterbit MCP server using the MCP Client connector. To request beta access or provide feedback, contact the Jitterbit Product Team.

Enhancements

Agent

• Security enhancements
  The version of ActiveMQ bundled with the agent and used by the Design Studio JMS connector has been upgraded.

API Manager

• Custom authentication type for security profiles
  A security profile now supports a Custom authentication type that validates an HMAC-SHA256 or HMAC-SHA512 signature included in a request header you specify. Configure the signing Algorithm, Signature header name, and Shared secret, along with the Unauthorized status code and Unauthorized response body returned when validation fails.

Connectors

• Anthropic Claude connector short-term memory
  An Anthropic Claude connection has a new Store chat context across operations setting that enables short-term memory for cloud agent groups, retaining chat context beyond a single operation using a shared chatId. When enabled, use the new Chat context TTL, Maximum messages saved in context, and When chat context is not found settings to configure retention and fallback behavior. Private agents already retain chat context in memory for operations in the same chain and are unaffected by this setting.

• Google Gemini connector short-term memory
  A Google Gemini connection has a new Store chat context across operations setting that enables short-term memory for cloud agent groups, retaining chat context beyond a single operation using a shared chatId. When enabled, use the new Chat context TTL, Maximum messages saved in context, and When chat context is not found settings to configure retention and fallback behavior. Private agents already retain chat context in memory for operations in the same chain and are unaffected by this setting.

• Salesforce Einstein Analytics connector support for OAuth 2.0 Client Credentials and JWT Bearer flows
  The Salesforce Einstein Analytics connection has a new Authentication field with three options: Username-Password (default, existing), Client Credentials (newly supported), and JWT Bearer (newly supported).

  • Client Credentials requires a Salesforce external client app, or an existing connected app, configured for the OAuth 2.0 client credentials flow. See 2-legged OAuth 2.0 prerequisites for setup instructions.
  • JWT Bearer requires a Salesforce connected app configured with a digital certificate. See Salesforce's OAuth 2.0 JWT Bearer Flow for Server-to-Server Integration documentation.

• Salesforce Events connector support for OAuth 2.0 Client Credentials and JWT Bearer flows
  The Salesforce Events connection has a new Authentication field with three options: Username-Password (default, existing), Client Credentials (newly supported), and JWT Bearer (newly supported).

  • Client Credentials requires a Salesforce external client app, or an existing connected app, configured for the OAuth 2.0 client credentials flow. See 2-legged OAuth 2.0 prerequisites for setup instructions.
  • JWT Bearer requires a Salesforce connected app configured with a digital certificate. See Salesforce's OAuth 2.0 JWT Bearer Flow for Server-to-Server Integration documentation.

Management Console

• Log Type search key on the Runtime page
  The Management Console Runtime page has a new logType search key. Use = or != to filter log entries by log type: Operation, Custom API, Proxy API, or OData API.

• Management AI Assistant support for Cloud Datastore, endpoint usage, and access tokens
  The Management AI Assistant (Beta) includes the following updates:

  • Cloud Datastore: Can now list, search, create, edit, and delete status storages and key storages.
  • Endpoints Usage: Can now list, search, and view details for endpoints.
  • Access Tokens: Can now list, search, create, edit, activate, deactivate, and delete access tokens.

• MCP usage on the Dashboard page
  The Licensed vs Actual Use tile on the Management Console Dashboard page now shows your licensed and actual usage of MCP servers, MCP tools, and MCP monthly requests. The Management AI Assistant can also report these counts.

Studio

• Deploy details in project history
  Deploy events in the project history now identify what was deployed. When a single operation is deployed, the entry shows an operation icon and the operation's name. When an entire project is deployed, the entry shows a project icon and the project's name. When configurable deploy is used to deploy multiple operations, the parent entry can be expanded to view each deployed operation individually.

• Source environment display for selective transfer
  The selective transfer feature's Select target environment and tag step now shows a Source environment field with the name of the environment the project was originally transferred from, or No source environment if the project has never been transferred. This environment remains excluded from the Target environment menu, since a project can't be transferred back to the environment it was promoted from.

Changes

Management Console

• Console AI Assistant renamed to Management AI Assistant
  The Console AI Assistant (Beta) is now named the Management AI Assistant (Beta). It lets you monitor, troubleshoot, and manage your Harmony organization by interacting with Management Console using natural language, instead of navigating between pages to find information or make a change.

Fixes

Agent

• JSONStringify and JSONParser now handle numeric, Boolean, and null values correctly
  The JSONStringify and JSONParser functions include these fixes:

  • Converting a dictionary that contains a numeric field, such as one created by JSONParser from a JSON string with number values, no longer fails with the error Unknown DataElement type seen.
  • Decimal values are no longer truncated to 6 significant digits.
  • Boolean values are now returned as true and false instead of 1 and 0.
  • JSONParser now preserves object fields and array elements with a null value instead of omitting them.

• Non-numeric per-operation override values for invocation limits now fall back to the configured default
  Setting either of the following Jitterbit variables to a non-numeric value now correctly falls back to the corresponding jitterbit.conf default, rather than disabling the limit entirely:

  • jitterbit.operation.max_sync_runop_calls_in_loop: Falls back to MaxSynchronousRunOperationCallsInLoop (50 by default), which caps synchronous calls within a While loop.
  • jitterbit.operation.max_async_chain_length: Falls back to MaxAsyncOperationChainLength (50 by default), which caps the length of an asynchronous operation chain.

  Both settings are configured in the jitterbit.conf file's [OperationEngine] section. Previously, a non-numeric value disabled the respective limit entirely, allowing unlimited invocation.

• GetLastError now identifies a synchronous RunOperation loop-limit trip by operation name
  When a While loop's limit on synchronous RunOperation calls is reached, GetLastError and the operation log now identify the child operation that triggered the limit by its operation name, falling back to its GUID if the name can't be resolved. Previously, GetLastError didn't return this identifying information, and the operation log identified the operation only by its GUID.

API Manager

• Security profile Basic authentication username now validated at save time
  The User name field for a security profile using Basic authentication is now validated when you save the security profile, blocking disallowed characters that previously caused an API request to fail later with an INVALID_TRIGGER_USER error. A security profile saved before this release isn't revalidated, so it can still contain a disallowed character and fail at runtime the same way.

Connectors

• Cloud Datastore connector now sends request bodies using the correct character encoding
  The Cloud Datastore connector's Insert Items, Update Items, and Delete Items activities now send the request body using UTF-8 encoding. Previously, these activities could send the request body using an incorrect charset, causing an error when the data contained multibyte characters.

• HTTP v2 DELETE activity now sends the request body
  The HTTP v2 connector's DELETE activity now includes the configured request body in the outbound request. Previously, the activity did not attach the request body when sending a DELETE request, so the target endpoint received an empty payload and could reject the request.

• Microsoft Excel v2 connector now loads correctly on 12.x Linux private agents
  The Microsoft Excel v2 connector now loads correctly on 12.x Linux private agents. Previously, testing a connection or running an operation using this connector on a 12.x Linux private agent returned an error indicating the connector was not found on the agent. To apply this fix, click Test on the connection in Studio to download the latest connector version, or use the Management Console Agents page's Action > Update connectors to force the update across the agent group.

• OData Query activity no longer includes a $skip parameter when Skip is left empty
  The OData Query activity's request URI no longer includes a $skip parameter when the Skip field is left empty. Previously, leaving Skip empty caused the request to include $skip=0, rather than omitting the parameter entirely, which could cause the operation to fail against an OData endpoint that rejects an unrecognized $skip parameter, such as Microsoft Dynamics 365 CRM.

• OpenAI Create Image activity response schema now includes generation_id
  The response schema for the OpenAI Create Image activity now includes the generation_id field returned by the OpenAI API. Previously, this missing field caused successful operations to report a Success with Warning status instead of Success with Info. To apply this fix to an existing activity, regenerate its schemas.

• Pinecone Query Vectors and Fetch Vectors activity response schemas now include egressBytes
  The response schemas for the Pinecone Query Vectors and Fetch Vectors activities now include the egressBytes field returned within the usage object by the Pinecone API. Previously, this missing field caused successful operations to report a Success with Warning status instead of Success with Info. To apply this fix to an existing activity, regenerate its schemas.

• Stripe connector Checkout Session creation no longer fails with an internal error
  The Stripe Create activity's Checkout object > Sessions sub-object no longer fails with an internal error before the request reaches Stripe. Previously, creating a session could fail with an error similar to The Exception is: "null", even when all required fields (such as mode, currency, success_url, and customer) were provided correctly. To apply this fix to an existing activity, you must regenerate its schemas.

Harmony portal

• AI Assistant now loads by default based on the app you're using
  Jitterbit AI in the Harmony portal header now loads the APIM AI Assistant by default in API Manager and Studio, the Management AI Assistant in Management Console, or the EDI AI Assistant in Jitterbit EDI, for organizations with access to that assistant. Previously, AskJB AI always loaded by default, requiring you to manually switch bot types.

Studio

• Operations no longer revert to Undeployed after switching between local and global endpoints
  Deploying an operation after changing the assigned endpoint for one of its activities between a local endpoint and a global endpoint, or vice versa, now sets and retains the correct deploy status. Previously, the operation could show as successfully deployed immediately after deploying, but revert to showing the Undeployed status after the project was reloaded, even though no further changes had been made.

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
    Connectors built by a third party with the Connector SDK 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.

Agent and API gateway

• End of life for version 11.50
  As of October 9, 2026, these product versions have reached end of life and are no longer supported:

  • Private agent version 11.50
  • Private API gateway version 11.50

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

Connectors

• Action required: Deprecation of OpenAI Prompt and Register Tools activities
  The OpenAI Prompt and Register Tools activities are now deprecated and no longer supported, and will be permanently removed in an upcoming release. Both were replaced in the 12.8 release by the redesigned Prompt V2 and Register Tools V2 activities, whose use of OpenAI's Responses API makes it possible to persist chat context and call registered tools on cloud agent groups, not just private agents.

  Important

  If you are using the Prompt (Deprecated) or Register Tools (Deprecated) activity in any operations, you must review your operation design and replace it with the Prompt V2 or Register Tools V2 activity as soon as possible, as the deprecated activities are no longer supported and will be removed in the future.

• 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 returns the individual fields you define in the Management Console Cloud Datastore page 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. The deprecated activity is no longer supported and will be removed in a future release.