10.74 / 11.12 Harmony Release Notes¶

10.74 / 11.12 Harmony Release¶

This page includes release notes for all generally available components being released as part of 10.74 / 11.12. Compilations of release notes for Production Cloud Agent Groups, Sandbox Cloud Agent Groups, and Private Agents are also available.

The 10.74 / 11.12 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). The end-of-life date for these components is one year after the release date.

New Features¶

EDI¶

• Harmony EDI
  Harmony EDI is a new Harmony cloud application for managing EDI trading partners and transactions made with them. To get started, first configure an EDI trading partner on the Admin page. Then see the related transaction details and reprocess or acknowledge EDI transactions on the Transactions page.

  Note

  Harmony EDI is subscription-based. To use Harmony EDI, contact your Customer Success Manager (CSM).

Cloud Studio¶

• EDI for Cloud v2 connector
  The EDI for Cloud v2 connector can be used with Cloud or Private Agents 10.1 or later to get or send documents to or from a specified partner, or get or set the status of documents in the new Harmony EDI cloud application.

  Note

  The original EDI for Cloud connector for connecting to eiCloud is now deprecated but remains available and supported in projects where it was already being used.

Management Console¶

• Access token management
  The new Access Tokens page allows you to create and manage access tokens for use with the EDI for Cloud v2 connector.

Enhancements¶

Agent¶

• Ubuntu 22.04 LTS support
  Jitterbit has verified Ubuntu 22.04 LTS as a supported operating system for non-Docker Linux Private Agent installations.

Agent, Cloud Studio, and Design Studio¶

• NetSuite WSDL version 2023.1 support
  Jitterbit has verified support for NetSuite WSDL version 2023.1 with the Cloud Studio NetSuite Connector and the Design Studio NetSuite Connector.

• Salesforce API version 58 support
  Salesforce API version 58 is now supported for these connectors:

  • The Cloud Studio Salesforce, Salesforce Service Cloud, and ServiceMax connectors use API version 58 automatically with the use of a 10.74 or 11.12 agent.

  • The Design Studio Salesforce connector provides the option to use API version 58 with the use of both a 10.74 or 11.12 agent and 10.74 version of Design Studio. When opening an existing Design Studio project that uses this connector and meets both of these version requirements, you will be prompted to upgrade to Salesforce API version 58.

API Manager¶

• OpenAPI documentation in multiple environments
  From the Portal Manager page, you can now generate OpenAPI documentation for multiple environments instead of being limited to a single one. The API Portal page has a new menu to select the environment and also displays the base API URL.

• External user access in multiple organizations
  An external user can now be invited to and can access the API Portal page in multiple organizations instead of being limited to a single one.

• API Groups view mode
  A new View option is available for API groups that allows you to see the name, version, environment, and path of each API in the group without needing to open the group in edit mode.

Cloud Studio¶

• Improved performance
  Performance has been improved for projects with a very large number of components, especially those with many scripts and transformations.

• Epicor Prophet 21 Create activity support for multi-record data
  Certain nodes and fields in the request schema of an Epicor Prophet 21 Create activity now support array data, allowing you to provide data for multiple records in one request. In existing projects, you must refresh the activity’s schema to get this change.

• Google BigQuery Data Transfer activity simplified requirements
  The Enable Data Transfer checkbox in a Google BigQuery connection, which was previously required for using a Google BigQuery Data Transfer activity, is now removed. Instead, the requirements for using the Data Transfer activity are now set automatically and no additional steps are required beyond having the required roles granted to the service account.

• HTTP v2 (Beta) connector support for Amazon’s Selling Partner API
  The HTTP v2 (Beta) connector now works with Amazon’s REST-based Selling Partner API (SP-API).

• Microsoft Azure ESB connector support for Azure Active Directory
  A Microsoft Azure ESB connection has a new Authentication Type field to select either Shared Access Signatures (the existing supported authentication) or Azure Active Directory (newly supported). When selected, you specify the Namespace/Hostname, Tenant ID, Client ID, and Client Secret associated with an Azure Active Directory application with the Microsoft.ServiceBus permission set.

• OpenAI (Beta) connector support for Private Agent proxy settings
  An OpenAI (Beta) connection has a new field that can be selected to use Private Agent proxy settings for HTTPS proxy (NTLM proxy is not supported). In addition, the beta version of this connector is now available to all organizations. To provide feedback on bugs and enhancements, contact your Customer Success Manager (CSM).

