10.47 Harmony Release
The 10.47 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.47. 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.
Harmony Portal, Sandbox Cloud Agent Group, and Select Installers
APAC: 6 January 2022 (AEDT), 5 January 2022 (PST)
EMEA: 6 January 2022
NA: 10 January 2022
NOTE: The Design Studio installer was updated to version 10.47.0.19 on 19 January 2022 to fix an issue with installing Design Studio on macOS Big Sur (11.6).
Production Cloud Agent Group and Private Agents
APAC: 12 January 2022 (AEDT), 11 January 2022 (PST)
EMEA: 12 January 2022
NA: 13 January 2022
The Docker Private Agent is available at Docker Hub at the conclusion of the NA region release:
- APAC: 14 January 2022 (1 pm AEDT)
- EMEA: 14 January 2022 (3 am CET)
- NA: 13 January 2022 (6 pm PST)
TLS 1.0 and 1.1 are no longer supported by default for JDBC driver connectionsCloud and Private Agents 10.47 and later no longer support TLS 1.0 or 1.1 for JDBC driver connections to database endpoints by default.
If a database endpoint no longer works after an upgrade to a 10.47 or later agent, add
enabledTLSProtocols=TLSv1.2to the database connection string in Cloud Studio or Design Studio to force TLS 1.2 to be used (provided the protocol version is supported by the database endpoint).
On Private Agents, if TLS 1.2 is not supported by the database endpoint, TLS 1.0 or 1.1 can be re-enabled (though not recommended) on Private Agents by removing
jdk.tls.disabledAlgorithmssecurity property in the Private Agent
java.securityconfiguration file, which is located in these default directories:
C:\Program Files\Jitterbit Agent\jre\lib\security
New Microsoft Teams connector activities
The Microsoft Teams Add Members, Add Channels, and Chat activities allow you to add members to an existing channel, add new channels, and send messages to an individual member in a Microsoft Teams endpoint.
Support for additional OData query filter options
The OData Query activity now supports additional logical operators as filter options beyond Equals, including Not Equals, Greater Than, Greater Than or Equal, Less Than, and Less Than or Equal.
Cloud Studio and Design Studio
Support for NetSuite WSDL version 2021.2
Jitterbit has verified support for NetSuite WSDL version 2021.2 using agents version 10.33 and later.
Microsoft Dynamics AX 2012, Design Studio, and Agent
Microsoft Dynamics AX connector now returns headers
The Design Studio Microsoft Dynamics AX endpoint configuration screen now has a Return Header Values checkbox that can be used to return header information in the response. This feature requires the Microsoft Dynamics AX 2012 connector version 184.108.40.206 and a 10.47 or later version of both Design Studio and Private Agents.
Windows Quiet Agent Installer script version is now correct
The Windows Quiet Agent Installer script
config64.ps1now has the appropriate executable version in the
Agent_install_filefield. Previously, you needed to edit the script to correct the version.
Upcoming required action for SAP connector users
In an upcoming Harmony release, users of the Cloud Studio SAP Connector or Design Studio SAP Connector on a Private Agent must obtain the SAP Java Connector (SAP JCo) development library from SAP and install it in a designated location on Private Agents in order for your projects to continue working. No action is required on Cloud Agents. Detailed instructions on installation will be forthcoming.
NetSuite deprecation of HMAC-SHA1
Changes are required to any projects using HMAC-SHA1 as the signature algorithm. For a timeline of key dates and instructions on how to change the signature algorithm, see NetSuite HMAC-SHA1 Deprecation.WARNING: As NetSuite will no longer support HMAC-SHA1, you must change any Jitterbit Harmony projects that are presently using HMAC-SHA1 as the signature algorithm to use HMAC-SHA256 instead as soon as possible to avoid issues with those integrations.