Past private agent releases

Introduction

This page provides a compilation of archived release notes for the private agent.

Archived private agent release notes

9.9

• EMEA: 07 March 2019

• NA: March 11, 2019

Enhancements

• LDAP passwords can be set and updated in Jitterbit Script using the LDAP functions.
• The maximum iterations for JavaScript loops can now be set in the jitterbit.conf file. In the [Settings] section, specify JavaScriptMaxIterations=_limit_ where _limit_ is the maximum number of iterations to be permitted.
• The Java distribution included in the Linux agent has been changed from the Oracle JRE to the AdoptOpenJDK JRE.
• The Java distribution included in the Windows agent has been changed from the Oracle JRE to the AdoptOpenJDK JRE.
• The PostgreSQL instance bundled in the Windows private agent installer has been upgraded to version 9.6.11.

Fixes

• Fixed an issue with the architecture of the third-party SAP JCo (Java Connector) library included in the Linux agent.
• Fixed an issue with the installation of the AdoptOpenJDK JRE by the Windows agent installer that prevented certain plugins from functioning.
• An issue with the Jitterbit global variable jitterbit.source.preserve_char_whitespace not being honored when transforming from CSV to JSON or from an Oracle Database to XML has been fixed. Setting jitterbit.source.preserve_char_whitespace=true means white space will be preserved and won't be trimmed from the beginning and end of strings in the source. The default value for this variable is "false", and white space will be trimmed from the beginning and end of strings in the source. This default value will be used if the variable has not been explicitly set. The default behavior is unchanged from prior releases.

9.8

• EMEA: 07 February 2019

• NA: February 11, 2019

9.7

• EMEA: 10 January 2019

• NA: January 14, 2019

Enhancements

• Boolean types are now supported for OData when using SQL Server, MySQL, or PostgreSQL.

• SAP fields defined as doubles now work correctly when used in OData APIs.

Fixes

• Fixed an issue with retrieval of the NetSuite custom segments to avoid timeout errors while generating or refreshing the schemas.
• Fixed an issue in the JMS Connector with messages that are missing a JMS destination header.

9.6

• EMEA: 12 December 2018

• NA: December 12, 2018

Fixes

• Fixed an issue with the parsing of IDoc types. It is now enabled by default and can be disabled in a private agent by setting the jitterbit.conf [TransformationEngine] section variable DefaultEntityResolution=false.

9.5

• EMEA: 08 November 2018

• NA: November 12, 2018

Fixes

• Resolved timeout issues when using JDBC to retrieve a large number of tables. Increased the defaultjitterbit.conf agent timeout values to match the messaging limits. Note: this affects fresh installs only.
• Fixed an Issue with the input parameter of the CVTDate() script function being set to an empty value. The CVTDate() function now successfully converts each input data value to the appropriate date and does not set any input to an empty value.
• Fixed an issue with retrieval of the NetSuite custom segments to avoid timeout errors while generating or refreshing the schemas.

9.4

• EMEA: 04 October 2018

• NA: October 8, 2018

New features

• Added support for reading and writing a NetSuite custom segment and its fields.

  Note

  Accessing NetSuite custom segments requires Design Studio version 9.4 or higher and private agents running version 9.4 or higher. Using the NetSuite Connector, create any operation to work with the appropriate object. The custom segment will display within the 'customFieldList' in the transformation. The value for the custom segment will be present in the target upon running the operation.

9.3

• EMEA: 06 September 2018

• NA: September 10, 2018

New features

• Added support for NetSuite conversion to TBA
  The authentication type of existing NetSuite endpoints can now be changed from single sign-on (SSO) to token-based authentication (TBA), allowing easy switching to TBA without requiring changes to the rest of your project. To configure, first enable TBA in NetSuite, then convert your NetSuite endpoint to use TBA. Design Studio 9.3.1 or higher and Agents 9.2 or higher are required to use this feature.
