These release notes identify the new features and bug fixes released in AtomSphere for June 2020.

Subject to the terms and conditions of our existing contract with your firm, and liability provisions and limits therein, we confirm that Boomi has successfully passed all applicable test cases associated with the updates identified in this product release.

Release notes for the 12 months preceding the current release are archived.

AtomSphere platform

Switching accounts


  • Immediately after signing in to the platform, users of SSO accounts could not switch accounts. With this fix, SSO account users can switch accounts after signing in. (UNI-474)

Atoms, Molecules, and Atom Clouds

Atom Cloud properties

  • When a cluster’s head node aborted unexpectedly, the cluster did not select a new head node, and additional nodes logged warning messages until a manual restart was performed to correct the issue. With this fix, the new Cloud property Timeout for Escalating Cluster Issue is added to enable you to set the number of milliseconds before this issue is automatically escalated to a severe status, which results in an automatic restart or shutdown of the node to resolve it. (BOOMI-35882)

    For more information, see the topics Properties panel, Advanced tab and Cluster monitoring for Molecules and Atom Clouds.

Atom Workers panel

  • In some cases, an internal error caused aborted Atom workers to fail to show in the list of inactive workers. With this fix, aborted Atom workers display in the Inactive view, as expected. (RUN-552)

Cluster Status panel

  • After restoring a deleted Atom Cloud, the Cluster Status panel did not appear in Atom Management as expected. With this fix, the Cluster Status panel is again available in Atom Management after an Atom Cloud is restored. (RUN-594)

Docker images


Process execution

  • In some cases, a temporary network interruption prevented suspended accounts from being properly updated to an unsuspended state, which resulted in an error. With this fix, Molecule and Atom Cloud nodes correctly report that an account is unsuspended. (RUN-295)

Boomi Integration

Audit logs


Find Changes shape

  • An error message now displays when the Find Changes shape contains an invalid key column. The message includes directions for correcting the invalid key. Additionally, the offending key column is highlighted in the Key Columns list for easy identification. (INT-2183)

    To learn more about this feature, see the topic Find Changes shape.

  • Processes that contained the Find Changes shape behaved inconsistently during executions. With this fix, the Find Changes shape no longer causes inconsistencies during process executions. (INT-999)

Map Scripting component

  • The order of script component variables designated in a Map Scripting component was not persisted throughout the Map component or during script execution. With this fix, users have the option to click the preserve script variables link in the Map Scripting component to persist the order of values throughout maps and during script execution. (INT-419)

    For more information, see the topic Creating a Map Scripting component.

Process executions

  • When a process contained both a Process Route component and a subprocess, and the subprocess failed during process execution, the error message did not provide adequate context. With this fix, a more detailed message is provided when an execution of this kind fails. (INT-1977)

Process extensions

  • It was not possible to add default values to the destination profile for data map extensions. With this fix, non-editable fields for adding default values to a destination profile are removed from the Data Map tab in the Extensions dialog. (INT-1145)

Process Reporting

  • When executions on a node were aborted as a result of the deletion of that node, Process Reporting continued showing them as in progress. The correct "Aborted due to Atom Stop" message was only reported if the node was brought back online or removed. With this fix, executions are correctly reported as aborted after a node is deleted. (RUN-636)

Single sign-on (SSO)

  • Administrators of SSO-enabled accounts now receive improved instructions via email for unlocking SSO users from the User Management page. Previously, the instructions included the steps only for unlocking non-SSO users. (ADSEC-672)

  • Administrators of SSO-enabled accounts are notified via email when an SSO user is locked from the AtomSphere platform due to too many invalid API Token entries. (ADSEC-673)

  • The capability to unlock SSO users from the User Management page introduced in the May 2020 release did not enable unlocking of users of both SSO and non-SSO accounts, and users who once used a now-deleted training account. With this fix, the unlock feature works as expected for all SSO users. (ADSEC-746)

    For more information, see the topics Single sign-on and Unlocking a user with single sign-on access.

