11.33 Harmony release notes
11.33 Harmony release
The 11.33 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.33 Sandbox Cloud Agent Group (SCAG) SDK connectors on 11.33 SCAG 11.33 Design Studio 1.0.4.2 Jitterbit Microsoft Dynamics 365 Cloud Connector Cloud platform and applications | 11.33 Production Cloud Agent Group (PCAG) SDK connectors on private agents and 11.33 PCAG 11.33 Windows and Linux private agents | 11.33 Docker private agent | |
|---|---|---|---|
| APAC | October 8, 2024 (1 - 5 AM AEDT) | October 15, 2024 (3 - 9 PM AEDT) | October 17, 2024 (9 PM AEDT) | 
| EMEA | October 8-9, 2024 (9 PM - 1 AM CEST) | October 16, 2024 (6 AM - 12 PM CEST) | October 17, 2024 (12 PM CEST) | 
| NA | October 9, 2024 (12 - 4 PM PDT) | October 16-17, 2024 (9 PM - 3 AM PDT) | October 17, 2024 (3 AM PDT) | 
The 11.33 Harmony release also includes the release of App Builder 4.0.35607 (11.33), whose release notes are provided separately.
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 SDK connectors
- Microsoft Azure Key Vault (Beta) connector
 The Microsoft Azure Key Vault (Beta) connector is now available to all organizations. It can be used with cloud or private agents to query, create, update, or delete a vault or vault objects in Microsoft Azure Key Vault.
Enhancements
Agent and Design Studio
- Logo updates
 The Jitterbit logo has been updated for private agents and Design Studio to reflect Jitterbit’s new brand.
EDI
- 
UX redesign of EDI and communication settings 
 The Admin page’s EDI settings and Communication settings tabs have a more intuitive UI, showing basic settings up front and advanced settings in expandable tabs.
- 
Additional EDI settings 
 The new EDI settings tabs Interchange, Functional Group, and Separators contain additional fields you can configure when using the applicable EDI standard. Providing these values in the EDI settings makes it unnecessary to provide this information via the Integration Studio EDI for Cloud v2 connector.
Harmony portal
- UI updates and Integration Studio rename
 The Harmony portal has an improved look and feel with updated colors, typography, and product logos that reflect Jitterbit’s new brand. As part of the branding updates, Jitterbit’s web app for creating workflows and integrations has been renamed to Integration Studio (formerly Cloud Studio).
Integration Studio
- Improved visibility of in-use endpoints
 The design component palette Project endpoints and connectors tab now differentiates between endpoints with activity instances that are used in the project (Endpoints used in this project) and endpoints where only a connection has been configured (Available endpoints).
Integration Studio SDK connectors
- 
Amazon S3 connector AWS SDK version upgrade 
 The Amazon S3 connector is now based on version 1.12.770 of the AWS SDK for Java to support V2 of the REST API.
- 
Epicor Kinetic connector new activities and improved encoding 
 The Epicor Kinetic connector has the following enhancements:- 
The new activities Get Custom Method and Post Custom Method allow you to retrieve or insert data in an Epicor Kinetic service using a custom method. 
- 
In an Update activity, URL path parameters are now encoded, allowing the use of characters such as a slash, hyphen, or space. 
 
- 
- 
HTTP v2 connector ability to follow redirects and Bulk activity general availability 
 The HTTP v2 connector has the following enhancements:- 
An HTTP v2 connection has a new Follow redirects checkbox in its Advanced HTTP Properties that can be used to allow rerouting of the base URL up to the number of times specified in the Maximum number of redirects field. 
- 
The HTTP v2 Bulk activity, used to send multiple HTTP or HTTPS requests, is no longer a beta version. 
 
- 
- 
Microsoft Azure Service Bus connector rename 
 The Microsoft Azure ESB connector has been renamed to the Microsoft Azure Service Bus connector.
- 
Microsoft Entra ID connector rename 
 The Microsoft Azure AD connector has been renamed to the Microsoft Entra ID connector.
