10.78 / 11.16 Harmony Release Notes¶
10.78 / 11.16 Harmony Release¶
This page includes release notes for all generally available components being released as part of 10.78 / 11.16. Compilations of release notes for Production Cloud Agent Groups, Sandbox Cloud Agent Groups, and Private Agents are also available.
The 10.78 / 11.16 release is staggered based on the dates and times as listed below by component and region. You can subscribe to maintenance notifications for cloud-based components at Jitterbit Trust. Locally installed components are available from the Downloads page (except for the Docker Private Agent, which is available at Docker Hub).
|11.16 Sandbox Cloud Agent Group |
10.78 API Gateway
Cloud Platform and Applications
|11.16 Production Cloud Agent Group |
11.16 and 10.78 Windows and Linux Private Agents
|11.16 Docker Private Agent|
|APAC||October 17, 2023 (12 - 4 AM AEDT)||October 24, 2023 (3 - 9 PM AEDT)||October 26, 2023 (9 PM AEDT)|
|EMEA||October 17-18, 2023 (9 PM - 1 AM CEST)||October 25, 2023 (6 AM - 12 PM CEST)||October 26, 2023 (12 PM CEST)|
|NA||October 18, 2023 (12 - 4 PM PDT)||October 25-26, 2023 (9 PM - 3 AM PDT)||October 26, 2023 (3 AM PDT)|
As of November 3, 2023 Private Agent version 10.61 has reached end of life and is no longer supported. We recommend that all users of this version (and earlier) upgrade to the latest version as soon as practicable.
- API health monitoring
A new API Health Monitoring module on the Analytics page shows a list of slow-running Custom APIs. The average response time is listed for each API exceeding the configured response threshold within the configured timeframe up to 48 hours ago.
- Multi-agent support for listening activities
Cloud Studio connector activities that use the listening service are now supported in Private Agent Groups that contain multiple agents. To use a multi-agent group, additional prerequisites must be met. In addition, persistence can be enabled so that if an agent stops, messages can be resent when the agent comes back online.
Ability to use an existing global connection with an imported project
When importing a project that uses global connections, you can now choose whether to Use an existing global connection to associate with the relevant activities from the imported project, or Create a new global connection that must be configured in the selected environment after the project import.
Ability to test all environment endpoints
During configuration of a global connection, a new Test All Connections button tests all environment endpoints in a global connection and displays a list of their connection statuses.
Real-time operation status for canceled operations
The operation status reported in the operation logs and in the lower left of an operation on the design canvas now updates in real-time after using the Cancel button next to it. Previously, after canceling an operation a refresh was required to see the updated status.
Tooltips in the custom schema editor
The custom schema editor for flat schemas now displays a tooltip for the Field and Default Value fields. The custom schema editor for hierarchical schemas now displays a tooltip for the Node and Field fields. The tooltips allow you to see long names without clicking into the field.
Execute activities for multiple connectors
The following connectors each have a new Execute activity that can be used to execute a procedure at the connected endpoint. These connectors also now use an updated version of the Log4j library.
Square v2 connector enhancements and public beta
Multiple enhancements have been made to the Square v2 (Beta) connector, whose beta is no longer limited to select organizations:
A Create activity now supports the Catalog > Create catalog image sub-object selection.
An Update activity now supports the Catalog object > Batch upsert catalog objects, Update catalog image, and Upsert catalog object sub-object selections.
Additional verbose logging details for multiple connectors
Enabling verbose logging with the Elasticsearch and Jira connectors results in the generation of additional log information beyond that already generated. To generate the additional log details, a new format of the configuration entry is required as documented on the linked pages.
- Tradacoms support
EDI documents in Tradacoms format can now be processed. The available formats depend on the configured trading partner.
- Services no longer stop after an install when remote agent configuration is enabled
After installing a 10.75 / 11.13 Private Agent or later in an organization using the organization policy Enable Remote Agent Configuration, services no longer stop after initially starting, rendering the agent inoperable. Previously, an issue was occurring when the agent attempted to sync the agent configuration file, causing all services to stop.
X-Jitterbit-TraceIdheader now works
Trace logs now generate as expected when passing
X-Jitterbit-TraceIdin the header of an API Manager API call.
Application slowdown after several hours no longer occurs
Performance has been improved when the Cloud Studio application has been open in the same session for several hours.
Database activity configuration 500 error no longer occurs
When configuring a Database connector activity, a
error no longer occurs while fetching data from a Database endpoint connected using a manual connection string with additional parameters. This error occurred only at design time in the activity configuration; testing the connection and operation runtime were unaffected.
Microsoft Azure ESB Get Queue Message activity no longer deletes next messages when queue is empty
When a Microsoft Azure ESB Get Queue Message activity is configured with Receive and Delete mode, if the queue is empty at the time of activity execution, then new messages in the queue are no longer immediately deleted. Previously, a counter was being set to delete messages as soon as they arrived in the queue.
OpenAI connector error related to Base64-encoded files no longer occurs
The OpenAI Create Transcription and Create Translation activities no longer fail when provided with a Base64-encoded file in the selected file format. Previously, a runtime error reported an unrecognized file format.
Salesforce Events (Beta) test connection buffering error no longer occurs
When testing a Salesforce Events (Beta) connection to a Salesforce instance with a large number of custom objects, an error reporting that the buffering capacity was exceeded no longer occurs.
- Jitterbit MQ Get and Get Bulk activities now retrieve unacknowledged messages that have returned to a ready state
In a Jitterbit Message Queue, Unack Messages that are not acknowledged within 30 minutes and have since returned to Ready Messages can now be retrieved as expected. Previously, a Jitterbit MQ Get or Get Bulk activity configured to retrieve the messages didn’t return the messages in its response payload.
- Two-factor authentication code is now required only after the configured number of days
When the organization policy Two-Factor Authentication (TFA) is enabled, users are no longer prompted to enter a TFA code on every login. Instead, the configured number of days is now used as expected.
Jitterbit’s intention to stop distributing Private Agent 10.x
Jitterbit intends to stop distributing a 10.x Private Agent version within the next several Harmony releases. Since Harmony release 10.63 / 11.1, both a 10.x and 11.x Private Agent version have been distributed with these differences:
11.x versions: In 11.1 and later versions, the PostgreSQL database bundled with the Private Agent is now version 14.5-1.
10.x versions: Current 10.x versions are packaged with the existing 9.6.24-1 PostgreSQL. The distributed 10.x versions will continue to be supported in accordance with Jitterbit’s end-of-life policy.
NetSuite Connector, 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.