User management

  • When an account administrator erroneously included trailing spaces in a new user’s email address, an error message was shown even after the administrator removed the trailing spaces. With this fix, an error message is not shown once the trailing spaces are removed. (ADSEC-727)

AtomSphere API and Partner API

Account Cloud Attachment Quota object

  • The new Account Cloud Attachment Quota object enables Atom Cloud owners to programmatically retrieve, add, update, and delete attachment quotas. An attachment quota specifies the number of Atoms that can be attached to a given account’s Atom Cloud. (RUN-372)

    To learn more about this feature, see the topic Account Cloud Attachment Quota object.

EDI connector record objects


  • Connector record object queries did not return connector records for executions of processes in which multiple-standard “My Company” trading partners were used in the Start shape or Trading Partner shape. With this fix, queries return the expected results for executions of this kind. (B2B-837)

  • Connector record object queries did not return connector records with custom fields when results in JSON format were requested. With this fix, connector records with custom fields are included in the results regardless of the requested result format. (B2B-964)

  • Connector record query operations occasionally returned inconsistent results from one request to the next for executions with 100 or more processed documents. With this fix, the returned results from one request to the next are reliably consistent with Boomi Integration Process Reporting. (B2B-996)

Environment Extensions object

  • PGP extension values were erroneously deleted when the object was used to update other extension values. With this fix, PGP extension values are correctly updated in the object. (INT-1984)

Trading Partner Component object


  • When a certificate component ID for AS2 communication was specified in a Create or Update request, that ID was erroneously applied to all three AS2 certificate fields in the object. With this fix, the certificate component ID is applied only to the field specified in the request. (B2B-502)


AtomSphere API and AtomSphere Partner API connectors

  • When importing objects, there was no indication that objects were deprecated from the platform. With this fix, the connectors identify deprecated objects. (INT-2082)

Google Ad Manager connector


  • To align with the most current list of object types, the connector is updated to support the latest version of the Google Ad Manager API, v202002. (CON-1311)

    These new Google Ad Manager v202002 object types and supporting operations are available:

    • AdSpot — Create, Update
    • BreakTemplate — Create, Update, Query
    • CreativeReview — Execute, Query
    • SamSession — Execute, Query
  • Other services and objects types are removed in v202002, resulting in those object types not being selectable in Boomi Integration when browsing (Import Wizard). See the Google Ad Manager API Release Notes for more information.

    To learn more about this feature, see the topic Google Ad Manager connector.

Listen connectors


  • When restarting listeners, the Atom restarts them in two phases. First, it restarts the “non-blocking” listeners; or those such as the Web Services Server listener that do not have to connect to an external service to restart. These “non-blocking” listeners have minimal startup time and do not prevent other listeners from restarting. Next, the Atom attempts to restart the “blocking” listeners; or those such as the JMS listener that need to connect to a service. For these, if the listener cannot restart for some reason (for example, the connection with the JMS server is lost), the listener cannot be used and it prevents others from restarting. Any listener that needs to establish a connection with a service should be considered a potentially “blocking” listener, but were not treated that way.

    With this fix, all SDK Listeners are considered “blocking”. While a “blocking” listener should not impact the restart of another SDK “blocking” listener, an impact can occur when a listener is slow to restart and therefore blocks another from restarting. Likewise, a “blocking” listener could impact the restart of a “non-blocking” listener, such as the Web Services Server listener, on new deployments when an SDK “blocking” listener is slow to restart and you deploy a “non-blocking” listener. In this case, the “non-blocking” listener is put in a queue behind the SDK Listener currently restarting. (CON-952)

Live Optics (Tech Preview) connector


  • The Live Optics (Tech Preview) connector enables you to connect to the Live Optics application and Get necessary data in JSON format using Public APIs (PAPIs) and Project ID. (CON-1076)

    To learn more about this feature, see the topic Live Optics (Tech Preview) connector.

