What's New in Dell Boomi August, 2015

Dell Boomi Atom and Molecule upgraders and installers for Java 8 are available as of August 5, 2015.  We advise all partners and customers to upgrade existing atoms and molecules to Java 8. More information related to the Java upgrade is located in the Java Upgrade FAQ in the documentation.

Please take note of the remaining dates for our Java 8 upgrade and sunset of Java 6:

Java 8 Support

The Dell Boomi Test Atom Cloud and EU Atom Cloud have been upgraded to support Java 8. Additionally, Atom and Molecule upgraders and installers for Java 8 are available. The Cloud upgrader and installer for Java 8 will be available as part of the September release.

Adding Write Restrictions to Folders 

Administrators can limit users’ ability to change a folder and the components in it by adding write restrictions to the folder. Adding write restrictions to a folder allows a certain group of users to rename, move, delete and restore the folder and to create sub-folders in the folder. It also allows these users to create, edit, move, delete and restore components in the folder. Users without write access cannot perform these tasks on the folder or its components. They do, however, have read-only access to them. Write restrictions are based on user roles, which are set up and managed by the system administrator.

Try/Catch Shape

In the July 2015 release the Try/Catch shape was enhanced to allow you to catch process errors as well as document errors. The behavior is as follows:

• If there is one Try/Catch shape in a process and its Failure Trigger is set to Document Errors, then it catches only document-level errors. This is the default behavior.
• If there is one Try/Catch shape in a process and its Failure Trigger is set to All Errors, then it catches process and document-level errors.
• If a process contains one Try/Catch shape followed immediately by a second Try/Catch shape (i.e., Some Shape > Try/Catch Shape #1 > Try/Catch Shape #2 > Some Other Shape), it works differently. The outer Try/Catch shape (Try/Catch Shape #1) catches document and process errors, regardless of how its Failure Trigger is set. The inner Try/Catch shape (Try/Catch Shape #2) catches errors as indicated by its Failure Trigger setting.
• As of the August 2015 release, if a process contains two Try/Catch shapes that have other shapes between them (i.e., Some Shape > Try/Catch Shape #1 > Some Other Shape > Try/Catch Shape #2 > Some Other Shape), then each Try/Catch shape catches errors as indicated by its Failure Trigger setting. This is the corrected behavior. If your process works differently as of the August 2015 release and if you want to revert to the pre-August behavior, change the outer Try/Catch shape’s (Try/Catch Shape #1’s)Failure Trigger to All Errors.

Limiting Concurrent Executions on Atoms and Molecules

The ability to limit the number of concurrent executions running on a Molecule or Cloud with forked execution enabled was added in a previous release. Now you also can limit the number of concurrent executions that run on Atoms and on Molecules that do not use forked execution. You set these limits by setting the following properties on the Advanced tab in the Atom or Molecule’s Properties dialog.

• Maximum Simultaneous Executions per Node — Used to set the maximum number of simultaneous execution JVMs that can run on a given node. If this property is set, a queue is enabled for pending executions that exceed the maximum limit for running executions. Use the following two properties to set the queue size and time limit. If this property is not set, queuing is not enabled and the number of concurrent executions per node is unlimited.
• Maximum Queued Executions per Node — Used to set the maximum number of queued executions that can wait to run on a given node.
• Timeout for Queued Executions per Node — Used to set the amount of time (in milliseconds) that queued executions will wait to run on a given node before they are discarded.

Usability

The Atom Setup dialog dynamically filters between fields for local Atoms and Atoms in a Cloud.

Google Connector

OAuth 2.0, the token-based authorization framework designed to support REST APIs, is available within the Google Apps connection.

NetSuite Connector

The Requisition object, which was in beta in NetSuite and thus omitted from the 2015.1 NetSuite connector update, is now supported. Previously, the missing transaction type enumeration value had prevented queries from being built properly.

ServiceNow Connector

A new ServiceNow Connector enables you to move data into and out of the enterprise Service Management software.

Web Services Server Connector

The Web Services Server Connector supports CORS. CORS (Cross-Origin Resource Sharing) is a W3C protocol designed to enable removal of the same-origin restriction from various APIs so that resources can be shared among different origins — that is, servers. In the Shared Web Server Settings dialog, the new CORS Configuration tab lets you define rules for the handling of incoming CORS requests. The tab is present only if Web Service Type is set to ADVANCED on the Basic tab.

For more information, please see the August Release Notes in the AtomSphere reference guide.