Harmony Release Notes – January 27, 2017
Log in to the Harmony Portal to access the latest version of the API Manager, Management Console, and Citizen Integrator or to download the latest version of Design Studio and Private Agents. For support, visit Getting Support.
- New feature: "Conditions" provide a simple, visual way to create conditional operations
Many operations depend on the result of a previous operation (i.e. "If this... Then that"). Advanced users typically set this up via Scripting. But now it's much easier for anyone to arrange basic logic using Conditions! Conditions use the value of a project variable after the operation ends to trigger a corresponding operation or action. In Studio, right-click on any insertion point (yellow dot) on your operation and choose Insert > Condition. Then double-click on your new Condition to set it up.
- New feature (NetSuite): New "GetList" feature simplifies searching by ID
The new GetList activity available under the NetSuite Connector in Studio allows you to query records by internal or external ID. This simplifies searching for NetSuite objects by ID or list of IDs.
- New feature (NetSuite): Function to retrieve session ID for non-connector calls
A new function, NetSuiteLogin(), retrieves a new sessionID from a NetSuite endpoint for use in REST or SOAP calls that are not built into the NetSuite Connector. This provides a simple way to log in to NetSuite without requiring authentication headers for each web service call. The new function is available in Studio under Scripts > Functions > Connector Functions > NetSuiteLogin.
- New feature: GZip support for HTTP sources and targets
For new and existing HTTP sources and targets, by default Jitterbit now requests servers to provide HTTP responses in GZip format. In return, Jitterbit will follow the RFC 1952 standard and automatically decompress GZip HTTP responses. If the server does not use GZip, Jitterbit will see that the response is not compressed and handle as usual. You can toggle the GZip option from the HTTP source or HTTP target configuration screen in Studio under Advanced Properties.
- Fix: HTTP sources and targets now report operation failures properly
When HTTP sources or targets fail, the status code, headers, and response are now saved appropriately. A failed HTTP target will write the response to the target selected on the HTTP target screen in Studio. A failed HTTP source will write the response to the new variable: $jitterbit.source.http.response. This functionality pertains to both HTTP operations and the ReadFile/WriteFile script functions.
- Fix: User interface fixes on Projects and Activities pages (Harmony website)
Display of data within the Projects page of the Web Management Console (WMC) has been fixed so that data is visible and sortable where appropriate. In addition, issues with scrolling and duplicate records on the Activities page have been resolved.
- Improvement: Milliseconds in DateTime fields are now retained
Millisecond components of DateTime fields are no longer truncated when performing date and time script functions, database transformations, and database lookup functions. You can include milliseconds by adding "SSS" to your function in the standard format string, for example yyyy-mm-dd HH:MM:SS.SSS.
- Fix: Local JSON files can again be used for sample XSD structure
When using JSON as the source for a new transformation, you are now able to successfully use a local copy of a JSON file as the sample file for an XSD structure.
- Fix: JDBC database without records no longer produces an error
When using chunking (in Studio under Operation Options) with a JDBC database source, an operation error will no longer occur if no rows are returned from the database. Instead, the operation will complete successfully and the log message will indicate that no database rows are available, which is the same behavior as when not using chunking.
- Fix: Special characters now work properly with custom OData APIs
When using your own OData API, characters in the URL are now fully decoded and are processed as intended. Previously, SQL queries were only partially decoded, causing issues when some special characters were used.
- Fix: CallStoredProcedure issue with non-alphanumeric characters resolved
The CallStoredProcedure function available for JDBC no longer produces an error when output parameters contain certain non-alphanumeric characters.
- Security enhancement: Library upgrades
The FasterXML / Jackson JSON library was upgraded from version 2.6.1 to 2.8.5. The Commons Codec library was upgraded to version 1.10. These upgrades improve the security of the system.
- New feature (Clarizen): Option to test query now available
For those using the Clarizen Connector, the option to test a query while configuring a Clarizen Query Activity is now available by clicking the Test Query button. Upon clicking the button, a message will indicate whether the query is valid.
- Improvement (Autodesk): Autodesk PLM 360 updated to Autodesk Fusion Lifecycle
With the launch of Autodesk Fusion Lifecycle, the branding of the Autodesk PLM 360 Connector in Studio has been updated to now reflect the new name and branding of Autodesk Fusion Lifecycle.