These release notes identify the new features and bug fixes released in AtomSphere for April 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


Audit logs

Fix:

  • When applying pending updates to a connector and migrating a connector from one account to another, the source value for the audit log entry was not provided. With this fix, the source value for the entry is provided, as expected. (CON-903)

Connector releases

Feature:

  • Executing connector updates for releases is now faster. This is a non-functional change to enhance the performance of connector releases. (CON-894)

Data Collection

Feature:

  • For a consistent user experience, the ability to opt-in to Data Collection (formerly, Intelligence) has been moved to the Account Features page (IS-533).
    • Existing customers who previously opted-in to Intelligence are automatically opted-in to Data Collection.
    • Existing customers who previously opted-out of Intelligence are automatically opted-out of Data Collection.
    • New customers are automatically opted-in to Data Collection, but may optionally opt-out.

Additionally, the documentation is updated to be clear about what information is collected and how it is used.

To learn more about this feature, see the topic Data Collection.

Packaged Component Deployment

Packaged Component Deployment was released in March 2020 and offers a new and improved work flow for deploying your processes and components to various environments, sharing to the Process Library, and adding to integration packs. Administrators that currently manage Legacy Deployment accounts are reminded to take advantage of the new functionality by enabling the Packaged Component Deployment feature from the Setup > Account Features page.

For more information about upgrading your Legacy Deployment account to use Packaged Component Deployment, see the Account features management and Enabling packaged component deployment for legacy accounts topics.

Platform sign-in

Feature:
  • Sign-in performance is improved for users of accounts with a large number of environments. (ADSEC-572)

User management

Feature:

  • A new user role is added to the Setup > User Management page for API Management - Access to enable you to allow only specific users access to API Management. (APIM-1096)

Welcome page

Feature:

  • A new welcome experience is released that contains information from all areas of the AtomSphere platform as well as links to additional information from other Boomi resources such as help content, Boomi Community, and training. (UNI-1, UNI-103, UNI-104, UNI-105)

    Seeing the new welcome page requires you to opt-in to Beta features by going to Setup > Beta Features > New build canvas and component icons and enabling the toggle. Then, click the AtomSphere logo to open the new welcome page. In future months, the new welcome page will become more robust and eventually will open by default.

    Note: This feature was previously deferred from the March 2020 release.

Atoms, Molecules, and Atom Clouds


Docker images

Features:
  • Docker installers for Atoms, Molecules, and Clouds are now converted to use the new Red Hat Enterprise Linux Universal base image (RHEL UBI). (RUN-392)

    To learn more about this feature, see the topic Docker installation of an Atom, Molecule, or Atom Cloud.

  • To allow the installation of Docker images to be configurable, a new environment variable HOST_INSTALLATION_DIRECTORY and installer configuration parameter (-g) are added to allow users the ability to specify the host installation directory. (RUN-394)

  • Changes to atom_home ownership can be made during new Docker installations only, and no longer at every startup. (RUN-423)

  • The AtomSphere platform now employs a new Docker infrastructure provider. Docker containers installed prior to the April 2020 release are defined as “Legacy Docker” in the Infrastructure Provider field of the Startup Properties panel and in the results of the Startup Properties API object. Newly installed Docker containers are listed as “Docker” in Startup Properties. (RUN-457)

    To learn more about this feature, see the Startup Properties panel and Atom Startup Properties object topics.

  • Docker installations for Molecules and Atom Clouds now default the cluster network transport type property to UNICAST. (RUN-477)

    To learn more about this feature, see the topic Properties panel, Advanced tab.

  • Users can set newly introduced container.properties (-j) and atom.vmoptions (-v) parameters during the installation of a Docker image. (RUN-497)

  • Docker installations for Molecules and Atom Clouds now default to use local storage. The local storage directory in the Docker image is /opt/boomi/local. (RUN-525)

    To learn more about this feature, see the topic Molecule and Atom Cloud working data storage.

Java security compatibility

