10.64 / 11.2 Harmony Release Notes¶
10.64 / 11.2 Harmony Release¶
This page includes release notes for all generally available components being released as part of 10.64 / 11.2. Compilations of release notes for Production Cloud Agent Groups, Sandbox Cloud Agent Groups, and Private Agents are also available.
The 10.64 / 11.2 release is staggered based on the dates as listed below by region. The date sets used for each component are identified in the tables that follow. See the Jitterbit Trust site for specific times.
|Date Set 1||Date Set 2||Date Set 3|
|APAC||Jan. 5, 2023 (AEDT)||Jan. 11, 2023 (AEDT)||Jan. 13, 2023 (1pm AEDT)|
|EMEA||Jan. 5, 2023 (CET)||Jan. 11, 2023 (CET)||Jan. 13, 2023 (3am CET)|
|NA||Jan. 9, 2023 (PST)||Jan. 12, 2023 (PST)||Jan. 12, 2023 (6pm PST)|
As part of this release, the Harmony platform and Harmony cloud applications (as applicable) are automatically updated by these dates:
|Cloud Components||Release Date|
|Harmony platform and Harmony Portal cloud-based applications||Date Set 1|
These versioned components are available from the Downloads page (unless noted) by these dates:
|Locally Installed Components||Version||Release Date|
|Windows Private Agent |
Linux Private Agent
|10.64, 11.2||Date Set 2|
|Docker Private Agent |
(available at Docker Hub)
|11.2||Date Set 3|
The Jitterbit Cloud Agent Groups are automatically updated to these versions by these dates:
|Jitterbit Cloud Agent Group||Version||Release Date|
|Sandbox Cloud Agent Group||11.2||Date Set 1|
|Production Cloud Agent Group||11.2||Date Set 2|
As of January 13, 2023 Design Studio and Private Agent version 10.47 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.
Cloud Firestore Delete activity option to continue on an error
During configuration of a Cloud Firestore Delete activity, the new checkbox Continue on Error can be used to continue the operation if an error is encountered.
Snowflake connector support for loading data from Google Cloud or Microsoft Azure storage
During configuration of a Snowflake Insert activity with the Stage File approach, you can now configure a stage type of Google Cloud Storage or Microsoft Azure to use for loading data.
Stripe connector support for Payment Links, Billing, and Connect objects
During configuration of a Stripe activity, you can now select the Payment Links, Billing, or Connect objects and their associated sub-objects and actions using the Stripe API.
- Additional security option for Cloud Studio connector configuration
A new Enable Re-authentication on Change setting is available in an organization’s policies. When enabled, certain changes made to a Database, FTP, NetSuite, Salesforce, Salesforce Service Cloud, or ServiceMax connection will require that you re-enter credentials for certain fields before saving your changes.
We recommend updating existing Cloud Studio and Design Studio projects that have a saved hash for binary files to use the new output.
As an alternative, to maintain the behavior prior to this change, you can set
$jitterbit.md5.hash.use.file.mode.string.only=truein a script upstream of the function call to generate the same values as prior to this change.
- New Harmony trial licenses no longer include
TRIALin the API URL
TRIALis no longer included as part of an API Manager API service URL. This change does not affect existing trials. To remove the word
TRIALfrom an existing API URL, contact Jitterbit Support.
- Private Agents now run after installation without an environment
When installing a Private Agent in an Agent Group that does not have an associated environment, it will again start up in Running status. Previously, since Private Agent version 10.61, the agent status after installation was Stopped and prevented from running until an environment was associated.
Mapping fields with colons is now supported
You can now map transformation fields that contain a colon in the field name. Previously, an error referring to an undefined token occurred on attempting to map the field.
Refreshing a transformation now maintains the user’s state
When you refresh a transformation, nodes that are collapsed or expanded are now maintained in their last accessed state. This also resolves an error indicating the value of Jitterbit states exceeded the quota.
Database activity configuration now shows tables using connection string parameters
When configuring a Database activity, tables are now fetched using any information provided in the Additional Connection String Parameters field of the associated connection. Previously, though input in this field was passed to the agent during a test of the connection, it was not being passed to the agent during activity configuration.
OData and Microsoft Azure AD Query activities now return the correct data type
Values with a decimal data type are no longer converted to integer values when returned by an OData Query or MS Azure AD Query activity.
Jira connector improved support for on-premises Jira instances
Multiple issues have been fixed when using the Jira connector with an on-premises Jira instance:
VTEX Read response now includes the
In the VTEX Read activity response schema for the Master Data V2 object > Customer Profiles sub-object > Get Unmasked Address action, the
documentfield is now returned in the
documentnode. This fixes an issue where the operation was completing with a Success with Warning status.
Workday Get activity now supports
Resource_Managementwith later WSDL versions
When configuring a Workday Get activity, the
Resource_Managementservice and its associated operations are now available to select when using a Workday WSDL version that is v36.0 or later.
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 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.