NetSuite connector


  • You can create custom fields in NetSuite for transaction line items (referred to as Transaction Column Fields) to hold any data you want. For example, you can customize invoice line items that refer to a product or service added to an invoice. Previously, when importing a profile from NetSuite for a custom-defined transaction, the Transaction Column Fields did not appear in the profile. With this fix, custom Transaction Column fields appear in the profile and are appropriately named after the customization. (CON-84)

OpenManage Enterprise (Tech Preview) connector


  • The OpenManage Enterprise (Tech Preview) connector allows you to connect to Dell OpenManage Enterprise (OME) and use a process to query Alerts (based on ID, SeverityType and Timestamp filters) in OME and receive output data in JSON format. (CON-1238)

    To learn more about this feature, see the topic OpenManage Enterprise (Tech Preview) connector.

SDK connectors


  • When a field in a previous version of a custom connector was made unavailable in a newer version, the field and its value still existed in the component.xml. With this fix, fields that are no longer in the user interface are not saved to the component.xml. (CON-1248)

Connectivity development

Connector SDK


  • With this release, the Connector SDK is updated to version 2.5.2. For more information about the enhancements in this update, see the SDK changelog.

  • The Connector SDK public repository and artifacts are now available on Boomi's Amazon S3 repository. You can now build a custom connector and maintain your projects without the downloadable distribution file. As a part of these changes, the Boomi Connector SDK API Javadocs are hosted in Boomi's Amazon S3 repository. The OnDemand javadocs are deprecated and will be removed in a future release. (CON-1368)

    To learn more about this feature, see the topic Building a custom connector.

    For the latest version of the javadocs, see:

  • The SDK now supports creation of importable operation fields that are usable after an Import (browse). This feature is made possible through the addition of the new UI definition, browseField.xsd, and the ability to create browseField objects as a part of the getObjectDefinitions method. (CON-888)

    To learn more about this feature, see the topics Connector descriptor file and Implementing Browse.

  • Custom connector developers can configure the DistributionMode as a part of the SubmitOption for SDK Listen operations. The DistributionMode accepts the following values to determine how submitted process executions are distributed and executed in a multi-node Molecule: “LOCAL_ONLY” and “PREFER_REMOTE”. (CON-943)

  • In descriptors, a customProperty field type can be declared for a connection, operation, and in the Import wizard. This lets users define a list of key-value pairs in the connection and operation components and dynamically apply them based on the property and use case. (CON-1291)

    To learn more about this feature, see the topic Connector descriptor file.

  • The SDK enables the extension of the ListenOperation class for SDK connectors to include a SingletonListenOperation interface, allowing Listen operations to run in singleton mode. A container property (com.boomi.container.bounded.listen.enabled) is available to enable and disable this feature. (CON-1230)

    To learn more about this feature, see the topic Implementing the Listen operation.

  • When running in singleton mode and starting the Listen operation on the node, the Listen Manager currently determines the active node by obtaining a file lock. With this feature, the lock files appear in a dedicated bounds directory, and the Listen Manager attempts to delete the lock file when released. (CON-1337)

    To learn more about this feature, see the topic Implementing the Listen operation.

Master Data Hub

There are no updates to Master Data Hub in the June 2020 release.

B2B/EDI Management

Note: See the AtomSphere API and Partner API section of these release notes for information about additional B2B/EDI Management-related fixes in the June 2020 release.

X12 document handling


  • Processes using a Start shape with an X12 trading partner failed upon execution of a Try/Catch shape when there were more than 20 incoming interchanges. With this fix, a Try/Catch shape can be expected to execute without error under the same circumstances. (B2B-1035)

    Note: This fix required the release of all Trading Partner connectors.

API Management

