11.41 Harmony release notes
11.41 Harmony release
The 11.41 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.
11.41 Sandbox Cloud Agent Group (SCAG) SDK connectors on 11.41 SCAG 11.41 Design Studio Cloud platform and applications | 11.41 Production Cloud Agent Group (PCAG) SDK connectors on private agents and 11.41 PCAG 11.41 Windows and Linux private agents | 11.41 Docker private agent | |
---|---|---|---|
APAC | March 25, 2025 (1 - 5 AM AEDT) | April 1, 2025 (3 - 9 PM AEDT) | April 4, 2025 (9 PM AEDT) |
EMEA | March 25-26, 2025 (8 PM - 12 AM CET) | April 2, 2025 (6 AM - 12PM CEST) | April 4, 2025 (12 PM CEST) |
NA | March 26, 2025 (12 - 4 PM PDT) | April 3-4, 2025 (9 PM - 3 AM PDT) | April 4, 2025 (3 AM PDT) |
Release notes are provided separately for App Builder 4.41.0, Wevo iPaaS 11.41, Data Loader 11.41, and Vinyl 3.3.36638, which were also released during this timeframe.
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 (except for the Docker private agent and Docker private API gateway, which are available at Docker Hub). The end-of-life date for these components is one year after the release date.
New features
Integration Studio
- Importing of individual project components
A new Import option in an open project's actions menu is now available to all organizations and is no longer a beta. The new option provides the ability to select individual components of an exported source project to import into the current project.
Integration Studio SDK connectors
- SugarCRM v2 (Beta) connector
The SugarCRM 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 SugarCRM. To provide feedback, contact the Jitterbit Product Team.
Enhancements
Agent, Integration Studio, and Design Studio
-
NetSuite WSDL version 2025.1 support
Jitterbit has verified support for NetSuite WSDL version 2025.1 with the Integration Studio NetSuite connector and the Design Studio NetSuite connector. An agent or Design Studio upgrade is not required. In addition, the 2025.1 WSDL is now the default WSDL download URL for a new Integration Studio NetSuite connection. -
Salesforce API version 63 support
Salesforce API version 63 is now supported for these connectors:-
The Integration Studio Salesforce, Salesforce Service Cloud, and ServiceMax connectors automatically use this API version with 11.41 or later agents.
-
The Design Studio Salesforce connector supports this API version with the use of both 11.41 or later agents and an 11.41 or later version of Design Studio. When both these version requirements are met, an API upgrade dialog is shown when opening existing projects using this connector.
-
Integration Studio
-
Custom group for components that are selectively imported
Using the Import option to import selected components into a project now automatically creates a custom component group for the imported components. -
Script-mode prompt for mapping occurrence mismatch
While in script mode and mapping from a source loop node to a single-instance target node, a dialog now prompts you to use change the mapping to use the first instance for each source, which automatically edits the mapping to add a#1
in the source object's reference path. This dialog was already present in mapping mode. -
Improvements to the new UI
When Try the new UI is enabled, the following UI improvements are available:-
The visible indication of operations with undeployed changes has been made to be more obvious.
-
The icons used as operation components are now more visually distinct.
-
Integration Studio SDK connectors
-
Amazon S3 Get Object activity tagging metadata setting
An Amazon S3 Get Object activity's Optional settings has a new Include tagging metadata in Response checkbox to return the tag-set of an object in the response. Thes3:GetObjectTagging
permission is required to use this setting.Note
In the 11.38 release, the
s3:GetObjectTagging
permission inadvertently became required. This permission is no longer required as of the 11.41 release unless you have enabled the new checkbox (disabled by default). -
BigCommerce connector API V3 support
A BigCommerce connection's Optional settings has a new API Version menu where you can select either BigCommerce API version V2 (Deprecated) (default existing) or V3 (newly supported). -
Coupa connector R41 support
The Coupa connector now uses version R41 of the Coupa Core Platform API. To use new objects introduced in R41 with existing activities, refresh the schema. -
Salesforce Einstein Analytics connector API version 63 support
The Salesforce Einstein Analytics connector has been verified to support Salesforce API versionv63.0
in its connection's Version field. -
Salesforce Events connector API version 63 support
The Salesforce Events connector has been verified to support Salesforce API version63
in its connection's API Version field. -
Shopify connector API 2025-01 support
A Shopify connection's API Version menu now has REST Admin API version 2025-01 as a selection. If updating an existing connection, see steps for changing the API version. -
SugarCRM v2 Query support for operators
A SugarCRM v2 (Beta) Query activity now supports operators in addition to sub-expressions.
Management Console
-
Display of Jitterbit MQ usage on the Dashboard page
The Dashboard's Licensing Usage panel now shows the number of transmitted and licensed Jitterbit Message Queue monthly messages. -
Dashboard auto-refresh interval updated
Data on the Dashboard page is now automatically refreshed every 15 minutes instead of every 1 minute.
Changes
Agent
- Observability configuration settings renamed
The[MetricLogging]
section of thejitterbit.conf
file is deprecated as of private agent version 11.41. The keys have moved to the[AgentMetrics]
section, with some keys being renamed. To provide feedback on agent observability (Beta), contact the Jitterbit Product Team.
Fixes
Agent and Design Studio
- Salesforce API upgrade to version 62 no longer causes transformation refresh error
An issue has been resolved where an upgrade to Salesforce API version 62 (available with Design Studio and agent version 11.35 to 11.40) prevented Salesforce transformations from being refreshed and returned the errorFailed to parse the response
. The fix requires Design Studio and agent version 11.41 or later. This issue was not present in Integration Studio.
Integration Studio
- Components no longer seem to disappear when converting a variable
Converting a global variable to a project variable via an individual project variable configuration dialog no longer causes a temporary issue rendering the components in the project pane's Components tab.
Integration Studio SDK connectors
-
Google BigQuery data type fields are now case-insensitive
The value provided for thedataType
andcolumnDataType
fields of a Google BigQuery Update Record activity and Create Structure activity, respectively, is no longer case-sensitive. -
Jitterbit MQ Get Bulk activity error resolved
A Jitterbit MQ Get Bulk activity no longer returns an error when executed using a queue name that does not exist. When a queue name does not exist, no results are returned.
Notices
Agent and Design Studio
-
End of life for versions 10.85 / 11.23
As of March 21, 2025, these product versions have reached end of life and are no longer supported:-
Private agent versions 10.85 and 11.23
-
Design Studio version 10.85
We recommend that users of these versions upgrade to the latest version as soon as practicable.
-
Agent
-
Private agent versions 10.x are no longer updated
Private agent version 10.87 was the last 10.x agent version distributed by Jitterbit and is intended to be the final supported 10.x agent version.Since Harmony release 10.63 / 11.1, both a 10.x and 11.x private agent version had been distributed with these differences:
-
11.x versions: In 11.1 and later versions, the PostgreSQL database bundled with the private agent is now version 14.5-1.
-
10.x versions: Supported 10.x versions are packaged with the existing 9.6.24-1 PostgreSQL. The distributed 10.x versions will continue to be supported in accordance with Jitterbit's end-of-life policy.
Important
To continue to receive private agent updates, including new features, enhancements, security patches, and fixes, upgrading to an 11.x private agent is required.
Follow the instructions to upgrade from 10.x to 11.x agents:
-
Windows agent upgrade instructions (requires a complete uninstall)
-
Design Studio
-
User action required: Salesforce retirement of API versions 21 to 30
Salesforce has announced the upcoming retirement of Salesforce Platform API versions 21.0 through 30.0 in its Summer '25 release (May or June 2025).As the Design Studio Salesforce connector has a feature that allows users to defer an upgrade of the Salesforce API version when opening an existing project that uses an earlier API version, it is possible that you may have projects using a Salesforce API version that is being retired. Any affected projects would have been originally created using Design Studio and agent versions earlier than Harmony 8.8 (released in March 2016).
We recommend following these steps to verify each Design Studio project uses a supported Salesforce API version as soon as possible to avoid issues with those integrations.
Design Studio and Integration Studio
-
User action required: Snowflake user
TYPE
property must be updated and future deprecation of single-factor authentication
Snowflake has announced the upcoming deprecation of single-factor authentication, which affects Integration Studio and Design Studio integrations that connect to Snowflake using a password.For those affected, user action is required in two phases:
-
By March 31, 2025, the
TYPE
property of the user account you use to connect to Snowflake must be set toLEGACY_SERVICE
in order to continue using password-based authentication (see Types of users). Without user action, existing integrations using Snowflake single-factor password authentication are expected to begin failing in April 2025. -
By November 2025, you must update the type of authentication used to connect to Snowflake to OAuth or key-pair authentication. At this time, password-based authentication will no longer be supported. In an upcoming release, the Integration Studio Snowflake connector will be updated to add support for the newly required authentication methods.
-