10.50 Harmony release notes¶
10.50 Harmony release¶
The 10.50 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.50. 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.
Note
As of March 8, 2022 private agent version 10.32 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 and Sandbox Cloud Agent Group¶
The Harmony portal and its applications and the Sandbox Cloud Agent Group are automatically updated as of these dates:
-
APAC: March 8, 2022 (AEDT), March 7, 2022 (PST)
-
EMEA: March 8, 2022
-
NA: March 9, 2022
Production Cloud Agent Group and private agents¶
The Production Cloud Agent Group is automatically updated and Windows and Linux private agent downloads are available from the Harmony portal Downloads page as of these dates:
-
APAC: March 18, 2022 (AEDT), March 17, 2022 (PDT)
-
EMEA: March 15, 2022
-
NA: March 16, 2022
The Docker private agent is available at Docker Hub at the conclusion of the NA region release:
-
APAC: March 17, 2022 (1 pm AEDT)
-
EMEA: March 17, 2022 (3 am CET)
-
NA: March 16, 2022 (6 pm PDT)
Enhancements¶
Agent¶
- New Jitterbit variable for returning multiple database results as a record set
The new Jitterbit variablejitterbit.scripting.db.search.rowset
can be set totrue
upstream of theDBExecute
function with a database and a JDBC driver. This will result in any calls to a stored procedure that returns multiple results to return the first non-empty record set instead of returning an empty set.
API Manager¶
-
Proxy API OpenAPI document uploads can now be any size
There is no longer a limit to the size of an OpenAPI document uploaded during proxy API configuration. Previously, uploads were limited to 400KB. -
Service URLs, names, and paths can now be longer
The character limits allowed for an API service URL, proxy API service name, and proxy API service path have each been increased to 2000 characters.
Fixes¶
API Manager¶
- Portal pages are now accessible after an environment is deleted
After an environment with published OpenAPI documentation is deleted, you no longer receive an error when accessing the Portal or Portal Manager pages. Instead, OpenAPI documentation for APIs in the deleted environment is no longer shown.
Cloud Studio¶
-
SOAP connector schemas now show all WSDL fields
All fields of a particular method selected from a WSDL are now visible in the SOAP connector activity's data schemas. Previously, some fields were missing. -
Amazon SQS Create Queue schema cardinality corrected
The request schema generated from an Amazon SQS Create Queue activity no longer requires optional parameters to be set, and now allows multiple optional parameters to be specified at once. -
Transformations with a source schema now require a preceding activity
For an operation to be reported as valid, a transformation with a source schema must now be preceded by an activity. Previously, if such a transformation was not preceded by an activity, the operation would appear as valid and could be deployed but would fail at runtime.
Notices¶
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.Warning
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.
SAP¶
- Upcoming required action for SAP connector users
In an upcoming Jitterbit private agent release, users of the SAP Connector (Cloud Studio SAP connector or Design Studio SAP connector) on a private agent must themselves obtain the SAP Java Connector (SAP JCo) development library from SAP and install it in the appropriate location on private agents in order for their projects to continue working. No action is required on cloud agents. Detailed instructions on installation will be forthcoming.
Related resources¶
- Jitterbit Trust (includes the latest release dates and times, as the schedule is subject to change)
- Sandbox Cloud Agent Group releases, Production Cloud Agent Group releases, and Private agent releases
- Release schedule
- Known issues
- Jitterbit end-of-life policy
- Jitterbit Community
- Jitterbit support