12.9 Harmony release notes

12.9 Harmony release

The 12.9 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.65 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

Marketplace

• App asset type
  Marketplace now offers apps, a fourth asset type alongside integration recipes, process templates, and AI agents, browsable by selecting the App type. An app is a low-code application built with Jitterbit App Builder, distributed as an .LP release package that you download from Marketplace and install into your own App Builder instance to configure and extend.

• Learning Apps
  Six Learning Apps are available at launch, each one an app you can install and explore to learn how an App Builder app is built:

  • AcuTrack: Track physical assets with mobile QR scanning, check-in and check-out, preventative maintenance scheduling, and location dashboards.
  • Form Flow: Build template-driven forms and collect responses through a guided wizard, with conditional field visibility and a review-and-approval workflow.
  • Jira Tracker: Track product lifecycle work across Product Management, UX, Engineering, and Documentation, with tabbed analytics dashboards.
  • Monitoring: Monitor scheduled jobs, notify user groups when a job fails, track resolutions, and run database maintenance.
  • Northwinds: A sample order-fulfillment app built on the classic Northwinds database, useful as a starting point and for learning App Builder.
  • Registration Portal: Provide self-service registration, login, and password recovery, with two-factor authentication and account lockout protection.

Management Console

• Console AI Assistant (Beta)
  The new Console AI Assistant lets you monitor, troubleshoot, and manage your Harmony platform by interacting with Management Console using natural language, instead of navigating between pages to find information or make a change. You can access it using the Jitterbit AI icon in the Harmony portal header on any Management Console page. To add it to your license, contact your Customer Success Manager (CSM).

Harmony portal

• Personal Studio defaults that apply across organizations
  You can now set personal, user-level defaults for common Studio settings instead of configuring them separately for every project or organization. These defaults are preset for new projects you create. Configure them in the new Studio tab of the Harmony portal's Account settings page.

  You can set defaults for the following:

  • View (Card view or List view) on the Projects page.
  • Design canvas operation auto-numbering.
  • Transformation view settings and panel states.
  • Icon view preferences in the project pane's Components tab.
  • Script editor tab size (2 to 8, defaults to 2) and AI-generated line completion preference. Both are new settings.
  • Whether the iterator reconfiguration warning dialog is suppressed. Unlike the settings above, this new Always suppress transformation iterator warnings toggle takes effect immediately across all of your existing projects too, not just new ones.

  A project's Edit project settings screen also has new Use my personal settings and Go to account settings controls, so you can apply your defaults to an existing project or jump straight to your Studio account settings.

Studio SDK connectors

• PDF Utilities (Beta) connector
  The PDF Utilities (Beta) connector can be used with cloud agents or private agent version 12.3 or later to generate PDF documents. It has no external API or outbound network calls. The connector's Convert Text to PDF and Convert HTML to PDF activities convert plain text or HTML content into a PDF document. To provide beta feedback, contact the Jitterbit Product Team.

• ServiceNow v2 (Beta) connector
  The ServiceNow v2 (Beta) connector is now available to all organizations. It can be used with cloud or private agents to query, create, update, or delete records in ServiceNow. To provide beta feedback, contact the Jitterbit Product Team.

Enhancements

Agent and Design Studio

• Platform-wide multibyte support
  Starting with agent version 12.9 and Design Studio 11.65, Portuguese, German, and Russian are now certified as supported languages for the Harmony platform. See Character encoding and multibyte support for details, including known exceptions.

• SHA512 cryptographic function
  A new SHA512 function is available for use in Studio and Design Studio scripts and transformations, complementing the existing SHA256 function. It applies the SHA-512 hash function to an input string and returns the hash as a string of 128 hexadecimal digits. String input is first converted to its UTF-8 byte representation, and non-string input is first converted to a string. This function requires agent version 12.9 or later; in Design Studio, it also requires version 11.65 or later.

Agent

