These release notes identify the new features and bug fixes slated for release in AtomSphere in October 2019. Atom and connector features and fixes that are available during Release Control are indicated. Links to additional information will appear here on the release date.


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


AtomSphere platform is updated with our new Boomi brand. You'll see these changes on the landing page and in the masthead. Plus, you'll see updated buttons, fonts, and colors throughout platform.

Curious to learn more about the new Boomi brand? Take a look at our Brand FAQ.


Atoms, Molecules, and Atom Clouds


Public Atom Clouds

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 targeted for November 16, 2019:

  • Dell Boomi GBR Hub Cloud

  • Dell Boomi USA East Hub Cloud (formerly US Hub Cloud)

Migrations of the following Atom Clouds to new hosts are targeted for January 18, 2020:

  • Dell Boomi GBR Integration Cloud

  • Dell Boomi US Test Atom Cloud (Legacy)


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.


Atom message queuing

Fix:

  • When a process using the Atom Queue connector fails to write messages to queue due to network issues, the process does not report errors.

    With this release, processes using the Atom Queue connector successfully report network errors. (RUN-272)

    This fix is available for use during Release Control.


Boomi Integration


XSLT support

You can now use Boomi Integration processes to apply XSLT transformations to XML documents. A transformation is defined in an XSLT Stylesheet component and applied using an XSLT Transformation step in a Data Process shape. (INT-1118)Note: XSLT support is a Tech Preview not intended for production use.

This feature is not available for use during Release Control. 


Cloud account properties

You can select Default Time Zone for Account Schedules as a new advanced account property available for Clouds and Cloud attachments. Setting this property specifies the time zone in which all of an account's process schedules run. (RUN-252)

This feature is not available for use during Release Control. 


Setup

Fix:

  • It is not possible to remove trailing whitespaces from one’s email address in the User Information panel (Setup > User Information).

    With this release, it is possible to remove trailing white spaces from one’s email address. (INT-417)

    This fix is not available for use during Release Control.


JSON profile generation

The following fix was released off-cycle into production after the September 14, 2019 release.

Fix:
  • Large Swagger documents may contain repeated JSON node types, causing these types to loop when generating new JSON profiles.

    With this release, the platform limits the number of recursive reference types that are imported from the API Service's Swagger specification file. (INT-1278)


AtomSphere API and Partner API


Trading Partner object

Fix:

  • All trading partner settings are not programmatically accessible and settable.

    With this release, the Trading Partner object is updated to include these previously omitted settings:

    • EDIFACT standard: Reject Duplicate UNB

    • HL7 standard: Reject Duplicates

    • RosettaNet standard: Reject Duplicate Transactions

    • X12 standard: Outbound Validation Option, Reject Duplicate ISA, Validate Outbound Interchanges

    • AS2 communication method, Default Partner Identification Information: Client SSL Certificate, Messages to Check for Duplicates, Reject Duplicate Messages (B2B-452)

  • This fix is not available for use during Release Control.


Connectivity


Amazon S3 REST connector

Fix:

  • When using server-side encryption (SSE) for multipart uploads, all SSE headers are erroneously included in all requests for the operation. As a result, multipart uploads fail.

    With this release, the headers are only included in the first request to initiate the upload, resulting in successful multipart uploads. (BOOMI-39090)

    This fix is available for use during Release Control.


Amazon SQS connector

When building a process, you can retrieve the queue and connect successfully without your account having the GetQueueUrl and ListQueues permissions. To circumvent the permissions, manually specify the queue URL either in the operation or at the document level. (BOOMI-38347)

This feature is not available for use during Release Control. 


JMS connector

Fix:

  • When a dynamic document property is set in a process prior to a JMS connector shape, the dynamic document property value is not persisted through the JMS connector shape upon process execution.

    With this release, a dynamic document property value set prior to the JMS connector shape should now persist, and using a dynamic document property to set the tracked field values in the JMS connector operation works as intended. (CON-29)

    This fix is available for use during Release Control.


Salesforce connector

When building a process, you can quickly and efficiently upload large amounts of data using v2 of the Salesforce Bulk API. (BOOMI-31875)

This feature is not available for use during Release Control. 


SAP connector

Listen operations now process incoming TID documents in Low Latency mode more efficiently. (CON-83)

This feature is available for use during Release Control.

Fix:

  • When you use Atom workers on an Atom Cloud to perform SAP listener executions in Low Latency Mode with low latency logging enabled, the executions are performed sequentially.

    With this release, these executions are performed in parallel, reducing the time it takes for large batches of IDocs to complete. (CON-336)

    This fix is available for use during Release Control.


Thru MFT - Partner connector

This connector was released off cycle into production after the September 14, 2019 release. Thru - MFT is designed to take your file transfer to a new level with unparalleled monitoring and control across all lines of business. (CON-352)


Web Services Server connector

Fix:

  • When web services are loaded on an Atom, the web services will stop loading when an exception is reached.

    With this release, web services continue to load on the Atom after an exception is reached. (BOOMI-38859)

    This fix is available for use during Release Control.


Workday connector

The Workday connector operation supports specifying Workday services as they are released and made available to your account by Workday. You can click Import to select the Custom option in the Service Name drop-down list, and use the Custom Service Name field to enter any valid Workday service not included in the list. A successful import will auto-populate Service Name and Custom Service Name in the operation. (CON-312)

This feature is not available for use during Release Control. 


Master Data Hub