Feature:

  • To maintain compatibility with Java 1.8.0_241 version upgrades, a new security compatibility property, jdk.security.allowNonCaAnchor, is introduced which preserves certificate functionality that may have otherwise been affected. (RUN-407)

    To learn more about this feature, see the topic Controlling Java security compatibility.

    Note: Support for Java 1.8.0_241 version upgrades was previously deferred from the March 2020 release.

Java upgrades

Feature:

  • The Atom, Molecule, and Atom Cloud installers and updaters are modified to use Java 1.8.0_241.

    Java 1.8.0_241 upgrades limit the number of capture groups defined in Javascript custom scripts to 32,767.

    When establishing a TLS connection, Java 1.8.0_241 requires that the TLS server certificate be an exact match of a trusted certificate on the client in order for it to be trusted. (RUN-302, RUN-310)

    To learn more about this feature, see the topic Java upgrade FAQ.

    Note: Boomi public Atom Clouds are also modified to use Java 1.8.0_241.
    Note: Support for Java 1.8.0_241 version upgrades was previously deferred from the March 2020 release.

Logging

Fix:

  • When there is a head node issue, the Flushed API call count log can show hundreds of records. With this fix, the Flushed API call count log is changed to a DEBUG level so that these records are not all shown. (APIM-1121)

Public Atom Clouds

Boomi is committed to modernizing its integration platform to ensure ongoing reliability, performance, and scalability. As part of this effort, migration events will be scheduled to occur during 2020. You will receive an email notification 60 days in advance of a migration event that will include your account.

To learn more about the transition plans, see the Boomi's Planned Improvements to its Hosting Environment article in the Boomiverse community. For an updated list of Atom Cloud IP addresses, see the topic Hostnames and IP addresses for the Boomi Atom Clouds.

Boomi Integration


API Proxy component

Fix:

  • Importing an API Proxy component using a Swagger file that is missing a license node caused the import to fail. With this fix, a Swagger file that is missing a license node imports to an API Proxy component successfully. (APIM-724)

Atom Management

Fixes:
  • Previously, the Atom Management page was slow to load for accounts that contain a large number of containers and environments. With this fix, the loading performance of the Atom Management page is improved for such accounts. (INT-1846)

  • Some inconsistencies were reported in the behavior of the Atom Management Read Access role, and, as a result, users may have erroneously had access to certain features within the platform. With this fix, Atom Management roles behave as intended. (ADSEC-573)

Environment Management roles

Feature:
  • Account administrators can apply the new Environment Management Read Access and Environment Management Full Access custom roles to enforce more granular access controls at the environment level.

    Administrators can enforce these roles by selecting the Advanced Environment option in Setup > Account Features, and then create and assign these custom roles to users in Setup > User Management. In the Environment Management page, administrators then assign their new Environment Access custom roles to various environments within the account as desired. As a result, users with roles which match that of the environment the environment can either view or edit the environment's settings. (ADSEC-28)

    To learn more about this feature, see the topic Account Features management.

JSON profiles

Feature:
  • To optimize platform performance when importing a new JSON profile, it is now not possible to generate more than 5,000 nodes. This limitation applies only to imported JSON profiles; you can manually add new nodes beyond these limits. (INT-1746)

    To learn more about this feature, see the topic Importing a JSON document into a JSON profile.

OData API endpoints

Feature:

  • Processes started with a Web Services Server connector in the Start shape now include inheader_ for OData endpoints that are set in the Dynamic Document Properties header settings and are not in a protected header group. These inheader_ prefixes will cause the prefix outheader_ on the result document. (APIM-12)

    Note: This feature was previously deferred from the March 2020 release.
    Note: This feature has companion changes covered in the Connectivity section of these release notes.

Packaged Component Deployment

Fix:
  • Previously, the Deploy: Select Packaged Component screen of the Deploy wizard allowed users to select packaged components before the screen finished loading. With this fix, interaction with selection boxes is not allowed until the screen finishes loading. (INT-1871)

Process configuration for API Service components