• Internal database connection pooling defaults to on for Linux private agents
  On Linux private agents, UseInternalPooling in jitterbit.conf now defaults to true when the key is absent, enabling internal database connection pooling to optimize agent performance, matching the default already used on Windows private agents since 12.5. Previously, an absent key defaulted to false on Linux.

API gateway

• API key expiry and reminder email for security profiles
  An API key security profile can now be configured to expire, after which API requests using the key are rejected. Enable API key expiry and set an Expiry duration (days) (180 by default) to have the key expire that many days after it's generated or regenerated using the refresh icon. The read-only Expiry column shows the calculated expiration date, along with a status pill showing Expiring soon when the key is within 7 days of expiring. A reminder email is sent to your organization's administrators before the key expires. The cloud API gateway enforces key expiry automatically; a private API gateway requires version 12.9 or later.

• Masked credential and session headers in API logs
  Headers that carry credentials or session data, such as authorization, password, and x_api_key, now have their values replaced with [removed] wherever API request headers appear in logs, including the Call information section of the API Manager API Logs page, the Management Console Runtime page, Studio operation logs, and the raw request and response data added by Verbose logging or Enable debug mode until. For the complete list, see Masked headers. Masking is applied by the cloud API gateway and by private API gateway version 12.9 or later; on earlier private API gateway versions, these header values are displayed in full.

• Configurable maximum subdomain levels for private API gateway custom FQDNs
  The private API gateway configuration file gatewayconfig.yaml supports a new MaxDomainParts key that lets you increase the maximum number of subdomain levels supported in a custom fully qualified domain name (FQDN), raising the default from 5 to 10. Add this key to gatewayconfig.yaml if your custom FQDN requires more than 10 levels, for example setting it to 15. For Docker-based gateways, add the key first, then set the equivalent MAX_DOMAIN_PARTS environment variable to the same value.

API Manager

• Customization preservation and conflict resolution for Portal Manager
  Clicking Regenerate Docs on the Portal Manager page no longer overwrites your OpenAPI editor customizations. It now preserves and reapplies them automatically wherever possible, and prompts you to resolve any conflicts before publishing. This does not apply to regenerating an individual API's documentation from the Documentation tab on the APIs page, which still overwrites customizations.

• Ask AI on the Analytics page
  The Analytics page has a new Ask AI button that opens the APIM AI Assistant, where you can use natural language prompts to query and interpret API performance metrics such as response time, status codes, errors, and rate-limit utilization.

EDI

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

  • Partner search: Search for trading partners by custom field description.
  • Custom fields: Retrieve, add, update, and delete a partner's custom fields.
  • Hourly transaction counts: Calculate transaction volume by hour for a date or a date range of up to 7 days, optionally filtered by document type (general type or specific code) or partner name.

• AS2 certificate expiration notifications
  The expiry dates of the certificates used by an AS2 connection are now checked when a document is sent or received. If a certificate is set to expire within the next 30 days, certificate expiration notifications appear: an error message is logged once per day on the Messaging page, and a banner notification is displayed once per day on EDI pages.

Management Console

• EDI audit log visibility in the Management Console
  Jitterbit EDI Audit category log messages, covering configuration changes, data access, reprocessing and resend attempts, and system login/logout activity, are now also visible on the Management Console Audit Logging page alongside Management Console, API Manager, and Studio activity.

Studio SDK connectors

• Apache Kafka connector support for SCRAM-SHA-512 authentication
  An Apache Kafka connection's Auth Protocol setting now includes a SASL SSL (SCRAM-SHA-512) option, available when PLAIN is selected as the Auth Mechanism. This lets you connect to a Kafka broker that requires SCRAM-SHA-512 authentication, such as an Amazon MSK cluster configured to allow only SHA-512.

• Smartsheet Import Sheet activity Workspace ID option
  The Smartsheet Import Sheet activity has a new Choose option setting for specifying the workspace to import the sheet into, either by entering a Workspace ID directly or by selecting from a list of available workspaces. A workspace can also be provided in the request transformation. Providing one imports the sheet into that workspace using Smartsheet's newer import endpoint; omitting it preserves existing behavior, importing into your Smartsheet home Sheets folder through the previous endpoint.