Master Data Hub features and fixes are not available for use during Release Control.


Historical reporting

Historical reporting is now available for the count of end-dated golden records. (HUB-404)


Platform API

Aggregate counts of end-dated golden record counts are programmatically retrievable via the Platform API as a result of enhancements to the Get Repositories Summary, Get Repository Summary, and Get Universe Summary operations. (HUB-405)


Repository

Fix:

  • A batch error occurs and processing of the batch ends prematurely when enforcing referential integrity on a reference field value modified by a Boomi Integration process call data quality step triggered by an update to that reference field.

    With this release, such an entity would be quarantined and processing of the batch would continue. (HUB-467)


B2B/EDI Management


EDIFACT trading partners

Fix:

  • If in a trading partner, under Interchange Version / Control options, the Recipient’s Reference/Password is set and Qualifier is set to NA-Not Used, the password is erroneously omitted from processed documents.

    With this release, given these settings, the password is included in a processed document, as expected, and the Qualifier field in the document is empty. (B2B-703)

    This fix is available for use during Release Control.


Processing group components

Fix:

  • In a processing group component, it is possible to add a partner route for a document type that is not defined for the selected trading partner.

    With this release, it is possible to add partner routes only for document types defined for the selected trading partner. If one attempts to add a partner route for a document type that is not defined for the selected trading partner, an error message is displayed. (B2B-591)

    This fix is not available for use during Release Control.


API Management


API Management features and fixes are not available for use during Release Control.

When you add a subscription on the Configure APIs and Applications > Applications page, you now can specify a date for the subscription to be enabled or disabled. (APIM-211)

Fix:

  • The Configure Server > Internal Roles page limits the displayed Internal Roles to 25.

    With this release, all of your Internal Roles display on the Configure Server > Internal Roles page. (BOOMI-39443)


Authentication Brokers and API Gateways

There are no updates to Authentication Brokers and API Gateways in the Oct 2019 release.


Developer Portal

An Application Owner Name is visible on new or existing Applications within the Developer Portal. Previously, this field was set in API Management on the Configure APIs and Applications > Applications page, but was not being populated in the Developer Portal. Now, this data populates within the Application on your Developer Portal where it can be viewed or edited. If the Application Owner Name is edited in the Developer Portal, it updates the value in API Management. (APIM-94, APIM-103)


Boomi Flow

The following information identifies the new features and fixes in Boomi Flow Tooling release 2.12.0, UI release 3.10.0, and Core releases 1.129.0 - 1.131.0.


Tooling

Boomi Flow builders can access the Notification menu from the platform menu bar to view the user's five most recent notification messages, and to see all notifications from the Notifications page. Users are presented with the following notification types: faults, warnings, password resets, create tenant, delete tenant, and delete all. (FUI-317)


When exporting a Flow package or generating a sharing token, the addition of a new checkbox allows builders to export passwords. (FUI-40)

Notification handling is improved in the macro editor.


Fixes:

  • Long flow names are no longer truncated in the Flow tile. (FUI-376)

  • Upon saving a Step element, the content field erroneously does not recognize user input and prompts the user to reenter the value.

  • When creating default values for a list value, users are unable to create nested lists.

  • When creating business rules, users are unable to select “All equal” or “Any equal”. Prior to this fix, users edited the business rule metadata as a workaround.

  • When creating a page rule, users are unable to clear the left/right page component selection from the drop-down.

  • The Flow canvas crashes when the user expands a swimlane beyond a certain size.

  • The character length of input into the Flow Summary field is validated client-side.

  • Only system boolean values are available for selection when creating a business rule, and do not include other boolean values available in the tenant.

  • An error occurs when attempting to delete a page container that contains a child container with embedded page components.

  • Google Chrome automatically populates the Type drop-down with information from the browser’s autofill feature.


User interface

Runtime user interface files are appended with the current version number rather than a random hash. This allows Boomi Flow builders to easily select and use previous versions of the runtime user interface in their custom players. (FUI-281)


The table component can perform client-side sorting on data that is not retrieved from a service. For example, a table populated with data derived from a list value is now sortable. Previously, the ability to sort data was wholly dependent on the service. (FUI-436)

Fixes:

  • The tile component is ignored when setting a label.

  • Date times in the datepicker component are erroneously set back by a day when the BST timezone is set.

  • Selected items are duplicated in a combo box.

  • Users are unable to upload files in Internet Explorer version 11.

  • The file upload component is not indicated as a required field.

  • Selected table rows are not persisted when a flow performs a sync request —for example, when a page condition is executed — or when the user refreshes the page.

  • Object data is duplicated when running a Flow offline. Duplication occurs when the Flow periodically caches object data.

  • The combo box component erroneously indicates a field as required.


Core

Services can now pass the name of bindings that are currently used when loading data with nested objects and lists. (1.129.0/CORE-5108)

Missing page data is generated and added to all page endpoints in the Draw API. (1.130.0/CORE-5002)

Performance is improved for build-time system flows and other flows that use the legacy Draw Service. (1.131.0/CORE-5393)


Fixes:

  • Value reference searches do not return references for value properties in some scenarios.

  • Performance degrades when a page is loaded in a tenant that has many complex values and types.

  • Invalid and empty criteria types in page conditions throw a “Key not found” exception.

  • Unsaved page conditions, rules, and operations do not display their auto-generated summaries.

  • The getPropertyBooleanValue macro method throws an un-catchable exception when reading a null property value.