Fix:

  • Dynamic Document Property headers were returned in the same case as the HTTP header request. This caused the returning of false null values due to a case insensitivity when calling the inheader_ value. For example, calling inheader_Test returned a null value because all headers were being generated as lowercase and resulted in the sending of the value as test rather than Test. With this fix, you can set the Atom property com.boomi.container.sharedServer.http.header.includelowercase to true to return both versions, inheader_Test and inheader_test.

    Sending both versions increases the chance of matching the Dynamic Document Property header in the integration process, regardless of case, and decreases the likelihood of a false null value being returned. Setting the property to false, or not setting a value, keeps the prior behavior. (APIM-1286)

    Note: The previous fix, APIM-873, was deferred from the March 2020 release.
    Note: This fix has companion changes covered in the Connectivity section of these release notes.

AtomSphere API and Partner API

Integration component metadata APIs

This release introduces a series of API objects that can be used in combination with one another to provide visibility into the details of components created in your account, including component metadata, packaged component details, and component configuration.

These new objects, along with the Component Metadata object (released in March 2020), allow Boomi components to be incorporated easily into external deployment workflows and continuous integration and delivery tools. For example, upon creating a new packaged component for a process, the detailed configuration XML for all the components used within that process can be exported. This exported information can be stored in a code repository for archiving and version differentials, inspected by code quality tools for validation and compliance, and parsed for documentation generation.

The new API objects are as follows:
  • The Packaged Component Manifest object enables you to programmatically query for all the components that are included in a given packaged component, similar to how you might use the Packaged Component Details panel to view all the included components that make up a packaged component. (INT-1678)

    To learn more about this feature, see the topic Packaged Component Manifest object.

  • The Component object enables you to programmatically retrieve component configuration XML for a single component ID and version number, similar to how you view Component XML from the Revision History panel on the Build tab. (INT-1679)

    To learn more about this feature, see the topic Component object.

  • The Connector object enables you to programmatically query for all the connector types available to your account. For example, You can then use this information to filter by specific connector types when querying. (INT-1765)

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

Note: All component API objects are all read-only, and cannot be used to import, create, or modify components outside the Boomi user interface. The AtomSphere platform retains version management for all components.

Atom Security Policies object

Fix:
  • When using the Update operation, a failed request erroneously resulted in a successful update to the execution.security file. With this fix, the execution.security file is not updated when a failed request occurs. (RUN-258)

EDIFACT Connector Record object

Fix:

  • Query results for inbound documents erroneously included the outboundValidationStatus field. With this fix, the field is included only for outbound documents. (B2B-959)

    Note: This fix required updates to all EDI trading partner connectors.

    To learn more about this object, see the topic EDIFACT Connector Record object.

HL7 Connector Record object

Fix:

  • Query results for inbound documents erroneously included the outboundValidationStatus field. With this fix, the field is included only for outbound documents. (B2B-959)

    Note: This fix required updates to all EDI trading partner connectors and the MLLP Client connector.

    To learn more about this object, see the topic HL7 Connector Record object.

RosettaNet Connector Record object

Feature:

  • The object is extended to support validation of outbound RosettaNet documents. (B2B-702)

    To learn more about this feature, see the topic RosettaNet Connector Record object.

Trading Partner Component object

Feature:

  • The object is extended to support validation of outbound RosettaNet documents. (B2B-699)

    To learn more about this feature, see the topic Trading Partner Component object.

X12 Connector Record object

Fix:

  • Query results for inbound documents erroneously included the outboundValidationStatus field. With this fix, the field is included only for outbound documents. (B2B-959)

    Note: This fix required updates to all EDI trading partner connectors.

    To learn more about this object, see the topic X12 Connector Record object.

Connectivity


AtomSphere API connector

Fix:
  • The AtomSphere API connector consistently returned a “false” value for the Purge Data Immediately property, regardless if the property is turned on in the Cloud Properties panel. With this fix, the property returns the correct “true” or “false” value depending on how the property is configured in the panel. (RUN-275)

Audit logs

Fix:

  • When applying pending updates to a connector and migrating a connector from one account to another, the source value for the audit log entry was not provided. With this fix, the source value for the entry is provided as expected. (CON-903)

JMS connector

Fix:

  • If a document with user-defined dynamic document properties passed into a JMS connector shape with configured parameters, the dynamic document property values did not persist through the connector shape upon process execution. With this fix, the values persist through the connector shape upon process execution. (CON-340)

