10.46 Harmony Release
The 10.46 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.46. 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 and API Gateway
- APAC: 14 December 2021 (AEDT), 13 December 2021 (PST)
- EMEA: 14 December 2021
- NA: 15 December 2021
Cloud Agent Groups and Private Agents
- Undo/redo in transformations
You can now undo and redo actions taken within transformations by using standard keyboard shortcuts or controls along the top of a transformation.
Intermittent log errors no longer occur
Detailed error messages are now consistently returned in the API Gateway logs. Previously, the log retrieval error
Target schemas with empty XML elements are now valid
When you use a target schema that has only nodes and no fields in a transformation, as is common with certain SOAP endpoints, the transformation is now considered valid even without having any target mappings and can now be deployed.
Send Email activity no longer overrides UI input
The request transformation of an Email Send Email activity now overrides the activity configuration UI settings only if the transformation provides data for individual fields. Previously, data in the To, CC, BCC, From, Mail Subject Line, or Mail Body UI fields was being overridden with empty values if a request transformation was providing data for any other fields.
Zendesk Search activity now supports user names and tags
You can now search for users by name or tag in a Zendesk Search activity.
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.