10.1 Harmony Release Notes¶
10.1.1 Harmony Release¶
Harmony Portal Released May 15, 16, and 20, 2019¶
The 10.1.1 release date was by region:
APAC: Released May 15, 2019
EMEA: Released May 16, 2019
NA: Released May 20, 2019
Included in this release were updates to the Harmony Portal and its applications.
- New Smartsheet connector
A new Cloud Studio connector for Smartsheet is now available to use with agents version 10.1 or higher. The new connector can be accessed on the right side of the project designer from the design component palette.
- New option to test an email notification
When configuring an email notification, a new Test button is now available to confirm your configuration is working properly by sending a test email.
- New option to retry a failed operation
If an operation fails with an error related to file dependencies, this issue may be resolved by resyncing the project between the agent and Harmony. In this scenario, a new Try Again button appears within the operation log to resync and retry the operation. Note that a 10.1 agent or higher is required for the operation retry to work.
- Cloud Studio documentation link now works
After logging in to the Harmony Portal, the landing page Support & Learning link to Get Started Cloud Studio now directs you to the correct location for the Cloud Studio Quick Start Guide at Jitterbit Success Central. See all Cloud Studio docs under the Cloud Studio section.
- All Cloud Studio operations are now reflected on the Projects page
All operations that have been deployed within Cloud Studio are now displayed within the Management Console Projects page. Previously, Cloud Studio operations that had debug mode enabled were not appearing.
- Transformation export link now persists
After reopening an existing transformation without making changes, the link to export the mapping is now present. Previously, the export link was displayed only after making changes to the mapping.
- Reuse of file-based schemas from imported Cloud Studio projects now works
When defining a sample file schema in an activity or in a transformation, you can now successfully use a saved schema that was loaded from an imported Cloud Studio project. Previously, an error would occur upon selecting the saved file.
- Hyphens in JSON property names are now supported
New JSON schemas created by uploading a URL or file or by manually entering the schema, where the schema also uses hyphens in node or field names, no longer cause operations to fail at runtime. Note that existing schemas created this way are not affected by this fix; however, you can delete the existing schema and recreate it in the same project to resolve this issue.
- Jira connector: Post issues activity now works properly
When using the Jira connector with a Jira post issues activity to set issue priority, the request no longer results an an error and the priority is set correctly. This fix requires the use of an agent version 10.1 or higher.
10.1 Harmony Release¶
Harmony Portal, Design Studio, Private API Gateway, Private Agents, and Sandbox Cloud Agent Group Released May 1, 2, and 6, 2019¶
The 10.1 release date for the listed components was by region:
APAC: Released May 1, 2019
EMEA: Released May 2, 2019
NA: Released May 6, 2019
Included in this release were updates to these Harmony components:
- Harmony Portal and its applications
- Design Studio
- Private API Gateway
- Private Agents
- Sandbox Cloud Agent Group
Design Studio, Private Agent, and Private API Gateway installers are available as of May 6, 2019.
- New Cloud Studio connectors
New Cloud Studio connectors for Evernote, Google Drive, HubSpot, Magento, and SugarCRM 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.
- The Cloud Studio Cherwell connector no longer works with 10.0 agents
A change made to the Cherwell connector in Cloud Studio means it is no longer compatible with 10.0 agents. If using the Cherwell connector, please upgrade to 10.1 agents.
- Private API Gateway proxy API calls are now logged
Proxy API calls made through a Private API Gateway are now displayed within the API Logs page of the API Manager, as they are for custom API calls.
Private API Gateway¶
- Private API Gateway installation improvements
The Private API Gateway installer has been improved to allow for DNS configuration and self-testing to ensure that the gateway is functioning properly and is able to connect to the Harmony platform. In addition, you can now use the
--helpcommand to access a basic overview.
SendEmail()function now supports multi-byte characters
The Jitterbit Script function
SendEmail()in Cloud Studio or Design Studio can now be used to send emails containing multi-byte characters.
- APIs can now be tested without CORS being enabled
When accessing the Portal Manager or Portal pages of the API Manager, you can now execute custom APIs regardless of the CORS setting. Previously, execution required CORS to be enabled.
- Connector Builder can now be used with previously incompatible HTTPS endpoints
Connector Builder connectors used with certain HTTPS (SSL/TLS) endpoints no longer result in an error during testing of the connection or at operation runtime. Error reporting has been improved to better describe any errors.
- Connector Builder now respects Private Agent proxy settings
Connector Builder now uses any proxy settings that you have configured on a Private Agent, instead of executing on the agent without using the proxy.
- Deleted project components no longer remain after they have been deleted
Upon deleting project components in an already-deployed project and then redeploying the project, the deleted components are now permanently deleted. Previously, if you re-deployed a project where components such as operations, schedules, or applied plugins had been deleted, those components would remain in the deployed project.
- Configurable deploy now automatically selects all required components
When deploying any part of a project using a configurable deploy, all component dependencies are now automatically selected by default. Previously, only operations and their steps were automatically selected, without required components such as connections, files, or variables.
- Invalid Salesforce bulk operations are now prevented from being deployed
Attempting to deploy an invalid transformation containing both a Salesforce bulk activity and a transformation now results in an operation validation error. Mapping capabilities are provided directly within Salesforce bulk activity configuration in lieu of using a transformation.
- Reusing custom schemas in activities now works properly
When reusing an existing custom schema by selecting the saved schema from the activity configuration screen, the schema now works properly in a transformation. Previously, the operation would fail at runtime.