What’s new in AtomSphere for Nov 2019
Modified on: Mon, 31 Aug, 2020 at 12:45 PM
These release notes identify the new features and bug fixes released in AtomSphere for November 2019.
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.
Additional design updates
Email address validation
Only user email addresses that have top-level domains with a length of two to six characters are accepted as valid.
With this release, a wider range of user email addresses are accepted as valid, including those with top-level domains containing more than six characters. (INT-400)
Atoms, Molecules, and Atom Clouds
Public Atom Clouds
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 will be scheduled:
Boomi GBR Hub Cloud
Boomi GBR Integration Cloud
Boomi US Test Atom Cloud (Legacy)
Boomi USA East Hub Cloud (formerly US Hub Cloud)
To learn more about the transition plans, see the Boomi's Planned Improvements to its Hosting Environment article in the Community. For an updated list of Atom Cloud IP addresses, see the topic Hostnames and IP addresses for the Boomi Atom Clouds.
A new advanced Cloud property, Atom Worker Pending Updates Queue Size, enables you to configure the size of the Worker Message Queue and optimize the Atom worker queue’s performance to handle large extension updates. (RUN-297)
To learn more about this feature, see the topic Properties panel, Advanced tab.
Users of Java 1.8.0_221 are denied access to the
java.util.TimeZone timezone method when running a custom Groovy script on a Boomi Atom Cloud.
With this release, users have authorized access to run a custom Groovy script on a Boomi Atom Cloud that uses the
java.util.TimeZone method. (RUN-290)
When a user provides only their proxy username to install an Atom, Molecule, or Atom Cloud, the installer erroneously assumes a password is also provided.
With this release, the installer validates that the user provides both their proxy username and password, and produces an error message if both are not specified. It is also acceptable to provide neither credential in order to pass validation. (RUN-241)
When installing an Atom, Molecule, Atom Cloud, Broker, or Gateway node, the JRE fails to completely download JRE files due to timeout issues.
With this release, the timeout for installing the JRE in an Atom, Molecule, Atom Cloud, Broker, or Gateway node is increased, and allows for the complete download and extraction of JRE files. (RUN-185)
When using a proxy to install an Atom via the Atom Docker installer, the installation fails because the proxy password is not set.
With this release, the Atom Docker installer is successfully run using a proxy server. (RUN-240)
After a large document errors in a process, the Atom is unable to send failure messages to the platform.
With this release, error messages are properly stored and truncated. (RUN-49)
Purging of Atom, Molecule, or Atom Cloud logs and data
The November release contains a change that was intended to improve purging performance (RUN-277). This change caused some local Atoms, Molecules, and private Atom Clouds to fail to compress some files during purging. If your containers experience an issue with compression, request Atom v19.11.8 from Support, which effectively rolls back the change. As of November 23, 2019, the rollback is applied to the Boomi
public Atom Clouds. (RUN-362)
Note: The change will be generally rolled back for the January 2020 Atom release.
Cross reference tables
An alignment issue occurs when exporting a cross reference table with a CSV field whose double-quoted value contains a comma, rendering the table uneditable.
With this release, exporting and reimporting a CSV file works as expected. (INT-414)
The Import from CSV option in a cross reference table does not handle special characters as expected.
With this release, special characters appear correctly in the cross reference table. (INT-568)
When a cross reference table containing a
# in a column header or row is imported to or exported from the Extensions dialog’s Cross Reference tab, the operation stops upon encountering the
#, and the resulting cross reference table or CSV file is incomplete.
With this release, the import or export operation continues. (INT-727)
Exporting cross reference tables produces an incorrect number of rows in some cases.
With this release, exporting cross reference tables produces the correct number of rows. (INT-1274)
On the Federation ID is in NameID element of the Subject option is selected as the Federation ID Location. page, there is no option to configure a Transient or Specified NameID Policy if the
With this release, you can configure a Transient or Unspecified Name ID Policy according to your identity provider’s needs. (INT-91)
The AtomSphere platform was subsequently re-released to apply related fixes on two occasions:
- With the first fix, all existing users now use Transient as the default Name ID Policy setting in their SSO Options configuration. Users are not required to make any changes as a result of this fix. (INT-1451)
- With the second fix, users can successfully use the UPDATE operation on the Account Single Sign-on Configuration object to enable single sign-on for an account, or update an account’s single sign-on options. (INT-1558)
To optimize platform performance, it is now not possible to generate more than 3,300 defined or anonymous types when importing a new XML profile. This limitation only applies to imported XML profiles; you can manually add new types beyond these limits. (INT-1166)
To learn more about XML profile limitations, see the topic Importing an XML profile from an XSD file.
To avoid type naming conflicts when importing XML profiles, a unique key is automatically generated for defined types that are created from anonymous types. (INT-1165)
Upon importing a particular WSDL file using the Web Services SOAP Client connector, the platform becomes unresponsive.
With this release, the platform successfully handles XML profiles imported from a WSDL file, including those that result in a large number of anonymous types. (INT-46)
AtomSphere API and Partner API
SSO-only users are not authorized to make Execute Process requests using their API tokens.
With this release, SSO-only users are successfully authorized to make Execute Process requests using their API tokens. (INT-1160)
SSO-only users are not authorized to make Download Process Log requests using their API tokens.
With this release, SSO-only users are successfully authenticated when making Download Process Log requests using their API Tokens. (INT-1205)
You can programmatically copy all counters from one container to another. (RUN-131)
To learn more about this feature, see the topic Atom Counters object.
Persisted process properties
You can programmatically copy all persisted process properties from one container to another. (RUN-135)
To learn more about this feature, see the topic Persisted Process Properties object.
The new release brings you new features and fixes to help you work smarter and be more efficient.
There is a new connector grouping, Event-Driven, in the Connect palette for the process canvas. This new organization provides greater visibility to connectors that address event-based integration needs, such as queuing, messaging brokers, event meshes, real-time streaming, analytics, and asynchronous APIs. (INT-1262)
The event-driven connectors are as follows:
AS2 Client connector
After selecting a certificate for a connector operation, it is not possible to remove it from the operation configuration.
With this release, the option to remove a previously selected certificate is added to the operation configuration dialog. This is a platform change — the connector itself is not updated. (B2B-676)
Disk (Tech Preview) connector
The Create operation now supports actions previously performed with an Upsert operation. This includes outbound actions such as inserting data for an object and uploading, updating, or creating new objects in a directory. You can create new Upsert operations, and existing processes with Upsert operations will continue to function. (CON-281)
To learn more about this feature, see the topic Disk (Tech Preview) operation.
Google BigQuery connector
To expand the capability of the connector and account for datasets located outside of the United States and European Union, you can now use the Get Query Results action for a job which references a dataset outside these regions. Additionally, you can continue performing Streaming Insert and Update actions on datasets outside these regions. (BOOMI-39552)
To learn more about this feature, see the topic Google BigQuery operation.
When using Atom workers in an Atom Cloud to perform JMS listener executions in Low Latency mode, the executions are performed sequentially if Maximum Listener Concurrent Executions is in use.
With this release, JMS listener executions in Low Latency mode are performed in parallel and will only execute sequentially when they are configured to do so. (CON-341)
The Kafka connector, formerly a Tech Preview, is Generally Available for production use with this release. (CON-497)
When using the LDAP Import Wizard for the Query operation, you can use the Custom Attributes field to enter additional attributes you want to add to the selected Object Type. This provides you the flexibility to include additional fields supported by your LDAP entries, but not part of the selected Object Type, in operation responses, response profiles, and filters. (BOOMI-35581)
To learn more about this feature, see the topic LDAP operation.
OData Client connector
To reduce the overhead when connecting, the connector supports preemptive authentication. When you select the Preemptive authentication option when making a connection, the connector builds and sends the authorization header to the HTTP server ahead of time in the initial request. (CON-460)
To learn more about this feature, see the topic OData Client connection.
To simplify the connection setup for those wanting to use a private app to integrate with their Shopify instance, the connector supports Access token authentication. (CON-461)
To learn more about this feature, see the topic Shopify connection.
With this release, the Connector SDK is updated to version 1.3.3. For information about the enhancements in this update, see the SDK changelog.
When you create a custom connector, you can choose the tracking direction for write and Execute operations using the
@trackedDocument attribute. Start shape operations remain unchanged. (CON-255)
To learn more about this feature, see the topic Connector descriptor file.
You can create Listen operations for private custom connectors by implementing the
com.boomi.connector.api.ListenConnector interface. Custom connector Listen operations support Low Latency and General mode. (CON-264)
Note: The Listen operation will be a feature of Connector SDK 2.0. Boomi is currently preparing Connector SDK 2.0 for release. In the meantime, to use the Listen operation and access the necessary Connector SDK 2.0 artifacts, contact your Boomi representative.
Connectors implemented using the Connector SDK can have integer fields with a scope of "both" or "browseOnly". During a profile import, entering a value into an integer field with a scope of "both" or "browseOnly" results in an error and prevents completion of the import process.
With this release, entering a value into such a field does not result in an error. For example, if your custom connector uses a field such as Version Number during the profile import, the import process will complete normally. (CON-407)
Master Data Hub
There are technical improvements to the Hub back-end to enable faster loading of golden records in the Golden Records page for domains having reference fields and to improve response time for Query Golden Records requests through the Repository API.
These improvements required a re-release in December of the Repository to Hub clouds. (HUB-600)
MDM connector usage in Hub-to-source integrations
An error occurs in a Hub-to-source integration if HTTP status code 204 (No Content) is returned from the repository in response to an MDM connector Query request.
The connector is updated with this release to report a warning and retry the Query request as expected in this situation. (HUB-454)
The model page neither identifies deleted repeatable fields as Repeatable nor provides their unique IDs.
With this release, the information in question for deleted repeatable fields is displayed or accessible as expected. (HUB-287)
A reference field is erroneously selectable for merging in the Resolve Matching Issues wizard if its value in the quarantined entity matches to the golden record with which to merge.
With this release, the reference field is not selectable for merging in this case. (HUB-445)
When a golden record is created at the same time a golden record it is referencing is created, the reference may not be resolved.
With this release, resolution occurs as expected in all such cases. (HUB-493)
Query Golden Records requests return truncated results if
<view> specifies a reference field. With this release, accurate results are returned.
This fix required a re-release in December of the Repository to Hub clouds. (HUB-620)
In the detail view for a golden record, clicking Next erroneously shows detail for the first record listed in the Golden Records page.
With this release, clicking Next or Preview in a golden record’s detail view has the expected effect. (HUB-285)
To improve Hub performance specific to the handling of inter-domain referencing, there is a change in the repository’s propagation of source record update requests. (HUB-219)
Previously, update requests for golden records with a reference field value that could not be resolved for a particular source were propagated to that source on its channel. Deliverability was not determined until a Fetch Channel Update request occurred for that channel. If a request was determined to be undeliverable due to the enforcement of outbound referential integrity for a reference field with an unresolved value, the request was held.
With this release, propagation of update requests for golden records with a reference field value that could not be resolved for a particular source is conditional upon a request’s deliverability. If a request is determined to be undeliverable due to the enforcement of outbound referential integrity for a reference field with an unresolved value, the request is not propagated and is marked as held. The request is propagated only after a subsequent golden record update resolves the reference field value. Propagation in this situation typically occurs immediately, but a short delay is possible.
To learn more about this feature, see the topic Inter-domain references.
During the resolution of pending references, which occurs in the background upon creation of a golden record, if an error occurs processing an end-dated golden record, the processing of subsequent golden records fails to occur. With this release, resolution processing omits end-dated golden records.
This fix required a re-release in December of the Repository to Hub clouds. (HUB-609)
EDI document handling in multi-node Atom Clouds
As a means of improving the performance of incoming EDI document handling in multi-node Atom Clouds, you can now set the following properties in the Advanced tab of the Properties panel in Atom Management:
Control ID Cache Idle Timeout
Control ID Cache Time to Live
Maximum Cached Control IDs
Maximum Cached Transaction Keys
The first three are Atom properties; the last is an Atom Cloud property. (B2B-745)
To learn more about this feature, see the topic Properties panel, Advanced tab.
The feature described above is coupled with this fix for the Atom, EDI trading partners, and the AS2 Shared Server connector, which prevents database lock and file lock conditions from occurring during the processing of bulk EDI documents in multi-node Atom Clouds. (B2B-619)
That fix caused AS2 listeners to report a connection failure error in the Listeners panel in Atom Management in some cases during the restart of a multi-node Atom Cloud. This error is misleading because the AS2 listener is already successfully connected to a node and operating.
With this additional fix, a connection failure error is not reported when an AS2 listener cannot connect to to an individual node. Instead, a warning is logged.
As of November 23, 2019, an AS2 Shared Server connector update containing this fix is deployed to the Boomi public Atom Clouds. The fix will be generally available with the January 2020 release. If your AS2 listeners experience connection issues during the restart of a multi-node Atom Cloud, request AS2 Shared Server connector v19.11.2 from Support. (B2B-827)
The Known Initiating Partner fields in the RosettaNet v2.0 Service Header — Global Business Identifier, Domain, and Location — can now be set using document properties. The same is true for the Known Initiating Partner Global Business Identifier field in the RosettaNet v1.1 Service Header. This feature enables correct handling of RosettaNet transmissions for which the known initiating partner is different than the sending partner. (B2B-741)
To learn more about this feature, see these topics:
Setting the trading partner using a map function
You can now use the Identifier value in a trading partner document to set the trading partner in a map function regardless of the document standard. Previously only the Identifier value in an X12 document could be used to set the trading partner in a map function. (B2B-687)
To learn more about this feature, see the topic Properties functions.
Trading Partner Management
The Trading Partner Management page () is a central location for viewing, adding, and modifying trading partner and processing group components. This page is particularly useful for users who do not have access to the Build page. Previously it was not possible to sort the components in Trading Partner Management. With this release, you can sort trading partners by name, organization, standard, or communication protocol, and processing groups by name or trading partner count. (B2B-655)
To learn more about this feature, see the topic Trading Partner Management.
Authentication Brokers and API Gateways
The Swagger reference URL for an API is accessible from the API Catalog in the API’s REST tab. (APIM-88)
The Subscriptions page identifies subscriptions that are disabled by the API publisher. (APIM-99)
As a subscriber, you can set Subscription Status in the Subscription Details dialog to enable or disable your subscription. (APIM-106)
To learn more about this feature, see the topic Subscriptions page.
The following information identifies the new features and fixes in Boomi Flow Core releases 1.133.0 and 1.134.0, Tooling release 2.13.0, SAML Service release 1.0.0, System Flows release 1.45.0 and User Interface release 3.11.0.
Flow builders can now confirm the overwriting of existing shared elements when importing packages, as a result of the addition of the
overwriteExisting flag to the Package API’s import endpoints. (CORE-5422)
Password complexity requirements have now been modified to improve password security. (CORE-5411) Passwords must now be at least 9 characters in length and contain at least three out of four of:
At least one uppercase character (A-Z)
At least one lowercase character (a-z)
At least one digit (0–9)
At least one special character
The Draw API now allows retrieval of a service’s describe metadata (configuration values and supported features) and install metadata (configuration values). (CORE-5273)
Dependencies are not checked when deleting map elements. (CORE-5467)
Internal services do not propagate correctly to the user, resulting in the loading spinner being permanently displayed. (CORE-5473)
Nested swimlanes do not enforce the correct authorization hierarchy. (CORE-5262)
Value references for nested lists do not appear in some cases. (CORE-5459)
Value references to
ContentPassword values incorrectly return the content to the API. (CORE-5256)
The new SAML Service enables you to configure flow authentication via a SAML Identity Provider (IdP). (CORE-4963)
The service endpoint URL is
The service allows you to delegate user authentication to an IdP. For example, you can use the service to authenticate a flow using SSO (Single Sign On). Any flow protected via this service acts as a relaying party to accept a SAML assertion package issued by your IdP. This means users can access the flow only after they successfully sign in to their IdP.
When a flow protected by the service is executed, the user is redirected to the IdP to sign in.
Once the user successfully signs in to their IdP, they are redirected to the flow with an assertion package.
The flow determines whether the assertion package is valid by using a certificate. If the assertion package is valid, it is trusted, and the user is signed into the flow.
To learn more about this service, see the topic SAML service.
- Minimum character count not updated from 7 to 9 when resetting a user password. (FLOW-659)
- Value lists cause an error when individual values are corrupted. (FLOW-409)
- No error message is displayed if there is a password mismatch when a user is changing a password. (FLOW-496)
- Unable to list and/or search for encrypted values in the value picker. (FLOW-409)
Flow builders can now install flows from the new Flow Library. The sample flows contained in the Flow Library provide you with quick access to best practice templates for common flow functionality, helping you to get started with creating flows. To learn more about this new feature, see the topic Flow Library. (CORE-5193)
Flow has now been updated with our new Boomi brand. You'll see these changes in the masthead and favicons. Plus, you'll see updated buttons, fonts and colors throughout the platform. Curious to learn more about the new Boomi brand? Take a look at our Brand FAQ. (FLOW-524)
Flow builders can now create a primitive value from the value reference dialogue used when inserting a value into the rich text editor. (FLOW-513)
The Platform status link now points to the Boomi status site. (FUI-241)
Error messages are not displayed when trying to remove the current logged in user from a tenant. (FLOW-446)
Flow builders are not prevented from copying outcomes using the copy/paste map element feature. (FLOW-499)
Player HTML is not displayed in the API tool when making a GET request on the player's endpoint. (FLOW-428)
Requests are not prevented from being made in the API tool when no endpoint has been specified. (FLOW-428)
Tenant names over a certain character length overflow out of the change tenant dropdown box. (FLOW-500)
Text and rich text fields being marked as required in the page editor even if configured as optional. (FLOW-456)
The copy/paste window displayed when right-clicking persists across all flow tabs. (FLOW-415)
Unable to specify object value properties when creating a page condition using the simple page condition tool. (FLOW-423)
When creating a complex value, the selected type overflows off the screen if the value needs to display over a certain number of properties. (FLOW-505)
When editing flow properties, the error message displayed if the system is unable to validate the specified service should be made more user-friendly. (FLOW-511)
Browser autocomplete behaviour is causing the input components date picker to block date selection. (FLOW-504)
Flows fail to load when the browser language preference is set to Canadian English (en-ca). (FLOW-419)
Inline outcomes are not wrapping correctly when displayed on a smaller screen. (FLOW-405)
Nested sub-menu navigation items are not behaving correctly on mobile device. (FLOW-401)
Rich text components are not working correctly when collaboration is enabled in a flow. (FLOW-457)
Rich text editor component assets are occasionally not being loaded from TinyMCE CDN edges. (FLOW-407)
Social feed Follow and Refresh buttons are not working correctly. (FLOW-503)
The className attribute is duplicated on table components. (FLOW-420)
The This Outcome should appear at the top of the Component option is not applied correctly to all components. (FLOW-399)
Selecting this option will now result in the following component behaviour:
Chart: An outcome is triggered by clicking an individual data series or displayed above the component.
Combobox: Displays an outcome above or below the component.
File list: Displays an outcome above or below the component.
File upload: Displays an outcome above or below the component.
Image: Displays an outcome above or below the component.
Input: Displays an outcome above or below the component.
List: Displays an outcome above or below the component.
Presentation: Displays an outcome above or below the component.
Radio Input: Displays an outcome on every row or above the component.
Table: Displays an outcome on every row or above the component.
Text: Displays an outcome on every tile or above the component.
Tile: Displays an outcome on every tile or above the component.
Toggle: Displays an outcome on every tile or above the component.
Unable to delete a flow from the flow list page using the delete icon in a Safari browser. (FLOW-398)
Unnecessary file data requests made by the file upload component, causing a process to be run when the flow leverages an Atomsphere service. (FLOW-397)
Did you find it helpful?
Sorry we couldn't be helpful. Help us improve this article with your feedback.