12.8 Harmony release notes

12.8 Harmony release

The 12.8 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.64 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 (Azure)
  The Document Compliance Agent (Azure), accessed from the Marketplace AI Agent category, automatically extracts text from PDFs using Azure Document Intelligence optical character recognition (OCR) and applies Azure AI Foundry 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.

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

Studio SDK connectors

• ServiceNow v2 (Beta) connector
  The ServiceNow v2 (Beta) connector can be used with cloud or private agents to query, create, update, or delete records in ServiceNow. For beta access and to provide feedback, contact the Jitterbit Product Team.

Enhancements

Agent

• Private agent installer validation enhancements
  Installing a private agent version 12.8 or later now includes additional validation and guidance during the installation process:

  • System requirements prompt: The Windows and Linux installers now display a prompt with the agent system requirements during installation.
  • PostgreSQL password validation: On Windows, the installer now validates the PostgreSQL service account (jitterbitpostgres) password against the character restrictions at input time and prompts you to correct it before installation proceeds. Previously, an invalid password was not caught until after PostgreSQL had been installed, causing the installation to fail with Error 1722.

API Manager

• Multi-client credential support for 2-legged OAuth 2.0 security profiles
  An OAuth 2.0 security profile using 2-legged OAuth Flow (Microsoft Entra ID or Okta) can now store multiple client credential entries under Client credentials, each with its own Consumer Name, Client ID, Client Secret, and Status (Active or Inactive). This lets multiple distinct consumers authenticate to the same API using their own credentials, without requiring a separate security profile or API per consumer.

EDI

• EDI AI Assistant support for document type codes
  The EDI AI Assistant now supports filtering transactions by a specific document type code, such as 810 or INVOIC, in addition to a general document type such as Invoice or Order. You can refer to a subtype by its code alone (for example, 810) or qualified with its general type (for example, Invoice.810).

• Menus to build with AI or open UI configuration
  A new New menu on the Trading Partners page, a partner's Manage workflows tab, and a partner's Communication settings tab show options to Build with AI or open the UI configuration. In addition, the Transactions page advanced search builder has a new Search menu with a Search with AI option. The Build with AI option opens the EDI AI Assistant to create a trading partner, workflow, or connection using natural language prompts, and the Search with AI option opens it to search transactions.

• Messaging page redesign
  The Messaging page has a redesigned interface with the following new capabilities: filtering and a column for message severity level (High, Medium, Low, or Info); filtering by message category and subcategory; a Columns drawer for showing, hiding, and reordering columns; and a message details drawer for reviewing a message's log entries without losing your place in the list.

Harmony portal

• Account settings page redesign and security question reset
  The Account settings page (previously My Account) has a redesigned interface with sidebar navigation and separate forms for your profile and contact information. You can also now reset your security question and answer, which provide an additional way to verify your identity.

Management Console

• New alert type: SSO Status Changed
  The Alerts page has a new alert type that emails users with Admin role permission when single sign-on (SSO) is enabled or disabled for the organization. This alert is enabled by default for both new and existing organizations, so Admin users are notified automatically with no setup required, unless the alert is reconfigured or deleted. Enabling or disabling SSO is also now logged as an Update entry in audit logging.

Studio

• Compact validation indicator for transformation field scripts
  Script validation status for a target field script within a transformation now displays as a collapsed, single-line indicator instead of automatically expanding, matching the behavior of the full script editor and the script component. Long validation messages are truncated with an ellipsis, and you can click the indicator to view the full message in a floating overlay that doesn't push the script or surrounding fields out of view. Click outside the overlay, or use its close control, to collapse it back to the indicator.

Studio SDK connectors

• Amazon Bedrock connector short-term memory and knowledge base retrieval
  The Amazon Bedrock connector has the following enhancements:

  • Chat context across operations: An Amazon Bedrock 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.
  • Additional knowledge base retrieval sources: The Amazon Bedrock Prompt activity now supports knowledge bases that use Amazon S3 Vectors (a vector store) or Amazon Redshift (a structured data store) as retrieval sources, enabled with the new Use Knowledge Base checkbox.

• Anthropic Claude (Beta) connector
  The Anthropic Claude (Beta) connector is now available to all organizations. It 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. To provide beta feedback, contact the Jitterbit Product Team.

• EDI for Cloud v2 Send Document activity connection override
  The EDI for Cloud v2 Send Document activity has a new optional setting, Use Alternative Communication Method. When enabled, you can select a specific EDI connection from the available connections list to use for that operation, overriding the trading partner's connection assigned in the EDI Communication settings.

• OpenAI connector support for the Responses API and MCP server tools
  The OpenAI connector has three new activities built on OpenAI's Responses API:

  • The Prompt V2 activity creates a response for a prompt and can call tools registered by a preceding activity that uses the same chatId.
  • The Register Tools V2 activity adds tools to a chatbot assistant.
  • The Register MCP Server Tools activity registers a remote MCP server as a tool provider so its tools become available to a chained Prompt V2 activity, enabling models to dynamically discover and invoke tools from customer-managed MCP endpoints at runtime.

  These three activities also support chat context persistence across operations using a shared chatId: an OpenAI connection has a new Store chat context across operations (V2 activities only) setting for cloud agent groups, with dependent Chat context TTL, Maximum messages saved in context, and When chat context is not found settings. Private agents already retain chat context in memory and are unaffected by this setting. The existing Prompt and Register Tools activities are unaffected.