Oracle E-Business (EBS) connector

Fixes:

  • Previously, when executing stored procedure calls and queries, the connector provided all parameters to the procedure call even when the parameters were missing in the incoming XML document. The connector set the missing parameter values to NULL, resulting in DEFAULT values set for optional parameters not being used. With this fix, you can use the Exclude missing parameters from the procedure setting to control whether parameters missing from the input document are excluded from the procedure call or included with a value of NULL. (CON-604)

    Note: This fix was previously deferred from the March 2020 release.

    To learn more about this feature, see the topic Oracle E-Business (EBS) operation.

  • Procedures can now be imported from another schema. That is, the credentials for one schema can be provided in the connection settings to import a procedure defined in a different schema. All dynamic types needed by the connector in order to work with the procedure will be declared in the schema associated with the given credentials, not in the schema where the procedure is defined. (CON-716)

Salesforce Platform Events connector

Fix:

  • Valid connections could generate an access token but fail when communicating with Salesforce Platform Events (for example, during an operation). With this fix, these failing connections work as intended. Part of this fix changed how the connector establishes a connection. Now, new and existing connections use the access token’s instance_url property instead of the Instance URL field. As a result, the Connection Settings tab and Instance URL field are no longer available. Existing connections and extensions should work as expected. (CON-596)

Web Services Server connector

Feature:

  • Processes started with this connector in the Start shape now include inheader_ for OData endpoints that are set in the Dynamic Document Properties header settings and are not in a protected header group. These inheader_ prefixes will cause the prefix outheader_ on the result document. (APIM-12)

    Note: This feature was previously deferred from the March 2020 release.
    Note: This feature has companion changes covered in the Boomi Integration section of these release notes.

Fix:

  • Dynamic Document Property headers were returned in the same case as the HTTP header request. This caused the returning of false null values due to a case insensitivity when calling the inheader_ value. For example, calling inheader_Test returned a null value because all headers were being generated as lowercase and resulted in the sending of the value as test rather than Test. With this fix, you can set the Atom property com.boomi.container.sharedServer.http.header.includelowercase to true to return both versions, inheader_Test and inheader_test.

    Sending both versions increases the chance of matching the Dynamic Document Property header in the integration process, regardless of case, and decreases the likelihood of a false null value being returned. Setting the property to false, or not setting a value, keeps the prior behavior. (APIM-1286)

    Note: The previous fix, APIM-873, was deferred from the March 2020 release.
    Note: This fix has companion changes covered in the Boomi Integration section of these release notes.

Web Services SOAP Client connector

Feature:

  • You can select the document Tracking Direction for the EXECUTE action. The default is Input Documents, but you now have the flexibility to change this based on your needs. This setting affects which documents appear in Process Reporting. (CON-911)

To learn more about this feature, see the topic Web Services SOAP Client operation.

Connectivity development


Boomi repository

Feature:

  • The official Boomi repository (repo) is now available at bitbucket.org/officialboomi. The repo is intended as a resource for connector developers using the SDK to contribute and modify connector code for the AtomSphere platform, and to fork and modify connector code for private use. The repo allows Boomi to leverage the community to develop best-of-breed connectors and deliver customer value quickly by increasing the velocity of new connector delivery and enhancements.

Connector SDK

Features:

  • The Connector SDK is updated to version 2.3.0. For information about the updates in this release, see the Connector SDK changelog.

  • The user value for the trackedDocument attribute (@trackedDocument="user") is added to the connector descriptor to allow the tracking direction to be set on a per-operation basis. (CON-256)

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

  • The demonstration (demo) connector descriptor file (connector-descriptor.xml) is updated to demonstrate how you can use the @trackedDocument="user" attribute value to allow selection of the tracking direction for an operation. (CON-899)

    To learn more about this feature, see these topics:
  • Atom configuration property values are accessible through the AtomConfig instance using the following methods:

    • getContainerProperty(String key) — Access Atom property String values.
    • getBooleanContainerProperty(String key) — Access Atom property Boolean values.
    • getLongContainerProperty(String key) — Access Atom property Numeric values.
  • For each method, specify the key of the container property and the method returns the container property value. (CON-653)

    Note: If the property value does not exist for the specified key, you can specify a default value to be returned in the following format:
    • getContainerProperty(String key, String defaultValue)
    • getBooleanContainerProperty(String key, boolean defaultValue)
    • getLongContainerProperty(String key, long defaultValue)
  • Payload metadata can be created by calling the createMetadata() method using the Listener instance. (CON-479)

