Skip to Content

10.12 Harmony release notes

10.12 Harmony release

Harmony portal, private agents, and Sandbox Cloud Agent Group released January 6, 7, and 9, 2020

The 10.12 release date is by region:

  • APAC: Released 6 January 2020

  • EMEA: Released 7 January 2020

  • NA: Released January 9, 2020

Included in this release are updates to these Harmony components:

The Sandbox Cloud Agent Group and cloud applications accessed through the Harmony Portal were updated to 10.12 at the time of the release. Private Agent installers are available in each region as of the conclusion of each region's release.

As of January 14, 2020, Design Studio and Private Agent versions 9.7 have reached end of life and are longer supported. We recommend that all users of these (and earlier) versions upgrade to the latest versions as soon as practicable.

New features


Cloud Studio

  • Project backups and restore
    Project backups are now automatically created upon deploying a project. You can access project backups from the project history by selecting Restore this version from the actions menu available on a project deploy event.



  • PostgreSQL database driver updated to 9.4
    The PostgreSQL JDBC database driver that is packaged with Private agents and the Jitterbit cloud agent groups has been upgraded from PostgreSQL JDBC Driver 9.1 to 9.4.

Cloud Studio

  • ServiceNow connector driver updated to V19
    The ServiceNow connector has been upgraded from ServiceNow CData JDBC Driver V18 to V19.


Cloud Studio

  • Project variables can now be edited directly from the list view
    The summary table of project variables that shows all project variables in a single list can now be edited inline, without requiring you to open an individual variable's configuration. Project variables can also be deleted in bulk from this screen.

  • Deploying a project is now faster
    The deploy process has been enhanced so that unchanged components are not redeployed. This speeds up deploying a project.



  • Linux Agents processing web services with a SOAP fault now report the correct status
    When using a Linux private agent or a Jitterbit cloud agent group to run a SOAP-based web service operation, the operation status is now correctly reported as a SOAP Fault as applicable. Previously, as of version 10.1 Linux Agents, the operation status for a SOAP fault was incorrectly being reported as an Error status. This issue affected operations using SOAP endpoints in Cloud Studio, and Web service method and Workday endpoints in Design Studio.

  • Data syncing errors related to API calls no longer occur
    When running operations that call an API, intermittent 400 errors related to data syncing no longer occur.

Cloud Studio

  • Renamed components are now updated wherever they are referenced
    After renaming a component, any area of the project where the component is referenced will reflect the updated component name.

  • Operation status is now indicated on child operations
    After manually running an operation, operations that are downstream in the operation chain now display the real-time operation status in the same manner it is displayed for the top-level operation.

  • Invalid mapping errors now disappear when resolved
    After resolving an error regarding an invalid mapping, the new mapping is now validated properly. Previously, in some cases the invalid mapping error would persist in the UI even after the error was resolved.

  • Mappings with special characters are now valid
    Target field mappings that contain special characters such as a hyphen (-) or a period (.) are now validated properly. Previously, the mapping would be displayed as invalid even if there was no issue with the mapping.

  • Empty transformation scripts now show default tags
    When mapping a target field in a transformation using a script, the Jitterbit Script <trans> </trans> tags are now shown by default. Previously, the tags would appear only after the script was saved.

  • Migrating a project more than once now works
    An already-migrated project can now be successfully migrated to a third environment. Previously, a generic "unexpected" error would occur and the project in the second target environment would be empty.

  • Database table/column names delimited by special characters are now supported
    When using a database that uses special characters (any of / . * = ? | ( ) [ ] { or }) as delimiters, database tables are now accessible during configuration of a Database activity. The characters used to define delimiters (Quote Begin and Quote End) can be specified in the Private agent configuration file under the [DbDrivers] section.

  • A Snowflake view can no longer be selected in a Snowflake Delete activity
    During configuration of a Snowflake Delete activity, views are no longer shown in the object selection screen. Previously, if you selected a view for deletion, you would receive an error message that the object must be a table.