Authentication Brokers and API Gateways


  • You can set a custom Authentication Broker com.boomi.plugin.authservice.accesslog.enabled property to true to enable access logs to be included in Log File downloads. (APIM-1587)

    To learn more about this feature, see the topic Authentication Broker settings.

  • You can set a custom Authentication Broker com.boomi.plugin.authservice.basicAuth.session.max.time property to control the Basic Authentication session maximum time. If you do not set this property, the default is five minutes. (APIM-1728)

    To learn more about this feature, see the topic Authentication Broker settings.

  • You can set a custom Authentication Broker com.boomi.plugin.authservice.jvm.options property to control the JVM heap size. If you do not set this property, the default is -Xms64m -Xmx512m. (APIM-1740)

    To learn more about this feature, see the topic Authentication Broker settings.


  • An API Gateway timed out after processing approximately 4MB of data. With this fix, the API Gateway does not time out when processing data. (APIM-1455)

Developer Portal


  • You can now set a custom home page title and welcome message for each Developer Portal. (APIM-37)

    To learn more about this feature, see the topic Configuring your Developer Portal.

Boomi Flow

The following information identifies the new features and fixes in Boomi Flow Core releases 1.154.4, 1.154.5, 1.154.6, SharePoint Service 1.1.0, Timer Service 1.3.0, Tooling 2.21.0, and User Interface 3.18.0.



  • A “Value cannot be null” error was displayed when importing older flow packages containing null configurations for map elements. With this fix, flow packages of this type are imported correctly. (FLOW-1754)

  • A "Value cannot be null" error message was displayed when selecting a page layout during the configuration of a page map element. With this fix, the error message is no longer displayed. (FLOW-1594)

  • Encrypted values were unable to be created if no default content value was defined. With this fix, encrypted values of this type can be created. (FLOW-1602)

  • New properties added to an existing type were not recognized by existing values bound to the type when a flow was run. With this fix, the new properties are correctly recognized by the existing bound type values. (FLOW-1635)

  • Run-specific endpoints were not correctly generated in the Boomi Flow API reference documentation. With this fix, run-specific endpoints are available in the Boomi Flow API reference documentation. (FLOW-1737)

  • The "is empty" command was always being evaluated as 'true' when checking date/time values in a business rule. With this fix, the "is empty" command now evaluates correctly for date/time values in a business rule. (FLOW-1715)

  • The property of a value was not being cleared when using an operator map element to empty the value, with no error message or warning displayed to inform the user that the operator was not being correctly applied. With this fix, operator map elements used to clear value properties operate correctly. (FLOW-1670)

  • Values referenced in another object value property are not parsing correctly when running a flow, resulting in the value reference snippet (for example {![value name]}) being displayed instead of the default content value of the referenced value. With this fix, referenced values are parsed correctly. Please note that affected object or list values will need to be re-saved. (FLOW-1736)

SharePoint Service


  • A “403” error message was displayed when installing the Sharepoint Service with either an incorrect configuration, or where the user had administrator permissions for a group but was not set to be a member of the group. With this fix, the error message now informs the user of the configuration error requiring attention, and the site is no longer included if the user is not a member of the group. (FLOW-1359)

Timer Service

  • Flows using the timer service were not correctly progressing forward after the scheduled time defined in the service had elapsed. With this fix, the timer service now operates correctly, progressing a flow once the scheduled time has elapsed. (FLOW-1793)


  • Alert notifications were incorrectly persisting when changing from one tenant to another. With this fix, these alert notifications are cleared when switching tenants. (FLOW-455)

  • Alignment for some drop-downs and buttons in the basic page conditions form was incorrectly formatted. With this fix, the drop-downs and buttons are correctly aligned. (FLOW-1263)

  • The notification icon was incorrectly formatted in Google Chrome 83.0.4103.61.With this fix, the icon is correctly aligned. (FLOW-1797)

User Interface


  • Using the Tab key to tab to an outcome from a form field that triggers a page condition caused the flow to progress forward. With this fix, tabbing to an outcome from a form field does not trigger progression in the flow. (FLOW-1601)