Fixes

Agent

• Testing a script that uses a database function no longer fails with No suitable driver found
  Testing a script that calls a database function such as DBLookup no longer fails with a No suitable driver found error when the Database endpoint's Login, Password, or Connection String is set from project or global variables assigned within the tested script. This applies to script testing in both Studio and Design Studio.

• Metrics service now uses the correct PgBouncer port on fresh Windows private agent installs
  On a fresh install of a Windows private agent, the metrics service now uses the configured PgBouncer port. Previously, it used 6432, PgBouncer's default port before 11.58, rather than the 6434 default used by fresh installs since 11.58, so metrics collection was incomplete. Agents upgraded to this version keep their existing PgBouncer port.

• PgBouncer now installs correctly on non-root Linux private agent installations
  Previously, installing a private agent as a non-root user on Linux did not provision PgBouncer, so the connection pooler never started and its status showed as unhealthy in Agent Metrics. New non-root Linux installations now install and start PgBouncer correctly. Upgrading an existing non-root Linux agent does not provision PgBouncer retroactively; the agent must be freshly installed.

• Salesforce bulk operations no longer fail with an internal database error
  A Studio Salesforce, Salesforce Service Cloud, or ServiceMax bulk operation configured with Studio Salesforce bulk operation options (Write success records to, Write failure records to, Send success records to, or Send failure records to), or a Design Studio Salesforce Bulk Process wizard operation configured with the equivalent operation options, no longer fails partway through with an internal database error. Previously, recording a bulk activity's success or failure file status could generate an invalid SQL statement, causing the operation to fail even after some records had already been processed successfully.

• File Share connector now supports multiple comma-separated paths
  Multiple comma-separated paths on the same server are now supported in the Path field of a Studio File Share connection, and in the Path(s) field of a Design Studio File Share source or File Share target. A source reads and aggregates the files found in every configured path, and a target writes to every configured path. Previously, a comma-separated value was treated as a single, invalid path and the connection failed.

• HTTP activities again include the target response body in operation error logs
  When a legacy HTTP connector POST or PUT activity fails in Studio, or the equivalent HTTP Target in Design Studio, the operation error log again includes the response body returned by the target endpoint. Previously, the response body was dropped from the error log for failed requests.

• Design Studio Salesforce Wave Analytics Dataset target now supports OAuth 2.0 Client Credentials authentication
  A Design Studio project's Salesforce Wave Analytics Dataset target can now generate and upload a dataset using a Salesforce Org endpoint configured with Select OAuth 2.0 Client Credentials. Previously, the operation failed with a SF Analytics Dataset Upload Error: username is required error, even when the endpoint's OAuth 2.0 connection test succeeded, because dataset generation and upload still required a username, password, and security token.

• DBLookup and DBExecute no longer fail with a Base64 decoding error on JDBC database connections
  DBLookup and DBExecute calls to a PostgreSQL or SQL Server database using a JDBC driver no longer fail with a Base64 decoding error when the returned value resembles Base64-encoded data, such as a JWT or other access token.

• Unmap no longer returns null when preceded by RunScript in the same mapping expression
  The Unmap function now correctly unmaps a target field when a RunScript call precedes it in the same mapping expression. Previously, in this case, Unmap returned a null value instead of unmapping the field.

• ConvertTimeZone now preserves millisecond precision
  The ConvertTimeZone function now preserves millisecond precision in the returned value. Previously, milliseconds were dropped regardless of the input value.

API Manager

• Proxy API request header values now accept periods and other punctuation
  On the Request headers tab of a proxy API, a header's Value now accepts periods and other punctuation, and its maximum length is raised to 8192 characters. Previously, a value could contain only letters, numbers, hyphens, and underscores, which blocked values such as JSON Web Tokens (JWTs) that require periods as part of their format.

EDI

