10.3 Harmony Release
Harmony Portal, Design Studio, Private API Gateway, Private Agents, and Sandbox Cloud Agent Group
Released June 26, July 8, and July 10, 2019
The 10.3 release date is by region:
- APAC: Released June 26, 2019
- EMEA: Released July 8, 2019
- NA: Released July 10, 2019
Included in this release are 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 July 10, 2019.
- New option to export proxy APIs
After configuring a proxy API, you can now export it as an APK file in the same way you can already export APIs. Importing a proxy API from the API Creation and Configuration page is also supported.
- New option to enable verbose logging
When configuring an API or proxy API, you now have the option to enable verbose logging, which will include request and response data in the API log. This option can be used to monitor incoming/outgoing data or to debug API issues.
- Derived types and substitution groups are now supported
User-provided and server-based schemas that contain derived types or substitution groups are now supported. When using the schema in a transformation, a link to select the types or group appears next to the node name.
- New API SOAP activities support using WSDL schemas
Two new API activities are available to configure by uploading a WSDL schema: API SOAP request and response. These enable support for Salesforce outbound messaging.
- Control over exporting/importing environment-level components
When exporting a project, you can now choose to exclude success/failure emails, project variable values, credentials, or schedules. When importing a project, if the project contains success/failure emails or schedules, you have a choice whether to include them in the import.
Private API Gateway
- Transport Layer Security (TLS) 1.0 is now disabled
Use of the cryptographic protocol TLS 1.0 is no longer supported by the Private API Gateway. For concerns or to change this default setting, contact Jitterbit Support.
- Design Studio Siebel queries now support Business Component dynamic activation
You can now use the Design Studio Siebel Connector with a Private Agent version 10.3 or higher to fetch data from an inactive Business Component field. To do so, a new field called
ActiveBCFieldis now included in the query request schema, which you can use to pass the Business Component field names that need to be active.
- More control over filtering APIs, analytics, and logs
You can now select more than one option in the dropdown filters on the API Manager API Creation and Configuration, Analytics, and API Logs pages, allowing you to filter by any combination of environments, profiles, statuses, types, APIs, profiles, status codes, or versions, as applicable.
- Proxy API UI improvements
During configuration of a proxy API, a new tooltip explains how to use the document editor, a new checkbox allows you to select all services and methods from a YAML file at once, new text indicates if you haven't created any security profiles, and you can now select an existing service or header to make changes to it.
Design Studio and Cloud Studio
- Salesforce API version 45 is now supported
The Salesforce connectors in Design Studio and Cloud Studio now use Salesforce API version 45. When opening an existing Design Studio project using this connector, you will be prompted to upgrade to this version. Existing Cloud Studio Salesforce endpoints use the new API version automatically.
- Installation on Windows no longer fails
When installing a Windows Private Agent, installation on a machine that already has a version of Visual C++ Redistributable for Visual Studio higher than 2015 is now successful.
- Escaping characters in pipe-delimited schemas now works
When configuring a pipe-delimited custom schema in Cloud Studio or Design Studio, the option to convert escape sequences now works as expected. Previously, using this option with such a schema would cause the operation to fail.
- An erroneous error no longer appears when testing a Cloud Studio connection
When testing a connection's configuration in Cloud Studio using the Test button, you will no longer see an erroneous error message indicating the connector is being downloaded across agents when the connection was actually successful.
- Cloud Studio connectors now work on Ubuntu Private Agents
You can now use certain application-specific Cloud Studio connectors with Ubuntu-based Linux Private Agents. Previously, when testing a connection's configuration using the Test button, an erroneous error message indicating the connector was being downloaded across agents would be displayed indefinitely.
- Reverse proxy server IP whitelisting is now supported
If you're using a reverse proxy server in front of your Jitterbit APIs, you can now use IP whitelisting within the API Manager Security Profiles page. If there are multiple IP addresses in the
X-Forwarded-Forheader, the last IP address is used by default. Those using a Private API Gateway can change the default IP address used in the configuration file.
- Portal Manager now supports a large number of APIs
When initializing the Portal Manager, you can now load a larger number of API definitions (more than 100). Previously, an error would be displayed related to item size exceeding maximum allowed size.
- A message now indicates that OData API export isn't supported
When attempting to export an OData API, you will now receive a message that exporting an OData API isn't supported. Previously, an APK file would be generated, but wouldn't work upon importing the file.
- List of security profiles now refreshes properly
After adding or deleting a security profile, the Security Profiles page now refreshes properly to show the current profiles.
- API logs now populate in orgs with a large number of environments
When viewing API logs within an organization that has hundreds of environments, such as the Jitterbit University training organization, you will no longer receive an unknown exception error, which occurred in some situations depending on your permissions within those environments.
- Proxy API YAML file is no longer unintentionally removed
After providing a YAML file during step 2 of a proxy API configuration, if you advance to step 3 and then return to step 2, the Provide OpenAPI Document selection will no longer automatically change from Yes to No and remove the YAML file.
- Connector Builder schemas are now validated when uploaded
When creating a new connector with Connector Builder, schemas that you upload from a file or URL to use as the request or response for the connector's activities are now automatically checked to make sure they are valid. Previously, invalid schemas could be uploaded, leading to an error for the end user when trying to use those activities.
- Operation options are now limited to applicable options
The operation options that are available to configure now depend on the type and order of activities used in an operation. Previously, some operation options shown in the UI weren't functional for certain operations.
- Schema URLs with multiple periods can now be uploaded
When defining a sample file schema by uploading a URL or by manually entering a schema into the text area, schemas that contain periods within the filename (other than those within the URL path or before the file extension) can now be uploaded successfully. Previously, such schemas would fail to upload with either a "TypeError" or a generic error message.
FindByPos()function now saves properly with other functions
When using the
FindByPos()function and any other function in the same transformation script, an additional hash symbol (#) is no longer erroneously added within the script upon saving, in addition to the one indicating an instance within the source field reference path.
- Loading indicator no longer prevents user interaction
You can now continue to interact with certain configuration screens, such as those for activities and transformations, while loading resources. A visual indication of loading is now shown below the Harmony Portal header instead of affecting the entire page.
- Testing scripts that reference activities with project variables now works
When testing a script that uses a file-based activity as an argument to a Jitterbit function, if the activity being referenced uses any project variables, you are now able to successfully test the script. Previously, the test would fail, although there was no issue at operation runtime.
- Transformation preview for hierarchical schemas again works
When previewing a transformation using a hierarchical schema, sample data values are again shown on the target side of the transformation. As of version 10.1, the sample data wouldn't show up in the UI, although there was no issue at operation runtime.
- Link to view API logs now goes to API Manager logs
When using the link within the operation log to view all API requests, you are now directed to the API Manager API Logs page instead of the deprecated View Debug Logs page.
- Environments and connectors are again displayed
The lists of environments and connectors now populate in Design Studio, as expected, after uploading a profile photo in the Harmony Portal. Previously, the environments dropdown was empty and there were no connectors displayed in the project items list, with an error related to the "profilePic."
- Number of failed operations is now reported correctly
The statistics on the Harmony Portal landing page now report the correct number of failed operations within the past 7 days (based on local time), as indicated within the UI. Previously, this number included all failed operations, not just those within the listed timeframe.
- Selected organization when switching apps now works as expected
When navigating between applications within the Harmony Portal, the selected organization will no longer change unexpectedly. In addition, when intentionally switching to another org that doesn't have access to the active application, the active org will be successfully changed when you are returned to the Harmony Portal landing page.
- Loading indicator no longer prevents user interaction
You can now continue to interact with Harmony Portal pages while loading resources, with a visual indication of loading shown below the Harmony Portal header. Previously, some screens would be grayed out until loading had finished before you could perform further action.
- Invalid Harmony Portal links now redirect to the landing page
When accessing a Harmony Portal link appended with a previous URL to use as a redirect, after logging in, if the page cannot be found, you will now be redirected to the Harmony Portal landing page instead of an error page within the Management Console.
- Agent Windows OS is now populated correctly
For Windows Private Agents, the OS name is now populated on the Management Console Agents page in cases where it was previously reported as "unknown."
Last updated: Jul 16, 2019
- No labels