Skip to Content

10.5 Harmony release notes

10.5 Harmony release

Harmony portal, private API gateway, private agents, and Sandbox Cloud Agent Group released August 7, 8, and 12, 2019

The 10.5 release date is by region:

  • APAC: Released 7 August 2019

  • EMEA: Released 8 August 2019

  • NA: Released August 12, 2019

Included in this release are updates to these Harmony components:

Web applications accessed through the Harmony portal were updated to 10.5 at the time of the release. Private agent and private API gateway installers are available in each region as of the conclusion of each region's release.

New features

Cloud Studio

  • New connectors
    New Cloud Studio connectors for Google Sheets and Zendesk are now available to use with agents version 10.1 or higher. The new connectors can be accessed on the right side of the project designer from the design component palette and will automatically be downloaded by an agent as required.

Changes

Harmony portal

  • Session timeout increased
    After logging in to the Harmony portal, you will automatically remain logged in for 24 hours after your last activity, unless you manually log out before then.

Enhancements

Cloud Studio

  • Complex CSV schemas are now supported
    When creating a custom hierarchical schema, new options for creating a fixed-width or character-delimited complex CSV are now available. Previously, hierarchical schemas were created as XML by default.
  • XSD schemas with imports/includes are now supported
    When defining a sample file schema, you can now upload XSDs that import or include each other, either by URL or by providing a ZIP file with reference to all associated XSDs.
  • Global variables can now be converted to project variables
    When configuring a project variable, if you enter the name of an existing global variable, upon saving, a prompt will ask if you want to convert the global variable to a project variable.
  • Display names can now be specified for Connector Builder credentials
    When creating a connector with Connector Builder, you can now specify display names for credential fields. Connector creators are encouraged to provide display names that match the terminology used by the specific endpoint to help the user configuring that connector understand the field.
  • MongoDB Delete activities now provide the request schema
    MongoDB Delete activities now provide the request schema, whose fields can be used in a transformation mapping to specify a filter, a locale, or the writing of document IDs. Previously, these fields could be specified only within the activity configuration and could not be overridden in a transformation mapping.
  • User experience enhancements
    • Faster to find connectors and variables: A search box is now provided within the design component palette to help you find a specific connector or endpoint when designing a project, or to search for variables when configuring a script.
    • Easier to open projects and Connector Builder connectors: Project and connector names are now links within the project index and Connector Builder index, respectively.
  • Clearer to use autocomplete in the script editor: Text added in the script editor provides a tip to use Control+Space to access the existing autocomplete feature, and suggestions are now grouped and sorted appropriately.

Fixes

API Manager

  • Calculation of response times is now accurate
    Charts of API response times shown on the API Manager Analytics page now plot three sets of data: one for each of the average, minimum, and maximum values. As a result, the summary calculations displayed to the right of the chart are now accurate.

Cloud Studio

  • Schemas with XML anonymous types can now be uploaded
    When defining an XSD sample file schema that uses XML anonymous types (embedded within an XSD element), you are now able to successfully upload the schema. Previously, such schemas would either fail to upload or were uploaded but resulted in a generic error.
  • Default values are now displayed in transformations
    If an XSD or WSDL schema has an element or attribute with a specified default value, the value is now displayed next to the field name within the transformation.
  • Instance functions now work properly
    When using an instance function in a transformation mapping, such as FindByPos(), the hash symbol (#) indicating an instance is now automatically inserted in the correct position within the source field reference path.
  • Missing options for file-based endpoints are now available
    When configuring a Local Storage or Temporary Storage Write activity, you can now append files to a ZIP archive by using the Mode dropdown to select Append. In addition, when configuring an FTP Read activity, the Success/Error Folder options are now present. These options function the same as existing options available for other file-based endpoints.
  • Testing a connection is now successful
    When accessing a project in a Harmony organization other than your default organization, testing a connection for certain application-specific connectors is now successful. Previously, an error message indicating the connector was being downloaded across agents would be displayed.
  • Script autosave is now more graceful
    When configuring a script, cursor movement and selection of text no longer behaves unexpectedly while the script is autosaving.
  • Errors now occur less frequently
    Generic "Something unexpected happened" errors now occur less frequently. If you experience such an error, please provide the error ID when contacting Jitterbit support.
  • Transformations with invalid condition scripts can no longer be deployed
    When using a conditional mapping, if the script on the target node is invalid, the transformation will now be flagged as invalid and will not be deployable.
  • Connector Builder path parameters can no longer be made optional
    When creating a connector with Connector Builder, you can no longer erroneously set a path parameter as an optional field. Path parameters, if defined by the creator, are always required to be filled out by a user when configuring the connector, as they are used as part of the URL.
  • Epicor ERP connections can now be configured successfully
    When configuring an Epicor ERP connection, there are now two fields for entering server information. Previously, only one field was available and the application name was not being handled properly, leading to an inability to make a successful connection.
  • Epicor ERP integer and double values now work as expected
    Epicor ERP Post and Update activities using integer or double values that are not enclosed in double quotes are now successfully written to the record. Previously, the record would fail to be written, while reporting success with a warning related to an extra subelement.

Harmony portal

  • Switching between many Harmony orgs is now possible
    Users with access to 10 or more orgs can access those orgs using the dropdown in the Harmony portal header, now that a vertical scrollbar has been added. Previously, only those orgs near the top of the dropdown could be accessed.