• Transaction details now open reliably for very large EDI documents
  Opening the Document information tab for a very large EDI document on the Transactions page now displays This EDI file is too large to view in HTML. Please use one of the RAW views to see its content. in place of the rendered document, so the tab loads without attempting to render the full EDIXML content as HTML. You can still access the document's full content from a Raw link in the Views pane.

Studio and Management Console

• Operations in Submitted or Received status can now be canceled
  The Cancel operation action is now enabled for operations in Submitted or Received status on the Management Console Runtime page, in the Studio operation log table, and next to an operation's runtime status on the design canvas. Previously, the action was disabled for these two statuses, so an operation that was queued but had not yet been picked up by an agent required Jitterbit support to clear it.

Studio

• Transformation mappings imported with duplicate nodes no longer cause operations to fail
  Importing a transformation mapping file that duplicates a target node now applies the duplication to the schema definition used when the operation runs. Previously, the duplication was applied only to the target schema shown in the transformation designer, so the mapping appeared correct at design time while the operation failed at runtime with Failed to expand the target tree for the path: <path to node>. The node: <node name> cannot be created. To correct a transformation whose mapping was imported before this fix, use Remove all mappings beneath this node on the root node, then import the mapping file again.

• Deploying a project no longer deletes WSDL files that are still in use
  Deploying a project no longer deletes WSDL files that are still in use. Previously, a project could deploy successfully and then fail on a later deployment with an error similar to No WSDL with locator, most often after the project was migrated to another environment. This affected any component that an existing WSDL file was uploaded to: SOAP connections and API SOAP Request and SOAP Response activities. To recover a project that is already affected, see SOAP deployment error: "No WSDL with locator".

• Workday activity responses now map correctly when the response schema is used directly or mirrored
  A transformation that uses a Workday activity's response schema directly, or a mirrored copy of it, no longer fails with Failed to find structure node name matching the data element: <node name>. Previously, a node in the Workday response was not matched to the corresponding node in the schema, so the transformation failed even though the same response mapped successfully to a flat target schema. If an existing transformation continues to fail, reconfigure the activity to regenerate its schema, then refresh the schema in the transformation.

Studio SDK connectors

• OpenAI and Azure OpenAI connector fixes
  The OpenAI and Azure OpenAI connectors have the following fixes:

  • Activities with a Temperature or Top Probability setting now save a decimal value entered in either field. Previously, a decimal value such as 0.2 or 1.35 was rounded to the nearest integer (0, 1, or 2) when the activity was saved, overwriting the entered value.
  • The OpenAI and Azure OpenAI Prompt activities now format multiple concurrent tool calls correctly, sending the assistant message once followed by each tool response in order. Previously, the assistant message was repeated before every tool response, with each response's content sent as an array instead of a flat string.

• RabbitMQ Consume activity now continues consuming messages when Auto Acknowledge is enabled
  The RabbitMQ Consume activity continues consuming messages from the queue after the first message when Auto Acknowledge is enabled. Previously, the listener stopped consuming further messages after successfully processing the first one, and only a full redeployment of the operation temporarily restored consumption.

• Snowflake Merge activity and global endpoint fixes
  The Snowflake connector includes the following fixes:

  • Merge activity special characters: The Snowflake Merge activity now quotes column identifiers in its generated SQL when Use quote for Snowflake identifiers is enabled on the connection, matching the Insert activity. Previously, a target column name with a special character such as a hyphen could cause a SQL compilation error even with this setting enabled.
  • Global endpoint configuration changes: Editing an existing global endpoint now correctly saves changes to the Account, Database name, Host name, Schema name, and User name fields. Previously, these edits were discarded, requiring you to remove and re-add the endpoint to apply a change.

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.

Agent, API gateway, and Design Studio

• End of life for version 11.47
  As of August 7, 2026, these product versions have reached end of life and are no longer supported:

  • Private agent version 11.47
  • Private API gateway version 11.47
  • Design Studio version 11.47

  We recommend that users of these versions 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.