Boomi Integration release notes for 14 Sep 2019
The following list shows new features, enhancements, and bug fixes in the Boomi Integration September 2019 release.
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.
Learn more about the new features and enhancements in the September Release Highlights blog post in the Dell Boomi Community.Note: Dell Boomi is committed to modernizing its integration platform to ensure ongoing reliability, performance, and scalability. As part of this effort, migrations of the following Atom Clouds to new hosts are planned as follows:
Migrations targeted for September 21, 2019
Dell Boomi ANZ Hub Cloud
Dell Boomi ANZ Integration Cloud
Migrations targeted for October 19, 2019
Dell Boomi GBR Hub Cloud
Dell Boomi GBR Integration Cloud
Dell Boomi US Test Atom Cloud (Legacy)
Dell Boomi USA East Hub Cloud (formerly US Hub Cloud)
To learn more about the transition plans, see the Dell Boomi's Planned Improvements to its Hosting Environment article in the Community. For an updated list of Atom Cloud IP addresses, see Hostnames and IP addresses for the Dell Boomi Atom Clouds.
Release notes for the 12 months preceding the current release are archived.
Issue summaryNote: The “Usable in RC?” column indicates whether individual features, enhancements, and fixes are usable during the Release Control window before final release. Atom and connector updates are included in Release Control and usable, but neither the AtomSphere platform nor Dell Boomi browse Atoms are updated until the actual release. Therefore, until the actual release:
You cannot use Atom and connector enhancements and fixes with companion platform changes.
You cannot use connector enhancements and fixes with browse changes for connectors that support browsing only through a Dell Boomi Atom Cloud.
|Area||ID||Usable in RC?||Summary|
|AtomSphere API and Partner API||B2B-424||No||Use the API to QUERY for HL7 trading partner document metadata.|
To learn more about this new feature, see the topic HL7 Connector Record object.
|AtomSphere API and Partner API||B2B-426||No||Use the API to QUERY for Custom trading partner document metadata.|
To learn more about this new feature, see the topic EDI Custom Connector Record object.
|AtomSphere API and Partner API||INT-116||No||Administrators can use the new Trusted IP Addresses page in Setup to specify a list of trusted IP addresses that can access the API.|
To learn more about this new feature, see the topic Trusted IP addresses management.
|Platform||BOOMI-27127||No||API Management users can create API Proxy components as a means of seamlessly sending API requests to any mix of endpoints — Dell Boomi-supported or not — through the same authentication, validations, and authorizations.|
To learn more about this new feature, see the topic API Proxy components.
|Platform||IS-245||Yes||Intelligence is a set of features that use the latest intelligent algorithms to help you improve your experience with the Dell Boomi AtomSphere platform and its elements, develop faster, make well-informed decisions, and help improve and enhance our Intelligence with new capabilities.|
To learn more about this new feature, see the topic Intelligence.
|Kafka (Tech Preview) connector||BOOMI-7614||Yes||This connector was released off cycle into production after the August 2019 release. Kafka is designed for distributed high-throughput systems. Use this connector to build streaming data pipelines that reliably share data between systems or applications.|
To learn more about this connector, see the topic Kafka (Tech Preview) connector.
|Area||ID||Usable in RC?||Summary|
|Atom Installers||RUN-198||No||The Atom, Molecule, and Atom Cloud installers and updaters are modified to use Java 1.8.0_221. Dell Boomi Atom Clouds are also modified to use Java 1.8.0_221.|
|AtomSphere API and Partner API||B2B-547||No||Use the API to set Atom extension values for Communication Channels.|
To learn more about this enhancement, see the topic Atom Extensions object.
|AtomSphere API and Partner API||B2B-548||No||Use the API to set environment extension values for Communication Channels.|
To learn more about this enhancement, see the topic Environment Extensions object.
|AtomSphere API and Partner API||INT-982||No||Use the API to GET a single audit log document. Unlike QUERY results, single audit log documents include audit log entries of type as.extension (extension values). Each QUERY result now contains a document ID that is used with the new form of the GET operation.|
To learn more about this enhancement, see the topic Audit Log object.
|Platform||BOOMI-25053||No||API Management users can select a new Authentication Type, Gateway, in the Shared Web Server panel of Atom Management.|
To learn more about this enhancement, see the topic Shared Web Server panel.
|Platform||BOOMI-38209||No||API components are now called API Service components to distinguish them from the new API Proxy components.|
|Platform||INT-927||No||It is easier to set date formats within Map functions as a result of the addition of drop-down options.|
|Platform, AS2 Client connector||B2B-545||No||New AS2 Send action document properties are available, enabling you to dynamically set the receiver and sender IDs from the outbound message using profile elements. The new document properties are AS2 From ID and AS2 To ID.|
|Microsoft Azure Blob Storage connector||BOOMI-37874||Yes||The connector’s error messaging is improved.|
|OData Client connector||CON-122||Yes||For navigation properties in the OData v4 Query operation, you can select a non-leaf node and receive all of its leaves or select a leaf node without selecting an intermediate branch. This enhancement prevents the resulting URL from being too long and supports $expand without requiring a nested $select. Re-importing a profile enables these enhancements for existing operations.|
To learn more about this enhancement, see the topic OData Client operation (V 4.0).
|SAP connector||BOOMI-36741||No||Enable Low Latency Logging is available as an option in Listener Settings within the connection. If this option is selected for a connection used in a Low Latency process, you can still troubleshoot the process while taking advantage of improved processing speed.|
To learn more about this enhancement, see the topic SAP connection.
|SAP connector||CON-156||Yes||To facilitate troubleshooting, inbound documents are preserved after failed General Mode listener process executions, and the documents are available in Process Reporting. Low Latency processes do not preserve documents.|
|Area||ID||Usable in RC?||Summary|
|Atom||BOOMI-38194||Yes||API handlers are not always started by the Atom in the AS2 Server and Shared Web Server at startup time.|
|Atom||RUN-181||No||SSL connections using deployed trusted certificates may intermittently fail while the certificates are redeployed.|
|AtomSphere API and Partner API||B2B-483||No||Functional acknowledgments for X12 documents listed on the Errors tab in Process Reporting are erroneously omitted from X12 Connector Record object query results.|
|Platform||B2B-499||No||When a registered X12 document type is saved in a trading partner component without setting any document options, the saved component does not include the Expect Acknowledgement For Outbound Documents option, even though the option is selected by default.|
|Platform||INT-569||No||When retrying a test in test mode for processes that produce documents, the scroll bar is missing in the documents section, thereby preventing access to the entire documents list.|
|Platform||INT-574||No||An error occurs when creating a component type profile with XML selected as the profile type.|
|Platform||INT-795||No||On the Extensions screen, user name and password fields are automatically populated by the browser’s autofill feature.|
|Platform||PS-296||No||Atom status events may be processed in different order on different platform nodes.|
|Platform, AS2 Client connector, AS2 Shared Server connector||B2B-294||No||Content Length is not shown for AS2 processes in Process Reporting.|
|EDIFACT, HL7, Tradacoms, and X12 trading partners||B2B-328||Yes||Tracked field values sourced as dynamic document properties are not shown in Procsss Reporting.|
|X12 trading partner||B2B-661||Yes||X12 documents with multiple GS segments per ISA line are rejected with a Duplicate ISA Control number error.|
|Amazon S3 REST connector||BOOMI-38113||Yes||When using the connector behind a proxy server to upload large files to an Amazon S3 bucket, a communication error occurs in certain cases when the proxy server modifies the request body sent by the connector.|
|AS2 Client connector||B2B-640||Yes||Tracked field values sourced as dynamic document properties are not shown in Procsss Reporting.|
|MLLP Client connector||B2B-641||Yes||Tracked field values sourced as dynamic document properties are not shown in Procsss Reporting.|