• Docker agent
  Jitterbit now supports a Jitterbit Linux OS agent that is packaged in a Docker Container. Following the Docker standard approach to container deployment, you can deploy and run the Linux agent anywhere that Docker runs. A new Docker agent version will be at the time a new version of the Jitterbit private agents is released. The Docker agent is public with available tags and instructions on installing found at https://hub.docker.com/r/jitterbit/agent.

Enhancements

• Added the SQL Server Microsoft JDBC Driver to the Jitterbit agent.
  The SQL Server Microsoft JDBC Driver is now included in the private agent (Windows, Linux) as an alternative way to connect to SQL Server. This fixes a known Date type bug in the jTDS Driver.

Fixes

• Fixed an issue that created logs referring to [axis] when shutting down a private agent.
  Added resource handling improvements to Tomcat server for axis web-app shutdown. Private agents now shut down properly without any logs referring to [axis].
• Fixed an issue where you were unable to create an SAP RFC function.
  SAP Remote Function Call now utilizes the user created functions.
• Fixed an issue where a field is missing on the actual SAP request, which causes the operation to fail.
  The Agent transformation engine now generates the required XML tag if the element in the schema has 0 occurrences and contains a fixed attribute.

9.2

• EMEA: 02 August 2018

• NA: August 6, 2018

Enhancements

• NetSuite has certified our NetSuite Connector on the NetSuite "Sandbox2.0"
  For additional information on your NetSuite account and "Sandbox2.0" please see https://system.na3.netsuite.com/app/help/helpcenter.nl?fid=section_4609939018.html&whence=.

• Improved running a scheduled operation within an agent group containing more than one agent.
  Improved efficiency for updating the started status for a scheduled operation.

• Added support in the NetSuite Connector for SerializedAssemblyItem and LotNumberedAssemblyItem while doing a search on AssemblyItem.
  The SerializedaAsemblyItem and LotNumberedAssemblyItem now display in the response transformation of NetSuite Searches activity performed on the AssemblyItem object.

Fixes

• Fixed an issue that caused a "Failed to get files" error when syncing files from a FileStore.
  Fixed an issue when the name of a file that is created on a Mac contains characters that are invalid on a Windows machine. This was causing an invalid file to be created on the Windows machine and the invalid file then cannot be used. This in turn caused an error that prevented the agent from running operations

9.1

• EMEA: 05 July 2018

• NA: July 9, 2018

New features

• Added support for OData indexof() function. This function is available specifically for SQL Server.
  Theindexof() Function is now supported for OData queries when coupled with a SQL Server database.

Fixes

• Fixed an issue that caused email messages to fail on Linux (RPM) agents after upgrading to versions 8.29.5 or 8.30.
  Removed a run-time dependency that caused a conflict with the third-party libraries. When running on Linux (RPM) agents, email messages are now sent and received successfully.

• Fixed an issue where$jitterbit.netsuite.async returns the wrong data when running concurrent NetSuite operations.
  The variable $jitterbit.netsuite.async returns the correct data when running concurrent NetSuite operations.

• Fixed an issue in which the 9.0 Agent was not handling API-based Archive operations properly.
  When an archive operation uses an API source and API target, it tells the Jitterbit engine that it should have a source and target file even though the source is not used. The process assumed that if the body should take the place of a source file, then the $jitterbit.api.request (plain text body) and $jitterbit.api.request.body.* (URL encoded body) variables would not be needed. This broke the archive operations that rely on the variables but ignore the source. The fix is to require the $jitterbit.api.request and $jitterbit.api.request.body.* variables are always populated, even if they are not needed.

• Stopping the Tomcat Service can intermittently leave the agent in an unstable state.
  Improved the Tomcat shutdown process so that the next restart is working properly, and the agent is stable.

