Boomi Integration release notes for 10 Aug 2019
The following list shows new features, enhancements, and bug fixes in the Boomi Integration August 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 August 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 Amazon Web Services are targeted for September 21, 2019:Dell Boomi ANZ Hub Cloud
Dell Boomi GBR Hub Cloud
Dell Boomi GBR Integration Cloud
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 summary
Note: 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.
New features | |||
| Area | ID | Usable in RC? | Summary |
| AtomSphere API and Partner API | B2B-425 | No | Add support for programmatically querying Tradacoms Connector Record objects. For more information, see Tradacoms Connector Record object. |
Enhancements | |||
| Area | ID | Usable in RC? | Summary |
| Platform | B2B-449 | No | Add the capability to extend Communication Channel settings for HTTP communication.For more information, see: |
| Amazon S3 REST connector | BOOMI-37245 | No | Add the capability to manually specify the AWS bucket region either in the operation or at the document level, thereby circumventing the automatic identification of the region. For more information, see Amazon S3 REST operation. |
| Google Ad Manager connector | BOOMI-37698 | No | Add support for Version 201905 of the API. For more information, see Google Ad Manager connector. |
| HTTP PATCH Client connector | BOOMI-33159 | No | Add support for AWS Signature v4 authentication. For more information, see HTTP PATCH Client connection. |
| Microsoft Azure Blob Storage connector | CON-166 | Yes | Improve the connector’s error messaging. |
| SAP connector | CON-92 | No | Add the capability to specify JCo properties using a properties file. For more information, see SAP connection. |
Fixes | |||
| Area | ID | Usable in RC? | Summary |
| Atom | B2B-246 | Yes | If an escape character is used to avoid conflict with a delimiter, the escape character is erroneously being counted and causing output to be truncated when using Field Length Validation for an EDI element. |
| Atom | RUN-160 | Yes | The DNS Time To Live System property is incorrectly set. |
| Platform | B2B-226 | No | It is not possible to filter tracked fields by values that contain “<” or “>”, such as AS2 message IDs. |
| Platform | BOOMI-32154 | No | Legacy attachments to Dell Boomi Atom Clouds cannot be deleted. |
| Platform | CON-105 | No | In certain connectors implemented using the Connector SDK, a non-leaf node selected for a Query operation remains selected only if one of its leaf nodes is also selected. |
| Platform | RUN-48 | No | The account name filter is erroneously applied to shared server log download requests originated by the Atom, Molecule, or Atom Cloud owner. |
| Trading partners | B2B-508 | Yes | EDIFACT documents that contain line feeds between segments are not routed from the trading partner Start shape. |
| Trading partners | B2B-521 | Yes | The UNT segment count is incorrect for EDIFACT documents that contain an escape character (?) followed by a single quote. |
| Trading partners | B2B-541 | Yes | If an EDIFACT trading partner is configured to use Recipient’s Reference/Password, that value is not set in the output document’s UNB segment. |
| Database connector | BOOMI-31891 | Yes | When a dynamic document property is set in a process prior to a Database connector shape, the dynamic property value is not persisted through the Database connector shape upon process execution. |
| HTTP PATCH Client connector | CON-192 | Yes | An error occurs during HTTP PATCH requests if a custom HTTP header contains leading whitespace. |
| MDM connector | HUB-299 | Yes | When a connection to a Hub Cloud unexpectedly closes, an error occurs in certain cases while logging the connection error. |
| SFTP connector | BOOMI-26712 | Yes | When a dynamic document property is set in a process prior to an SFTP connector shape, the dynamic document property value is not persisted through the SFTP connector shape upon process execution. |