Fix:

  • The connector-sdk-model JAR contained schemas incorrectly stored in the root of the JAR file. With this release, these .xsd files are nested in the com/boomi/model/connector/ directory within the connector-sdk-model JAR. (CON-947)

Master Data Hub

Modeling

Feature:

  • Reference field names and collection names are validated to enforce length limitations. Changes to these names that would exceed a limit cannot be applied. For reference field names, the limit is 53 characters minus the number of characters in the model name. For collection names, the limit is 58 characters minus the number of characters in the model name. (HUB-762)

    To learn more about this feature, see the topic Fields tab.

Incoming source entity processing

Fix:

  • When an incoming entity specified an UPSERT operation on a collection item, if a collection field was omitted from the collection item, the field’s value in the golden record was nulled. With this fix, in this scenario the value of the omitted collection field in the golden record is retained, as expected. (HUB-754)

    Note: This fix was rolled back subsequent to the April 2020 release. The issue will be addressed in a future release.

B2B/EDI Management


RosettaNet document handling

Feature:

  • The option to configure a trading partner to enable outbound validation of RosettaNet v2.0 and v1.1 messages is now available. The level of validation performed on outbound messages is the same as inbound messages. The new settings are extensible. (B2B-156, B2B-700)

    Note: This feature has companion changes covered in the AtomSphere API and Partner API section of these release notes.

To learn more about this feature, see the topic Outbound EDI document validation.

Trading partner document reporting

Fixes:

  • The Outbound Validation Status and Outbound Validation Report columns did not appear for outbound X12, EDIFACT, and HL7 documents in the trading partner results table in Process Reporting. With this fix, the columns appear in the table for outbound X12, EDIFACT, and HL7 documents. (B2B-235)

  • Reporting of interchange-level outbound validation did not occur for X12 documents sent from trading partners for which the option to filter errored documents was selected. With this fix, the X12 trading partner connector is updated to enable interchange-level outbound validation results in this scenario to be reported for an execution in Process Reporting. (B2B-282)

  • The Ack Status column for an X12 document was not updated in the trading partner results table in Process Reporting upon receipt of the acknowledgment document (997) from the receiver process. With this fix, the X12 trading partner connector is updated to enable the Ack Status to be updated upon receipt of the acknowledgment document. (B2B-948)

API Management

API Key object

Feature:
  • You can now use the API Key object to delete pending or rejected subscriptions. (APIM-1112)

Authentication Brokers and API Gateways

Fix:

  • When an Authentication Source had a subscription associated with it, the Authentication Source could not be deleted. With this fix, you can delete an Authentication Source regardless of whether there are subscriptions associated with it. (APIM-1133)

Developer Portal

Fix:

  • Using Chrome, refreshing the Developer Portal multiple times gave an incorrect sign-in is unavailable error message. With this fix, the incorrect error message no longer displays. (APIM-923)

Subscription page

Feature:

  • A new column, Published Name, is added to the Subscriptions page to allow easier comparison between information in this page and the Subscriptions on the Developer Portal. The Subscriptions page is accessed by clicking the text in the Subscriptions column on the Configure APIs and Applications > Applications page. (APIM-648)

Boomi Flow

The following information identifies the new features and fixes in Boomi Flow Core release 1.148.0.

Core

Feature:

  • Tenant expiration dates are added to the /api/admin/1/tenant API endpoint. The Boomi Flow platform menu Account option is updated to display the tenant expiration date. (FLOW-794)

Fix:

  • The Service and message Action names were not displayed on the Message Action configuration panel when adding a message action to a message map element. With this fix, the Service and Action names are added to the message action API metadata. The names of the service and the selected message action are displayed in the Message Action configuration panel when adding a message action to a message map element. (FLOW-433)