- 
Workday connector OAuth support 
 A Workday connection has a new Authentication type menu that provides the option to select Basic Auth (default existing) or JWT Bearer OAuth (newly supported). To obtain the required credentials and configure OAuth, see the Workday OAuth prerequisites.
Management Console
- 
Ability to refresh Agents page 
 The Agents page now has a Refresh icon for reloading the screen after changes.
- 
Premium tier Message Queue limit increase 
 Premium-tier subscribers of the Jitterbit Message Queue service can now configure a Message Limit of up to 100,000 messages for new queues on the Message Queues page. Existing queues remain limited to the former limit of 50,000 and must be reconfigured to have the new limit applied.
Fixes
Agent
- Evalfunction behavior with- RunOperationcorrected
 When used with the- RunOperationfunction, the- Evalfunction now inspects the results of- RunOperationand if it returns- false, then it will process the second argument.
Integration Studio
- 
SOAP connector WSDL upload with XSD imports no longer fails 
 In a SOAP connection, providing a ZIP of a WSDL that contains XSD import references now works as expected. Previously, after selecting the root, an error was being returned indicatingFailed to upload file - Maximum call stack size exceeded.
- 
Derived-type nodes can now be duplicated 
 A custom field using a derived type can now be duplicated successfully. Previously, after duplicating the node and selecting a derived type, clicking OK did not take effect to duplicate the node.
- 
Duplicated nodes no longer collapse unexpectedly 
 Duplicated nodes no longer automatically collapse unexpectedly while modifying fields within them.
- 
An API security profile is no longer incorrectly required 
 When the organization policy Require security profile to publish is disabled, assigning a security profile is no longer required to publish an operation as an API.
Integration Studio SDK connectors
- 
Active Directory v2 connector error messages improved 
 The Active Directory v2 connector returns clearer error messages when an authentication error occurs.
- 
GraphQL v2 connector response schema fixed 
 A response schema correction to the GraphQL v2 connector fixes the runtime errorParameter at indexwhen working with Shopify’s GraphQL endpoints.
- 
HTTP v2 GET activity custom response extra subelementwarning no longer occurs
 When the response from an HTTP v2 GET activity configured with a custom response schema returns aContent-Typeheader that is in a format other than JSON, XML, HTML, or text, the structure of the response no longer incorrectly uses the standard response schema structure and returns anextra subelementwarning.
Jitterbit CRM REST connector
- Microsoft Dynamics CRM connector now supports the connectionobject
 An Integration Studio or Design Studio Microsoft Dynamics CRM connector activity configured with theconnectionobject now works as expected to link two entities. Previously, the connection between those entities failed with the messageThe selected record does not support connections. You cannot add the connection.This fix requires version 1.0.4.2 of Jitterbit’s Microsoft Dynamics 365 Cloud installer provided through the Harmony portal Downloads page.
Management Console
- Whitelist IP range no longer requires current user’s IP in every range
 The organization policy User Management feature Enable whitelist IP range now allows additional ranges that do not include the current user’s IP to be added when there is already another range that includes the current user’s IP.
Notices
Agent and Design Studio
- 
End of life for agent 10.77 / 11.15 and Design Studio 10.77 
 As of September 27, 2024 these product versions have reached end of life and are no longer supported:- 
Private agent versions 10.77 and 11.15 
- 
Design Studio version 10.77 
 We recommend that all 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) 
 
- 
NetSuite connector, Integration Studio, and Design Studio
- 
HMAC-SHA1 deprecation and removal from the Integration Studio and Design Studio UI 
 NetSuite is deprecating HMAC-SHA1 as a valid signature algorithm as previously announced (see NetSuite HMAC-SHA1 deprecation). To support these changes, Jitterbit intends to remove the HMAC-SHA1 signature algorithm from the Integration Studio and Design Studio UI in an upcoming Harmony release.Warning As the HMAC-SHA1 signature algorithm will no longer be supported by NetSuite or the Jitterbit Harmony NetSuite connectors, you should change any Jitterbit Harmony projects that are presently using HMAC-SHA1 as the signature algorithm to use HMAC-SHA256 as soon as possible to avoid issues with those integrations.