10.54 Harmony Release Notes¶
10.54 Harmony Release¶
The 10.54 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.54. 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 May 24, 2022 Private Agent version 10.36 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¶
APAC: June 2, 2022 (AEST), June 1, 2022 (PDT)
EMEA: June 2, 2022
NA: June 6, 2022
Production Cloud Agent Group and Private Agents¶
APAC: June 8, 2022 (AEST), June 7, 2022 (PDT)
EMEA: June 8, 2022
NA: June 9, 2022
The Docker Private Agent is available at Docker Hub at the conclusion of the NA region release:
APAC: June 10, 2022 (1 pm AEST)
EMEA: June 10, 2022 (3 am CEST)
NA: June 9, 2022 (6 pm PDT)
- Mirakl connector
The Mirakl connector can be used to read, create, update, or delete data in Mirakl. The connector will automatically be downloaded by agents version 10.1 or later as required.
- New Audit Logging UI
A new Audit Logging page allows administrators to retrieve logs of user login and activity taking place in Management Console and Cloud Studio. Previously, audit logs were accessible only by API.
Microsoft Teams additional query parameters are now supported
A Microsoft Teams List Channels activity now supports the query parameters
$expandto customize the response.
OData bind syntax is now supported
OData Update and Insert activities now have a
bindnode in their request schema, which allows you to provide a
valuefor each bind
ShipStation queries support additional fields
A ShipStation Query activity's request schema now contains fields that are relevant to the selected object instead of using a request schema common to all objects.
VTEX dynamic account names are now supported
A new Account Name field present in the configuration of each VTEX activity allows you to override the Account Name specified in the configuration of a VTEX connection. An activity-provided Account Name must be compatible with the App Key and App Token configured in the connection.
Visual indicator of undeployed changes
The deploy icon in an operation's toolbar is now highlighted in blue when the operation or any of its dependencies contain undeployed changes.
Enhanced deploy performance
When deploying, only components that have been changed since the last deploy (and their dependencies) are now deployed. In addition, deployments of changed project components now take less time to complete.
Enhanced project pane UI
The project pane can now be resized wider, improving the readability of long component names. In addition, the Components tab now reports a count of components in each category and the Show Activity Types setting is remembered.
Private Agent and SAP¶
- Changes required for SAP connector projects
As of Private Agent version 10.54, Jitterbit's SAP connectors will no longer work until you obtain and install the SAP library files as described in SAP Connector Installation. If the SAP library files have not been installed, your SAP operations will fail with an error indicating that the class for SAP JCo cannot be found.
- Archiving successful files from an FTP endpoint now works
The Use Success Folder option of a Cloud Studio or Design Studio FTP endpoint now works as expected. Since agent version 10.40, processed files were not being copied to the specified success folder on the Private Agent machine.
Custom schema edits no longer remove mappings
When you rename a custom schema field that has an existing mapping, the mappings now persist and are no longer removed.
Operations are now flagged as invalid when the same HTTP target activity writes to different targets In operations using the Two-Target Archive Pattern, if an HTTP activity in the Target 1 position writes a response to a second target activity (Target 2), then that HTTP target activity must not be used in any other operations where it writes to a different second target activity. Previously, such operations were not flagged as invalid and instead the response was written to only one of the targets.
Existing projects with affected operations will continue to run. However, design changes to accommodate this new validation rule are required to redeploy the project. If you need time to modify an existing project, you can disable this rule using a project setting (see HTTP Validation Rule Errors in Operation Validity).
Salesforce refresh on related objects now works
During configuration of a Salesforce-based Query activity (Salesforce, Salesforce Service Cloud, and ServiceMax connectors), the Refresh option present on the Select Related Object(s) column is now functional.
SAP Concur connection now requires OAuth2 authentication
A SAP Concur connection now requires OAuth2 credentials to be provided instead of those used for basic authentication, which is now deprecated by SAP Concur. This resolves an error reporting an unexpected element during testing of the connection.
Operation log UI issue fixed
The font and spacing in operation logs is now rendered as it was prior to the 10.53 release, which unintentionally introduced a rendering issue.
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.