Skip to Content

10.72 / 11.10 Harmony release notes

10.72 / 11.10 Harmony release

This page includes release notes for all generally available components being released as part of 10.72 / 11.10. Compilations of release notes for Production Cloud Agent Groups, Sandbox Cloud Agent Groups, and private agents are also available.

The 10.72 / 11.10 release is staggered based on the dates and times as listed below by component and region. 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, which is available at Docker Hub). The end-of-life date for these components is one year after the release date.

11.10 Sandbox Cloud Agent Group
Cloud platform and applications
11.10 Production Cloud Agent Group
11.10 and 10.72 Windows and Linux private agents
11.10 Docker private agent
APAC June 13, 2023 (12 - 4 AM AEST) June 21, 2023 (2 - 8 PM AEST) June 23, 2023 (8 PM AEST)
EMEA June 13-14, 2023 (10 PM - 2 AM CEST) June 22, 2023 (6 AM - 12 PM CEST) June 23, 2023 (12 PM CEST)
NA June 14, 2023 (1 - 5 PM PDT) June 22-23, 2023 (9 PM - 3 AM PDT) June 23, 2023 (3 AM PDT)

Note

As of June 23, 2023 private agent version 10.55 has reached end of life and is no longer supported. We recommend that all users of this version (and earlier) upgrade to the latest version as soon as practicable.

New features

Cloud Studio

  • OpenAI (beta) connector
    The OpenAI (beta) connector can be used to generate text or an image based on a provided text prompt, or can transcribe or translate audio into text. This connector is available for use with both cloud and private agents version 10.1 or later. For beta access, contact your Customer Success Manager (CSM).

Enhancements

Agent

Cloud Studio

Fixes

Agent

  • Operations with chunking enabled now output the expected content type
    When an operation has chunking enabled, transformations configured with JSON output are no longer unexpectedly converted to XML output.

  • Error writing Salesforce bulk query results to a file no longer occurs
    When the type of encoding differs between a Cloud Studio Salesforce Bulk Query activity or a Design Studio Salesforce Bulk Process Query action source and its target, a fatal error writing the result to a file no longer occurs. The former error had indicated: Reason: The process cannot access the file because it is being used by another process.

API Manager

  • Proxy API 405 error after deleting and re-publishing no longer occurs
    After exporting and deleting a published proxy API that uses a custom method, and then re-importing and publishing the proxy API, it now works as expected. Previously, when the proxy API was called, the error 405 Method Not Allowed was returned.

Cloud Studio

  • User action required to fix error with duplicated nodes in transformation mappings
    Executing a transformation that contains mappings within newly duplicated nodes no longer results in the following operation runtime error, where the node referenced in the error message is one that has been duplicated:

    Failed to initialize transformation "<Transformation Name>". Failed to expand the target tree for the path:<Node Path>. The node:<Node Name> cannot be created.
    

    In existing transformations already experiencing this error, you must first remove the duplicated node and then duplicate it again to resolve the error.

  • Private agent-only connectors are now prevented from being imported or migrated to cloud agents
    You can no longer import or migrate projects that use private agent-only connectors to environments associated with cloud agents. Previously, when a private agent-only endpoint was imported or migrated to cloud agents, its connection was unable to be tested and its activities were invalid.

  • Active Directory Update activity now works with user account and password fields
    Using an Active Directory Update activity to update the UserAccountControl and UserPassword fields now works as expected.

  • Google BigQuery connector now supports the record data type
    Google BigQuery Query, Update Record, and Insert Record activities now treat the record data type as expected instead of interpreting it as a string.

  • Jira connector fixes for on-premises instances
    When an on-premises instance type is selected in a Jira connection, these issues are now resolved:

    • Jira Create, Update, and Delete activities no longer unexpectedly return duplicate occurrences of information in their responses.

    • When configured with the Get Transition operation, a Jira Transition activity now returns the field opsbarSequence in its response.

    • The selection of 8.2.3 for the Jira server version has been corrected to 8.22.3. This was an error in display only.

  • JMS connection no longer requires a password
    When the Use Authentication checkbox in a JMS connection is selected, entering a Password is no longer required. This enables the use case where the JMS server has only a username with no password. Previously, when an empty variable was used as the password, activities failed to return a response.

  • OData Query activity now supports enumerated fields
    Fields with an enum data type are now displayed for selection in an OData Query activity. This enables querying App Builder dropdown fields using the App Builder OData API.

  • Temporary Storage Write activity edits no longer clear its schema in adjacent transformations
    Editing a Temporary Storage Write activity that is used in multiple operations no longer causes its schema to be cleared from adjacent transformations that are inheriting that schema.

Harmony portal

  • New users can now register in organizations using two-factor authentication
    When a new user is invited to an organization that has two-factor authentication enabled, the user is now able to complete the registration. Previously, an authorization error occurred.

Management Console

  • Error when saving organization policies no longer occurs
    A generic exception is no longer returned when saving updated organization policies.

Notices

Agent

  • Jitterbit’s intention to stop distributing private agent 10.x
    Jitterbit intends to stop distributing a 10.x private agent version within the next several Harmony releases. Since Harmony release 10.63 / 11.1, both a 10.x and 11.x private agent version have 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: Current 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.

      Note

      Upgrading to an 11.x Windows private agent from 10.x requires a complete uninstall. Follow the documented instructions to complete the upgrade. Linux private agents can be upgraded as usual from any 10.x version.

Shopify connector, Cloud Studio

  • Shopify Fulfillment API deprecation
    Shopify has announced it is deprecating some endpoints on its Fulfillment API on June 30, 2023. Customers with Cloud Studio projects using the Shopify connector with deprecated Fulfillment API endpoints must reconfigure the connector as soon as possible, or operations using the deprecated API endpoints will begin failing after June 30, 2023. For additional information, see details on impacted projects and required user action.

NetSuite connector, Cloud Studio, and Design Studio

  • HMAC-SHA1 deprecation and removal from the Cloud 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 Cloud 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 Harmony NetSuite connectors, you should change any 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.