Skip to Content

10.56 Harmony Release Notes

10.56 Harmony Release

The 10.56 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.56. 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 July 7, 2022 Private Agent version 10.38 has reached end of life and is 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: July 12, 2022 (AEST), July 11, 2022 (PDT)

  • EMEA: July 12, 2022

  • NA: July 13, 2022

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: July 19, 2022 (AEST), July 18, 2022 (PDT)

  • EMEA: July 19, 2022

  • NA: July 20, 2022

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

  • APAC: July 21, 2022 (1 pm AEST)

  • EMEA: July 21, 2022 (3 am CEST)

  • NA: July 20, 2022 (6 pm PDT)

New Features

Cloud Studio

  • Ripley Marketplace and YAMI connectors
    Two new connectors are available for use with agents version 10.1 or later. They will automatically be downloaded by an agent as required.

    • Ripley Marketplace: Read, create, or update data in Ripley Marketplace.

    • YAMI: Read, create, update, or delete data in the YAMI platform.


Cloud Studio and Design Studio

Cloud Studio

  • Exported projects are now smaller
    Exported Cloud Studio projects are now smaller in file size as they no longer include xml assets, which are regenerated at deploy time.

  • Nodes with condition scripts now show mapping lines
    When a source object or variable is used in a condition script, visual mapping lines are now shown connecting to the node, and the count of mappings includes nodes that the source object or variable is referenced in.

  • Searching in transformations is enhanced
    Searches within the source and target schemas of a transformation are now more usable with large and complex schemas with these enhancements:

    • Nodes dynamically expand and collapse to expose search results in context.

    • Text matches are now highlighted.

    • A count of matches and a navigator are now shown.

    • Script content is included in search results.

    • Data types are excluded from search results.

  • Epicor ERP connector rebranded to Epicor Kinetic
    The former Epicor ERP connector has been renamed to the Epicor Kinetic connector to reflect Epicor's latest release.

  • Shopify connector now supports Shopify API release 2022-04
    The Shopify connector now uses version 2022-04 of Shopify's APIs. Previously, the connector used version 2020-07.

  • VTEX connector now supports Offer Management APIs
    The VTEX connector now supports Offer Management APIs, whose actions can be selected during activity configuration in the Marketplace object > Offer Management sub-object.

  • VTEX Create activity can now create product and child SKUs together
    In a VTEX Create activity, the Catalog object > Product sub-object now has a new Create Product and SKU action that allows you to create a product and SKU together in the same activity instead of needing to create multiple activities.



  • DbExecute with an ODBC driver no longer causes Windows Private Agent crashes
    Using the DbExecute function against a database that uses an ODBC driver on a Windows Private Agent no longer causes memory issues resulting in an agent crash.

API Gateway

  • APIs secured with API key authentication can now be tested
    You can now test an API using a security profile configured with API key authentication by using the Execute button in the OpenAPI documentation generated through the Portal Manager page. Previously, an error was returned: Server Response: Type Error Failed to fetch.

API Manager

  • OpenAPI documentation is now generated for Custom APIs that write to the system variable
    OpenAPI documentation generated from the Portal Manager now includes Custom APIs that write to the jitterbit.api.response system variable, in addition to APIs that include an API request or response in the triggered operation.

  • Proxy API request headers can now be set not to override existing headers
    The Override Incoming setting of request headers in a Proxy API no longer prevents saving the API configuration when the setting is not selected. Previously, an exception occurred on attempting to save the configuration when Override Incoming was not selected.

Cloud Studio

  • Design component palette now remains collapsed after closing the project history
    The collapsed state of the design component palette now persists when exiting the project history pane.

  • Updated validation of condition scripts is now shown in the transformation UI
    A condition script referencing a source field is now revalidated when there are changes to the source field in the schema, such as after the source schema is removed or replaced. Previously, the condition's validation state was not refreshing in the UI of the transformation despite being accurately reflected in the validation on the design canvas.

  • Mapping count is now accurate after automapping to a collapsed node
    The count of mappings in a transformation is now updated accurately after automapping to a node where target fields being mapped to are in a collapsed state in the user interface.

  • HTTP verb can no longer be changed in an existing HTTP activity
    The HTTP Verb field in an HTTP GET, PUT, POST, or DELETE activity can no longer be changed to a verb other than one appropriate to the activity type being used. Previously, you could, for example, create a GET activity and then change the HTTP Verb to PUT. Now, a GET activity must use a GET verb.

  • Epicor Kinetic Get BAQ activity can now return a single BAQ service
    An Epicor Kinetic Get BAQ activity no longer returns an error when getting the definition of a specific BAQ service rather than a list of BAQ services.

  • JMS session handling now works properly on commit or rollback
    The commit/rollback behavior and session caching in the JMS connector no longer results in closing the last transacted session prematurely. In addition, certain connection exhaustion and messaging processing issues are now resolved.

  • Microsoft Teams activities with channel selection can now be configured
    During configuration of a Microsoft Teams List Channels, Add Members, or Send Message activity, the table of Microsoft Teams channels to select from is now loaded as expected. Previously, the activity configuration could not be completed.

  • SendGrid Send activity supports additional fields
    A SendGrid Send activity now has additional fields in its request schema that allow sending emails using all fields provided by SendGrid's Mail Send API.

  • Via B2B Initial Load activity no longer returns an invalid warning
    A Via B2B Initial Load activity no longer returns an invalid warning reporting an error writing the XML value. The schemas in existing activities must be refreshed to receive this fix.


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.