• Salesforce Events (Beta) support for a specific Replay ID
  The Replay ID dropdown in a Salesforce Events (Beta) Subscribe activity now has the option to select From Specific Replay ID. When you provide a Specific Reply ID, the activity receives all events that occurred after the event with the specified replay ID.

• Shopify connector support for API version 2023-04 and cursor-based pagination
  Multiple enhancements have been made to the Shopify connector:

  • Shopify REST Admin API version 2023-04 is now available to select in the API Version menu of a Shopify connection.

  • Query activities now support cursor-based pagination using the new page_info request field and token response fields for the next and previous pages.

• Verbose logging support for additional connectors
  The Amazon Redshift, Amazon S3, DocuSign, and ServiceNow connectors now support connector verbose logging. The specific configuration entry of logger name and level is documented on the linked pages.

• Additional verbose logging details for multiple connectors
  Enabling verbose logging with the Algonomy Personalization and Amazon SQS 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.

Harmony Platform¶

• BMC OAuth 2.0 SSO auto-creation of users
  When configuring Harmony SSO with OAuth 2.0 with BMC as the OAuth provider and the Enable SSO URL checkbox is selected, a new Auto Add User option is available. It will create a new user with the specified Default Role if the user does not already exist.

• Jitterbit Message Queue limit increased to 50 queues
  The number of queues per environment provided by the premium-tier subscription has been increased from 25 to 50 queues.

• Harmony account creation with additional top-level domains
  Creating a Harmony account with an email address that ends in .africa, .ca, .inc, .llc, and .shop is now supported.

Fixes¶

Cloud Studio¶

• BigCommerce connector fixes
  Multiple fixes have been made to the BigCommerce connector:

  • You can now use a Query activity in the first source position of the operation patterns Transformation, Two-target Archive, and Two-target HTTP Archive, as expected. Previously, when there was no preceding request transformation, a runtime error occurred.

  • When a Query activity is configured with the Orders V2 > Get All Orders or Orders V2 > Get an Order object selections, the field external_order_id is now included in the response schema.

  • The data type of the existing external_id field in various activity schemas configured with the Orders V2 object has been corrected from integer to string. You must refresh affected schemas and make any necessary changes to mappings using this field.

• Database activity configuration issue resolved
  When configuring an activity from a Database connection whose password contains certain special characters, tables now load for selection as expected. Previously, an error indicating the data could not be fetched occurred. This issue did not affect connection tests or activity execution.

• HTTP v2 (Beta) connector fixes
  Multiple fixes have been made to the HTTP v2 (Beta) connector:

  • When Multipart is selected in a PATCH, POST, or PUT activity, a content type of multipart/form is now automatically sent without explicitly needing to set it. In addition, adding boundary data to each key is now automatically handled without any additional configuration.

  • A connection configured to use Custom proxy settings with a specified NTLM Domain now works.

  • The response body for HTTP status codes outside the 200 series is now returned. Previously, the response body was being returned only for successful responses.

  • Activities using OAuth 2.0 authorization now cache and reuse an existing valid access token instead of requesting a new access token on each activity execution. In addition, Message Authentication Code (MAC) tokens are now supported in addition to Bearer tokens.

  • A POST activity using AWS Signature authorization now sends the authorization header correctly, resolving an error executing the activity. In addition, when an activity using AWS Signature authorization has no request payload, an error no longer occurs.

• Microsoft Azure ESB queue consumption issue resolved
  When operations with different instances of Microsoft Azure ESB Consume Queue (Beta) activities are executed on the same agent, it is no longer possible for an operation to consume messages from the wrong queue.

• SOAP activities with many derived-type nodes can now be created
  You can now create SOAP activities from a SOAP connection configured with a large WSDL with many derived-type nodes. Previously, when attempting to create an activity instance, the UI did not respond and the activity would not be created.

Notices¶

Agent¶

• 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.

    Note

    Upgrading to an 11.x Windows Private Agent from 10.x requires a complete uninstall. Follow the documented instructions to complete the upgrade. Linux Private Agents can be upgraded as usual from any 10.x version.

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.

  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.

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