Skip to Content

10.58 Harmony Release Notes

10.58 Harmony Release

The 10.58 Harmony release date is by region and component as listed below. This page includes release notes for all components being released as part of 10.58. See the related pages for Production Cloud Agent Group Releases, Sandbox Cloud Agent Group Releases, and Private Agent Releases for a compilation of updates limited to each of those components.


As of August 16, 2022 Design Studio and Private Agent version 10.40 have reached end of life and are no longer supported. We recommend that all users of these (and earlier) versions upgrade to the latest versions as soon as practicable.

Harmony Portal, Sandbox Cloud Agent Group, and Select Installers

The Harmony Portal and its applications, the Sandbox Cloud Agent Group, and select component installers (as applicable) are automatically updated as of these dates:

  • APAC: August 23, 2022 (AEST)

  • EMEA: August 23, 2022 (CEST)

  • NA: August 24, 2022 (PDT)

Private API Gateway updates were internal and are not included in the release notes below.

Production Cloud Agent Group and Private Agents

The Production Cloud Agent Group is automatically updated and Windows and Linux Private Agent downloads are available from the Harmony Portal Downloads page as of these dates:

  • APAC: August 30, 2022 (AEST)

  • EMEA: August 30, 2022 (CEST)

  • NA: September 1, 2022 (PDT)

The Docker Private Agent is available at Docker Hub at the conclusion of the NA region release:

  • APAC: September 2, 2022 (1 pm AEST)

  • EMEA: September 2, 2022 (3 am CEST)

  • NA: September 1, 2022 (6 pm PDT)

Private Agent updates were internal and are not included in the release notes below.

New Features

API Manager

  • Trusted IP Groups
    You can now define Trusted IP Groups that can be assigned to multiple security profiles to restrict API access to only those IPs in the assigned groups. Those with existing trusted IP ranges configured directly on a security profile are encouraged to assign IP groups going forward, as Trusted IP Groups will fully replace Trusted IP Ranges in a future release.


Cloud Studio

  • Conditions can now be set on any node
    Condition scripts can now be defined on nodes with any cardinality except [1] . Note that if the node is required and the condition evaluates to false, the operation may fail at runtime.

  • The top-level node can now be duplicated in flat schemas
    The Duplicate node option is now available to use on the top-level ___flat___ node of a flat schema.

  • Transformation search enhancements
    Enhancements have been made to searching in transformations to speed up the time it takes to return results.

  • Email connector now supports specifying the message type
    An Email Send Email activity now has a messageType field in its request schema that can be used to specify the type of message (such as text or HTML) in the request payload.

  • Email connector has improved error messages
    The Email connector now provides more useful error messages to help a user troubleshoot errors.

  • Snowflake connector now supports table names with spaces
    The Snowflake Merge, Insert, and Update activities can now be used with tables whose names include spaces.


Cloud Studio

  • Performance improved for large projects
    Performance is improved for large projects when auto-saving components that have many dependencies and when dragging and dropping components in the project designer.

  • 12 PM schedules are now reported correctly
    When a schedule configured to run at 12 PM is assigned to an operation, the time shown in the Assigned Schedule area is no longer incorrectly reported to be 12 AM.

  • Undeployed changes are no longer erroneously reported
    The blue deploy icon indicating the presence of undeployed changes no longer incorrectly appears after discarding changes to a component.

  • HTTP connection paths no longer add a trailing backslash
    The Path provided in an HTTP connection is no longer appended with a trailing backslash when none was specified by the user.

  • HTTP activity request parameters with quotes are now URL-encoded
    Single and double quotes included within request parameters provided in an HTTP activity are now automatically URL-encoded as expected.

  • SendGrid activities now respect the Continue on Error setting
    The Continue on Error setting in SendGrid activities is now functional. Previously, on encountering an error, activities stopped executing regardless of whether this option was set.

  • Shopify Create activity metafield values now work as expected
    Values provided in the fields of a Shopify Create request's metafield node now create a custom field and return field metadata as expected instead of failing with an exception indicating that the type can't be blank.

  • VTEX Update activity can now update sellers
    In a VTEX Update activity, the Marketplace object > Sellers sub-object now has the Update Seller by Seller ID action. Previously, this action was incorrectly associated with the Upsert activity and did not work there.

Harmony Platform

  • Project downloads are now successful
    An error no longer persists after a Harmony organization member tries to download a project that is deployed in at least one environment that they have limited permissions in.

Management Console

  • Agent download link now works
    The link provided announcing a new agent version in an orange banner along the top of the Management Console now goes to the Downloads page.


NetSuite, 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.


    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.