Changes

API gateway

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

API Manager

• API name display in the Analytics page APIs filter
  The APIs filter on the API Manager Analytics page now displays each API by its name only, and filtering by an API matches on the API name. Previously, the dropdown displayed the API name concatenated with its version number. Because filtering matches on the name, selecting an API can return results for multiple APIs that share the same name; use the separate Version and Environment filters to narrow the results.

Management Console

• Environment role access scoping for the Project access and API access tabs
  The Project access and API access tabs in the User Management Role Assignments drawer now list a project or API only when both the selected role and your own user account have at least Read environment role access to its environment. Previously, you could see projects and APIs listed here that you did not have environment role access to.

Studio SDK connectors

• Google Gemini connector RAG corpus setting moved; requires user action
  The Google Gemini Prompt activity's Use RAG Corpus (Vertex AI) option now displays the RAG corpus selection fields on the same step as the model and prompt settings, instead of on a separate step.

  Action required: Existing Prompt activities using RAG Corpus (Vertex AI) must be reconfigured

  Existing operations using Prompt activities configured with Use RAG Corpus (Vertex AI) enabled before this change will fail until you open the activity and reconfigure the RAG corpus selection. Prompt activities without this option enabled are not affected.

Fixes

Agent

• New Jitterbit variable to preserve source XML namespace prefixes
  The new Jitterbit variable jitterbit.target.xml.preserve.namespace.prefix can be set to true upstream of a transformation with XML output to preserve the namespace prefixes defined in the source XML. By default (false), transformations continue to apply generic namespace prefixes (ns, ns2, and so on), so existing behavior is unchanged unless you set this variable. This is useful when a target endpoint requires the original namespace prefixes to be retained.

• Date and time functions now preserve midnight values
  The ConvertTimeZone, Date, and GeneralDate functions now treat midnight (00:00:00) as a valid time value and preserve it in the returned value, whether the input is a raw datetime string or produced by Date or GeneralDate. Previously, a converted or parsed value of exactly midnight could be truncated to a date-only string, while any other time was preserved correctly. The CVTDate function was not affected.

• Improved agent stability during operation processing
  Agents are more stable when running transformations and processing operations under load. This resolves crashes that could occur during transformations and data format conversions, when long-running operations reach their timeout, and when processing high volumes of operations concurrently.

Agent and Design Studio

• Multibyte character fixes
  The following fixes resolve issues with operation failures, incorrect output, incorrectly displayed characters, and inaccessible files.

  These fixes apply when using agent version 12.8 or later:

  • Operations no longer fail with a UTF-8 Invalid byte error when the source data or a source file's name contains multibyte characters. For example, a JSON source file with multibyte content now loads correctly in a transformation, and a Salesforce operation with a multibyte character in the source file name no longer returns a SOAP fault.
  • NetSuite operations no longer replace multibyte characters in returned field names with ?, which previously caused transformations to fail.
  • The File Share and FTP connectors can now read files whose names contain multibyte characters. Previously, operations could fail when a filename contained multibyte characters.

  Note

  Writing a file with a multibyte filename over SFTP can still fail if the SFTP server does not support renaming files whose names contain multibyte characters. See FTP connector troubleshooting for a workaround.

  These fixes require both agent version 12.8 or later and Design Studio 11.64 or later:

  • Oracle EBS object names that contain multibyte characters are now displayed correctly in the object selection wizard.
  • Multibyte characters are no longer corrupted when a Design Studio project is downloaded or restored from the Harmony cloud, including in email message subjects and bodies.

  Important

  A transformation created before this release that uses multibyte characters in field names may show invalid mappings or process those fields incorrectly. Recreate the affected transformation (or remap the fields) to pick up these fixes.

Management Console

• Runtime search now supports HTTP status codes for API log entries
  The Runtime page status search key now accepts an HTTP status code (100–599) to search Custom API, Proxy API, and OData API log entries, in addition to an operation status name for Operation log entries. Previously, searching with an HTTP status code returned an error and no API log entries.

Studio

• Transformation now saves multiple open mapping scripts without a conflict error
  The transformation editor no longer shows a false save conflict when you have multiple mapping scripts open and edited at the same time. Previously, editing script content or field values across several open scripts could intermittently trigger a save conflict message; resolving it discarded your unsaved changes and closed any open mapping scripts.

Studio SDK connectors

• Refreshing an existing activity's schema no longer fails with DTDPARSER_ERR_UNKNOWN_FILE_EXTENSION
  Refreshing the schema of a previously configured activity, such as for the JWT or Stripe connectors, no longer fails with a DTDPARSER_ERR_UNKNOWN_FILE_EXTENSION error and a blank response schema. Previously, this could occur on an activity created before a change in how these connectors report their schema type.

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.46
  As of July 17, 2026, private agent version 11.46 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 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.