• OData API queries would return an error indicating the URL is not valid when the queries contained the pound character (#).
  OData APIs now encode the pound character (#) correctly.

• OData DateTime parameter was not working with "T" in the DateTime timestamp.
  The OData DateTime timestamp now converts properly to a standard datetime when utilizing an OData Entity.

• Issue with SQL Server database Date type not being recognized correctly as a Date type with the default SQL Server driver.
  Date datatype is now supported when utilizing an OData Entity with a SQL Server database.

• Global variables were not being passed to JavaScript in 'On Success' and 'On Failure' operations.
  Jitterbit Global Variables are now passed successfully to JavaScript in 'On Success' and 'On Failure' operations.

• NetSuite objects TransferOrder and InventoryTransfer are not available in NetSuite Search.
  Added support for performing NetSuite Search on the TransferOrder and InventoryTansfer objects only when using private agents.

9.0

• EMEA: 17 May 2018

• NA: May 20, 2018

Enhancements

• Added the ability to log 504 timed out API operations.
  API requests that result in a 504 timeout error message can now be tracked to see the actual result of the underlying operation, along with log information.

• Added the ability to detect target types from the structure of the operation.
  The agent will now automatically set the 'Content-Type' header for custom APIs that use JSON or XML response structures.

• Added an operation monitor to log and correct the status of non-running operations.
  The Agent now has built-in operation monitoring that will correct the status of an operation in certain scenarios.

Fixes

• Fixed an exception error from the agent when the proxy credentials include the '%' character.
  The Agent will not generate an error when using the '%', '&' or '=' characters in proxy credentials.

• Fixed operation chaining to continue when the DEBUG folder is not copied correctly.
  The operation chain will now continue on through the 'On Success' processing even when the DEBUG folder is not copied correctly.

8.30

• EMEA: 12 April 2018

• NA: April 12, 2018

New features

• Implemented the ability to perform lookup within JMS Queue.
  JMS Connector now supports JNDI context lookup for JMS destinations when using Poll, Browse and Publish activities.
• Added the option to write an FTP source file to a separate archive folder after processing.
  Added 'Use Success Folder' and 'Use Error Folder' under Options for an FTP source file. Configure an FTP source file to be archived in a separate "success" folder after successful processing to the primary target destination(s) or to a separate "error" folder if not successful.
• Added the option to write a local file target to a separate archive folder after processing.
  Added 'Use Success Folder' and 'Use Error Folder' under Options for a local file target. Configure a local file target to be archived in a separate "success" folder after successful processing to the primary target destination(s) or to a separate "error" folder if not successful.
• Added the option to write a local file source to a separate archive folder after processing.
  Added 'Use Success Folder' and 'Use Error Folder' under Options for a local file source. Configure a local file source to be archived in a separate "success" folder after successful processing to the primary target destination(s) or to a separate "error" folder if not successful.
• QuickBooks: OAuth 2.0 is now supported.
  The Design Studio QuickBooks connector has been updated to support OAuth 2.0 authentication while remaining backward compatible with OAuth 1.0. QuickBooks OAuth 2.0 authentication is only supported using private agents.
• SAP S4 HANA Connector is now available in Design Studio.
  The SAP S4 HANA Connector is now accessible from Design Studio. You can find the SAP S4 HANA (on-premises) Connector in the Connector tree. The SAP S4 HANA connector is only supported using private agents.

Fixes

• Fixed the issue where the run time JSON is not parsing properly.
  When creating a JSON transformation that contains nested arrays, the JSON now processes properly.
• Fixed an issue on Linux where the Drain/Stop feature was not waiting for Log Sync before shutting down.
  Updated Drain/Stop features so that the status shows correctly and the agents shutdown properly. When doing a drain stop, operations will now complete before the agent turns off. This fix will allow an agent to properly synchronize all operation instances with the Harmony Cloud.
• Fixed a critical error during temporary directory creation.
  Certain temporary directories and files will now be removed after each operation successfully completes.
• Fixed an issue causing debug statements to fill up logs.
  Removed a dependency so that the debug statements are working correctly, and excessive logging does not occur.
• Fixed an issue where an FTP archive target was not copied to the error folder path when using a Linux agent
  When the 'Use Error Folder' option has been set up in an FTP target, the archive file is now successfully created in the error folder path when an archive operation fails to run successfully on a Linux agent.
• Fixed an issue that was allowing archived files to be overwritten.
  When the 'Use Success Folder' or 'Use Error Folder' option are set up, the success or error archive files are now successfully written to a success folder when the operation is successful or to an error folder when the operation fails. The file names are written with an additional "_x" string appended to them sequentially to prevent overwriting previous files.

8.29

• EMEA: 22 February 2018

• NA: February 22, 2018

Enhancements

• Linux installation has been upgraded to support Ubuntu 16.04
  Linux private agent now supports Ubuntu 14.04 and Ubuntu 16.04. Ubuntu 12.04 is no longer supported.
• Security enhancements: Multiple upgrades
  Multiple updates have been made to improve stability and security of the system.
• Added a new notification email type when a new private agent version is available.
  A new Notification Type, Agent Available, has been added to the WMC Notifications page. The Agent Available notification may be set up to automatically send an email to a specified email address at the time a new private agent version is released.

Fixes

• Fixed an issue with theDateAdd() function where adding 12 months to any December date returned the incorrect year.
  Using the DateAdd() function to add 12 months to any December date now returns the correct date; returning a date exactly 1 year from the original date.

• Fixed an issue that causes a dictionary or array to become corrupt when the variable name contains a period and a JavaScript is run.
  When using JavaScript within Jitterbit, JavaScript will no longer process variables that contain a period when the variables are dictionaries or arrays.

• Fixed an error when running a SQL statement on a PostgreSQL database with an OID higher than int allows.
  A SQL statement will run successfully on a PostgreSQL database when an OID is higher than the integer data type allows.

8.28

No changes applicable to private agents.

8.27

• NA: December 14, 2017

Enhancements

• Additional special characters are now allowed in the username and password for the private agent's proxy.
  Additional special characters ("/", "%" or "&") are now allowed when configuring the username and password for the private agent's proxy.

Fixes

• Fixed an error that occurred when upgrading a Linux agent to version 8.26.
  The Linux build environment has been re-enabled to support backwards compatibility of up to minus one version from Centos release version 6.

8.26.1

• NA: September, 15 2017

Fixes

• A popup message will display during installation of the agent if the previously installed version of PostgreSQL is lower than 9.3.
  When upgrading from an older version of Harmony, and skipping multiple versions to upgrade to the current version, the agent upgrade installation will not complete if the installed version of PostgreSQL is lower than 9.3. A popup message will now be presented to the user advising to upgrade the PostgreSQL version to 9.3 first and then install the upgrade for Agent.

8.26.1

• NA: September, 15 2017

Fixes

• A popup message will display during installation of the agent if the previously installed version of PostgreSQL is lower than 9.3.
  When upgrading from an older version of Harmony, and skipping multiple versions to upgrade to the current version, the agent upgrade installation will not complete if the installed version of PostgreSQL is lower than 9.3. A popup message will now be presented to the user advising to upgrade the PostgreSQL version to 9.3 first and then install the upgrade for Agent.

8.25.1

No changes applicable to private agents.

8.25.0

No changes applicable to private agents.

8.24.2

• NA: June 19, 2017

New features

• Support for JavaScript
  When creating a script as an operation step, you can now use either JavaScript or Jitterbit Script language. The new JavaScript feature in Studio version 8.24.2 is compatible with Agent versions 8.24.0 or higher. Learn more in our JavaScript documentation.

8.24.1

• NA: June 12, 2017

Fixes

• Scripting: Issue with returned values fixed
  We have identified an issue with our latest release that impacts customers who have implemented RunScript calls where the return value is the result of a function call.

  When the return value in the script is a function call, the script returns a blank value. RunScript calls that return results from variables are not impacted.

  This incorrectly returns a blank value:

  num = 3.14;
  RoundToInt(num);
  

  This returns the expected value:

  num = 3.14;
  num = RoundToInt(num);
  num;
  

  This issue has been corrected in 8.24.1 private agent downloads. If you are running private agents and have not upgraded to version 8.24.0, you are not impacted.

  In order to resolve this issue, a different 8.24.0 fix related to the data type returned by the RunScript() function has been rolled back. For more information on the fix that was rolled back, see Fixes under 8.24.0 below.

8.24.0

• NA: June 9, 2017

Fixes

• Scripting: RunScript issues fixed related to data type, memory
  When using the RunScript() function, the value returned can now be a complex data type, such as dictionary or array. In addition, an issue has been fixed that previously resulted in an error related to memory.

  Note

  The portion of this fix related to data type returned by the RunScript() function was originally with 8.24.0, but has since been rolled back as part of 8.24.1.

8.23.2

No changes applicable to private agents.

8.23.0

• NA: May 26, 2017

Fixes

• Install experience improved for those already running PgBouncer
  When installing a private agent, Jitterbit will now automatically detect the port of an existing PgBouncer installation and re-register the service using another port. The PgBouncer application was integrated into the agent install package as of version 8.22, and this fix provides a more seamless experience for users that already have the connection pooling application in use.

8.22.4

No changes applicable to private agents.

8.22.3

No changes applicable to private agents.

8.22.2

No changes applicable to private agents.

8.22.1

No changes applicable to private agents.

8.22.0

• NA: March 17, 2017

Enhancements

• Improved performance with integrated PgBouncer installation
  PgBouncer, a connection pooling application for PostgreSQL, has been integrated into the agent install package. If you already have an existing installation of PgBouncer and experience issues upgrading, please contact support.

Fixes

• Private agent: Shutdown port for Tomcat services changed to avoid conflicts
  The default shutdown port used by Jitterbit for Tomcat services has been changed so that it does not conflict with other applications that use Tomcat services configured with the same original default shutdown port.

8.21.0

No changes applicable to private agents.

8.20.0

• NA: January 27, 2017

Enhancement

• 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.
• Security enhancement: Library upgrades
  The FasterXML / Jackson JSON and Commons Codec libraries were upgraded. These upgrades improve the security of the system.

Fixes

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

8.19.0

• NA: January 6, 2017

New feature

• MS Dynamics CRM: Support for 'listmember' object
  The MS Dynamics CRM connector now provides support for the 'listmember' object during an MS CRM Create operation.

Fixes

• Salesforce: Functionality restored for Salesforce bulk query operations
  The previous 8.18.0 release created an issue causing Salesforce some bulk queries not to operate. This fix restores that functionality.
• NetSuite: Compatibility error resolved for imported NetSuite 2016.2 projects
  The previous 8.18.0 release created an issue resulting in a version compatibility error when importing a NetSuite 2016.2 project that had been created prior to version 8.18.0. This issue is now resolved.
• NetSuite: Support for asynchronous NetSuite search operations
  The NetSuite asynchronous function for bulk processing now works properly for NetSuite search operations. The asynchronous option for NetSuite search, as well as for other NetSuite operations, can be enabled by setting $jitterbit.netsuite.async=true.
• Clarizen: Querying multiple fields
  When performing a query using the Clarizen Connector, you can now select multiple fields. Previously, only one field at a time could be queried successfully.

Security Enhancement

• Library upgrade
  The Apache Commons BeanUtils library was upgraded, which improves security of the system.

8.18.10

No changes applicable to private agents.

8.18.0

• NA: November 3, 2016

New features

• Option to add new configuration settings remotely
  You can now add new configuration settings in the Jitterbit config file remotely via the Web Management Console (WMC). This feature allows you to override default private agent settings, even if the particular setting was not previously set in the agent configuration. To do this, first make sure you have remote Agent configuration enabled (Organizations > Actions > Organization Policies). Then go to the Jitterbit config file (Agent Groups > Actions > Jitterbit Config), where you will see a new Add button next to Edit. Here you can specify the new parameter and value, whether the parameter should be enabled, and the existing section to which the setting will be added.
• Scripting for Agent version name and ID, current project name
  You can now access the agent version name and version ID using new script functions: GetAgentVersionName(), GetAgentVersionId(). These are consistent with the existing functions GetAgentName() and GetAgentId(). You can also now use the current project name in scripts by using $jitterbit.operation.project_name. This is a new system variable that holds the current project name when the operation is running.
• Improved support for XML \<any> element
  You can now use the XML \<any> element in an XML schema, including when defined as the middle sibling in an XML schema.

Improvements

• Notification of manual configuration changes
  If you have enabled remote Agent configuration and the Jitterbit config file becomes modified manually outside WMC, you will now see a warning icon and message icon displayed on the agents and Agent Groups pages of the WMC. Clicking the message icon will open a popup with a detailed description of the warning. Note that manual changes to the config file will always override your existing configuration.
• Creating new file share directories (Linux)
  For those using a private agent on Linux, you can now specify target file share paths that do not yet exist. That is, the Linux agent will no longer produce an error if the directory does not yet exist, and instead will create new file share directories as specified.
• Option to disable logging for Hosted HTTP Endpoints
  You now have the ability to disable operation logging for Hosted HTTP Endpoints, which allows for greater efficiency and throughput under load. To do this, edit the Jitterbit config file under the [HttpEndpoints] section to set EnableLogging = false.

Fixes

• Carriage returns and special character supported (OData API)
  For those using OData API, fields containing multiple carriage returns or certain special characters are now supported. These fields in OData results will no longer be truncated.
• GetUTCFormattedDataTime returns correct time
  The GetUTCFormattedDateTime function now returns the correct time for all standard U.S. timezones (PST, MST, CST, EST). Previously, the CST and PST timezones were returning results an hour off during Daylight Saving Time.

Security enhancement

• OpenSSL and Apache Tomcat upgrades
  The Apache Tomcat version was upgraded, which improves performance and security. The OpenSSL library was upgraded. This addresses all known OpenSSL vulnerabilities and improves the security of SSL connections made by the agent.

8.17.0

• NA: September 23, 2016

New feature

• Control over whitespace
  Whitespace for values within an XML source can now be preserved during the transformation to a target by setting "$jitterbit.source.xml.trim = false".

Improvements

• Support for null characters
  Support for null characters has been added to UTF-16 and UTF-32 character encoding sets for text sources and targets.
• Standardized character encoding (Salesforce)
  The character encoding behavior for Salesforce bulk operations now works the same way as for Salesforce operations, with operation responses being UTF-8 encoded regardless of the character encoding type of the source.

Fix

• Option to ignore lines
  The option to ignore a set number of first or last lines now works properly for UTF-16 (LE and BE) encoded text files. This option is specified during the setup of a source or target.

Security enhancement

• Library upgrade
  The async-http-client library has been upgraded. This improves the security of asynchronous HTTP connections made by the agent.

8.16.0

• NA: September 10, 2016

New features

• You can now use Jitterbit global variables as sources and targets. The new type of source and target allow users to read and write directly from/to global variables in their operations, bypassing any extra workarounds, such as temporary or local storage.

• Added support for the Salesforce Summer '16 release (aka SFDC API v37).

Improvements

• The agent can now preserve white-space characters in a JSON transformation. Set $jitterbit.source.json.trim = false to enable this behavior.

• Enhanced user experience when using the SortArray method through improving documentation and error handling.

• Improved Agent reconnect logic to help Agent recover quicker when experiencing network problems.

• Added a Knowledge Base link to the Error Message that pops up when NetSuite requires the use of Application ID.

• NetSuite Connector now shows the custom field for CustomerDeposit object.

• Vendor Return Authorization has been configured in NetSuite search.

• In the NetSuite search object, one can now filter by "Vendor Return Authorization".

• NetSuite is now capable of retries to Cloud API calls.

Fix

• Salesforce timestamp function now reflects the accurate timestamp results between UTC 12:00 and UTC 13:00.

Security enhancements

• Bouncy Castle upgraded. Improves security by forcing Key Fingerprint usage in its cryptography algorithms.

• XercesImpl library upgraded. This improves the security of the overall system.

• PDFbox upgraded. This increases the security when processing PDF documents.