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

Global navigation

Feature:

  • The recently introduced global navigation menu is improved (DS-2546):

    • Within the Services, Help, and Settings menus, each link includes a description.

    • Within the Services menu, an indicator is added to the active service.

    • The Settings menu introduces icons to indicate your user information and your account information.

  • Note: Global navigation updates are deferred from the September 2020 release and will be included in the October 2020 release.

Password management

Fix:
  • While a password expiration rule was in effect for an account, the rule was not displayed to users who attempted to change their password from the User Information page. With this fix, the rule is displayed, when applicable, to users attempting to change their password. (ADSEC-556)

Atoms, Molecules, and Atom Clouds

Atom message queuing

Feature:
  • You can use a systems management tool with a JMX hook to monitor dead letter queues. (RUN-776)

    To learn more about this feature, see the topic System monitoring with JMX.

Docker installers

Feature:
  • During installation, you can select an environment to which to attach your new Atom, Molecule, or Atom Cloud. (RUN-590)
    Note: This feature was previously deferred from the August 2020 release.

    To learn more about this feature, see the various topics about installing Atoms, Molecules, and Atom Clouds for Linux and Windows and operating systems: Atom setupMolecule setup, and Atom Cloud setup.

Fix:
  • Though the environment variables BOOMI_CONTAINERNAME, INSTALLATION_DIRECTORY, and HOST_INSTALLATION_DIRECTORY are optional, Docker installations failed when these environment variables were not passed. With this fix, optional environment variables no longer cause installation failures. (RUN-923)

Log files

Fix:

  • An error occurred in some cases when downloading large AS2 artifact files. With this fix, AS2 artifact file download requests should succeed regardless of file size. (B2B-980)

Boomi Integration

Packaged Component Deployment

Packaged Component Deployment, originally introduced to Boomi Integration in March 2020, is automatically enabled for all new and existing accounts as of the September 2020 release. All users that currently have the Deployment privilege are also upgraded to have the Packaged Component privilege.

Note: Integration pack publisher accounts will not be converted to use the Packaged Components workflow as of the September 2020 release, but will be converted in a later release.
This workflow leverages the former Package Manager feature in both design and function. Using packaged components, you can apply custom, consistent versioning to deployable components and processes, which provides greater traceability as they are deployed across multiple environments, published to process libraries, or added to integration packs. (INT-279)
Note: Support for Legacy Deployment functionality is removed as of the September 2020 release.

For more information about the new Packaged Component Deployment workflow, see the Boomiverse article How to Prepare for Integration Packaged Component Deployments and the free training course Preparing for Packaged Component Deployment. You can find additional information about this new workflow in the topic Deployment.

API components

Known issue:

Atom Workers panel

Fix:
  • Previously, all Atom workers’ start and shutdown times were displayed as Eastern Time, irrespective of the local time zone. With this fix, local time is displayed. (RUN-274)

Boomi Mobile Manage application

Fix:
  • Performing various actions on the Atom and Process Reporting tabs resulted in errors — for example, when applying filters in Process Reporting. With this fix, interactions with the Atom and Process Reporting tabs no longer result in errors. (ADSEC-852, INT-2584)

Dynamic process properties

Fix:

  • When using JWT authentication, the inuser and x-gateway-roles dynamic process properties were not passed into the header. With this fix, the inuser and x-gateway-roles dynamic process properties are passed into the header when using JWT authentication. (APIM-2168)

Environment extensions

Fix:
  • Process executions ignored the overridden component-based extension fields for Trading Partners and Connections, and erroneously used the component's default values instead. With this fix, all overridden fields take precedence over default values during process execution. (INT-2800)
    Note: This fix was applied in an off-cycle platform release. The defect was introduced in the September 2020 release.

JSON profiles

Feature:

  • In the Data Element tab’s Element Details panel in a JSON profile, you can more easily view, add, activate, and deactivate element qualifiers. Active qualifiers identify values that can be used in instance identifiers.

    • Active qualifiers for an element are presented in a table. If a description was included in the qualifier definition, the description is shown. (B2B-1053)

    • You can add and activate individual qualifiers for an element using the Add Custom Qualifier dialog. To open this dialog, select Add Custom Qualifier in the Actions menu for the qualifiers table. In the dialog, you can optionally specify a description as part of the qualifier definition. (B2B-1060)

    • Use the Choose Qualifier(s) dialog to activate and deactivate qualifiers for an element. To open this dialog, select Choose Qualifier(s) in the Actions menu for the qualifiers table. (B2B-1054)

  • Note: All qualifiers that were added to a profile before this release are automatically activated.

    To learn more about this feature, see the topics Activating qualifiers for a JSON profile data element and JSON profile’s Data Elements tab.

Listener configuration

Feature:

  • When configuring the Listener Startup Mode in the Properties panel, Advanced tab of Atom Management, EFFECTIVE_SINGLE_TENANT_ONLY is available as an option. Setting the Listener Startup Mode to EFFECTIVE_SINGLE_TENANT_ONLY ensures connector listeners built with the Connector SDK start in both Atom workers and the main JVM. (CON-1777)

    Note: This feature has companion changes covered in the Connectivity section of these release notes.

Fix:

  • When setting the Listener Startup Mode to MULTI_TENANT in the Properties panel, Advanced tab of Atom Management, the property defaulted to NONE. Additionally, the only way to set the property to MULTI_TENANT was to not select an option. With this fix, your selection is honored after you save the properties and restart the Atom Cloud. You can also directly add the value to the container.properties file and restart the Atom Cloud. (CON-1511)

    Note: This fix has companion changes covered in the Connectivity section of these release notes.

    As a part of this fix, the MULTI_TENANT option is renamed as MULTITENANT_ONLY to distinguish it from the new EFFECTIVE_SINGLE_TENANT_ONLY option.

Shared Web Server panel

Fix:
  • If you did not set a Port on the Shared Web Server panel, one was not automatically configured. With this fix, a default port of 9090 is configured. (APIM-2212)

XML profiles

Feature:

  • In the Data Element tab’s Element Details panel in an XML profile, you can more easily view, add, activate, and deactivate element qualifiers. Active qualifiers identify values that can be used in instance identifiers.

    • Active qualifiers for an element are presented in a table. If a description was included in a qualifier definition, the description is shown. (B2B-1053)

    • You can add and activate individual qualifiers for an element using the Add Custom Qualifier dialog. To open this dialog, select Add Custom Qualifier in the Actions menu for the qualifiers table. In the dialog, you can optionally specify a description as part of the qualifier definition. (B2B-1060)

    • Use the Choose Qualifier(s) dialog to activate and deactivate qualifiers for an element. To open this dialog, select Choose Qualifier(s) in the Actions menu for the qualifiers table. (B2B-1054)

  • Note: All qualifiers that were added to a profile before this release are automatically activated.

    To learn more about this feature, see the topics Activating qualifiers for an XML profile element or attribute and XML profile’s Data Elements tab.

Fixes:

  • When importing a profile from a RosettaNet schema, the schema for v02.03.00 of message type 3A4 - Request Purchase Order was not available for selection in the XML Import Wizard. With this fix, the schema for that version is available for selection. (B2B-250)

  • Applying edits to a profile in its Types tab resulted in the disappearance of an element from the profile’s Data Elements tab. With this fix, no elements disappear from the tab. (B2B-1190)

    Note: This fix was applied in an off-cycle platform release. The defect was introduced in the September 2020 release.

AtomSphere API and Partner API

Account Single Sign-on Configuration object

Fix:
  • Previously, the nameIdPolicy attribute was erroneously omitted from responses to Get and Update requests. With this fix, nameIdPolicy is included in Get and Update responses, as expected. (ADSEC-808)

Environment Extensions object

Partial extension updates, formerly a Tech Preview, is Generally Available for production use with this release. (INT-2573)

Feature:
  • You can use partial updates to update process property values at the individual property level. (INT-2548)

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

Fixes:
  • The useDefault attribute in Get and Query requests always returned a false value for connection, trading partner, and shared communication extensions, even when a field was not overridden. With this fix, the correct value for useDefault is returned in all cases. (INT-2559)

  • The value attribute was erroneously omitted from Get and Query responses for process property components. With this fix, the value attribute is included for process property components, as expected. (INT-2558)

Connectivity

OAuth 2.0 authentication

Fix:

  • When using the OAuth 2.0 authentication type and client credentials with any connector supporting this grant type, the connectors do not utilize the Atom’s trust store when normal or forked executions in Atoms, Molecules, and Atom Clouds attempt to connect to the Access Token URL. To successfully connect, you must manually load the required certificates into the Java keystore (java/jdk<version>/jre/lib/security/cacerts) using the keytool utility. The location of your Atom’s trust store may be different than the location of your Java keystore. With this Atom software fix, normal and forked executions in Atoms, Molecules, and Atom Clouds utilize the certificate in the Atom’s trust store and successfully connect to the Access Token URL. (CON-41)

    Note: The connectors did not require an update for this fix.

SDK connectors

Features:

  • SDK connectors with dynamic operation properties enabled display the Dynamic Operation Properties tab on the Connector shape. Dynamic operation properties are document-level override values passed into the Connector shape to modify the value set in the operation component. These values only affect the shape’s operation. (CON-818)

    Note: This feature is only available when a connector developer enables it for an SDK connector. As of the September 2020 release, no connectors make use of this feature.

    To learn more about this feature, see the topics Connector descriptor file and Connector shape.

  • Secure Listen can be enabled in Atom Clouds to support connectors built using the Connector SDK. This feature lets you deploy connectors with Listen operations to Atom workers on an Atom Cloud so your processes can listen and execute from the Atom Cloud environment using these workers. Connector listeners running on Atom workers appear in the Listeners tab of Atom Management so you can pause, resume, and restart them similar to other listeners. (CON-579)

    Note: This feature has companion changes covered in the Boomi Integration section of these release notes. Additionally, the Microsoft Azure Service Bus connector and Salesforce Platform Events connector already feature multi-tenant support for private Atom Clouds and Molecules and are not affected by these changes.

    To learn more about this feature, see the topic Implementing Secure Listen.

  • When Secure Listen is enabled, connector listeners built using the Connector SDK and running on Atom Clouds can utilize Custom Libraries on a per account basis. (CON-1703)

  • To support Secure Listen, the template policy file for Atom workers, procworker-HIGH.policy.template, is updated, allowing Atom workers to update necessary files even when there is a security policy on the Atom Cloud. (CON-1717)

    To learn more about this feature, see the topic Maintaining security permissions for custom security policy files.

Atom Queue connector

Feature:
  • The new Consume from Dead Letter Queue? (Point-to-Point Only) setting for Listen and Get operations enables retrieval of dead letters from a Point-to-Point message queue. (RUN-775)

    To learn more about this feature, see the topic Atom Queue operation.

Flow Client connector

Feature:

  • You can select the player to use upon launching a flow. (FLOW-717)

Kafka connector

Features:

  • With the new Listen operation, you can subscribe to a topic, poll the message broker on a regular basis, and retrieve batches of messages from the Kafka server. You can determine how often the message broker is polled, how often the Listen operation waits before starting to poll, specify the maximum number of messages to return for a single poll, and select the delivery policy to guarantee message delivery between the producer and consumer. The flexibility offered by the operation lets you build processes and consume messages in real-time as they are received by a topic. (BOOMI-42594)

    To learn more about this feature, see the topic Kafka operation.

  • Prior to the Tracking Direction feature implementation for connector operations in the November 2019 release (CON-255), the Kafka Consume operation set the default tracking direction to Input Documents and it could not be changed. With this feature, Tracking Direction for Consume is appropriately set by default to Output Documents so you can view documents and their properties in Process Reporting. (CON-1771)

Microsoft Dynamics 365 for Customer Engagement connector

Feature:

  • Previously, this connector’s Query operation could process and return only one page of results when the server paginated the response having a predefined page size. For example, if the server’s page size was 5,000 and the connector’s query resulted in 10,000 records, only the first 5,000 records were returned, and there was no way to obtain all 10,000 records in a single query. With this feature, the connector transparently manages server-side pagination, consumes all available pages of results, and returns the expected number of records for a given Query operation. (CON-1413)

Microsoft Dynamics 365 for Finance and Operations connector

Feature:

  • Previously, this connector’s Query operation could process and return only one page of results when the server paginated the response having a predefined page size. For example, if the server’s page size was 5,000 and the connector’s query resulted in 10,000 records, only the first 5,000 records were returned, and there was no way to obtain all 10,000 records in a single query. With this feature, the connector transparently manages server-side pagination, consumes all available pages of results, and returns the expected number of records for a given Query operation. (CON-1414)

MongoDB connector

Feature:

  • The MongoDB connector allows you to connect to MongoDB and use a process to Get, Query, Create, Update, Upsert and Delete the data stored in the MongoDB database. (CON-1812)

    To learn more about this feature, see the topic MongoDB connector.

OData Client connector

Feature:

  • Previously, this connector’s Query operation (v4.0) could process and return only one page of results when the server paginated the response having a predefined page size. For example, if the server’s page size was 5,000 and the connector’s query resulted in 10,000 records, only the first 5,000 records were returned, and there was no way to obtain all 10,000 records in a single query. With this feature, the connector transparently manages server-side pagination, consumes all available pages of results, and returns the expected number of records for a given Query operation. (CON-1412)

Oracle E-Business Suite V2 (Tech Preview) connector

Feature:

  • This connector was released off-cycle into production after the September, 2020 release. The Oracle E-Business Suite V2 (Tech Preview) connector supports PL/SQL execution, Interface Tables, and Java Bean Services using the REST Locator enabled via the Oracle Integrated SOA Gateway executed in a local Atom and Molecules. (CON-1950)

    To learn more about this connector, see the topic Oracle E-Business Suite V2 (Tech Preview) connector.

Salesforce connector

Feature:

  • Previously, when using Salesforce Bulk API v2 to batch and process data, the response payload was processed in a network stream. In some cases this resulted in decreased or delayed data transfer. With this feature, the complete response payload is collected in a temporary output stream (disk-based storage with a heap buffer) to ensure more efficient data transmission from the network. (CON-1711)

SAP Cloud for Customer connector

Feature:

  • The SAP Cloud for Customer connector is renamed as SAP Business ByDesign and can be used to connect and integrate with SAP Business ByDesign. This is a non-functional change. (CON-1839)

    To learn more about this feature, see the topic SAP Business ByDesign connector.

SAP JCo V2 (Tech Preview) connector

Fix:

  • Setting the value of the Listener Connection CountSAP Maximum Idle Connections, and SAP Maximum Active Connections fields in the connector or environment extension resulted in the following error: java.lang.Long cannot be cast to java.lang.String. With this fix, these fields can be set, as expected. (CON-1917)

SFTP V2 (Tech Preview) connector

Fix:

  • Using Public Key authentication failed and returned a connection error due to an invalid internal identifier lookup. With this fix, this type of authentication works as expected, enabling successful connection. (CON-1919)

Web Services Server connector

Fix:

  • The array type was not being shown in the JSON profile. With this fix, the array type is shown in the JSON profile. (APIM-1910)

    Note: This fix has companion changes covered in the API Management section of these release notes.

Connectivity development

Connector SDK

Features:

  • With this release, the Connector SDK is updated to version 2.8.0. For information about the enhancements in this update, see the SDK changelog.

  • SDK connector developers can create connectors with dynamic operation properties. Dynamic operation properties are document-level override values passed into the Connector shape to modify the value set in the operation component. These values only affect the shape’s operation. (CON-818)

    To learn more about this feature, see the topics Connector descriptor file and Connector shape.

  • The Connector SDK supports text areas with higher character limits and greater visibility. To enable this functionality in a connector, developers can declare the textarea value for an input string field’s @displayType attribute. (CON-1505)

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

Master Data Hub

Transactional workflow

Fix:

  • When the same entity was contributed multiple times and the original contribution resulted in creation of a golden record containing a multiple-item collection, the subsequent contributions were in some cases erroneously processed as golden record updates. With this fix, in this scenario the subsequent entity contributions are correctly processed as null operations. (HUB-908)

B2B/EDI Management

EDI profiles

Feature:

  • In the Data Element tab’s EDI Element Details panel in an EDI profile, you can more easily view, add, activate, and deactivate element qualifiers. Active qualifiers identify values that can be used in instance identifiers.

    • Active qualifiers for an element are presented in a table. Each qualifier is identified as Standard or Custom. If a description was included in the qualifier definition, the description is shown. (B2B-1053)

    • Use the Choose Qualifier(s) dialog to activate and deactivate qualifiers for an element. To open this dialog, select Choose Qualifier(s) in the Actions menu for the qualifiers table. In the dialog, you can select one or more standard element values from X12 specification versions 4030–6020 for activation as Standard qualifiers. (B2B-1054)

      Note: This capability will be added in future releases for other supported X12 versions and other supported EDI standards. In addition, descriptions will be included in Standard qualifier definitions.
    • In the Choose Qualifier(s) dialog, you can also select custom values for activation as Custom qualifiers. To define a Custom qualifier for an element, use the Add Custom Qualifier dialog. To open this dialog, select Add Custom Qualifier in the Actions menu for the qualifiers table. In the dialog, you can optionally specify a description as part of the Custom qualifier definition. When the Custom qualifier is defined, it is automatically activated. (B2B-1060)

  • Note: All qualifiers that were added to a profile before this release are automatically activated as Custom qualifiers, regardless of whether their values conform to an EDI standard and version.
    Note: Atom software is updated to support this feature. (B2B-1147)

    To learn more about this feature, see the topics Activating qualifiers for an EDI profile data element and EDI profile’s Data Elements tab, element details.

RosettaNet document handling

Feature:

  • You can set the Signal Version field in the RosettaNet Service Header using document properties. (B2B-1113)

    Note: This feature required an update to the RosettaNet EDI connector.

    To learn more about this feature, see the topic Trading Partner information document properties.

Fix:

  • In the XML declaration in RosettaNet message headers, the standalone attribute was erroneously populated with the Yes value. With this fix, the standalone attribute is omitted from the XML declaration, which equates to the No value. (B2B-1138)

    Note: This fix required an update to the RosettaNet EDI connector.

API Management

Authentication Brokers and API Gateways

Fixes:

  • If you selected a JWT Authentication on the Developer Portal Settings panel of an API Gateway from the Configure Server > Gateway page, an extraneous error message that you did not save your changes displayed whether or not your changes were saved. With this fix, the extraneous error message does not appear. (APIM-2076)

  • If a client timed out before the API request received a response from the API Gateway, the request was not added to the access log. With this fix, all API requests are added to the access log, even if the client times out before the API request receives a response from the API Gateway. (APIM-2022)

Developer Portal

Features:

  • Developer Portal welcome message improvements are introduced:
    • The ability to search the content of your welcome message is added. (APIM-1996)

    • You can include description lists in the welcome message on your portal home page. (APIM-1415)

    • The text that you enter in the welcome message is automatically spell-checked. (APIM-1992)

    To learn more about this feature, see the topic Publish screen.

Swagger Visualization Portal

Fix:

  • The Swagger Visualization Portal did not show the array type in the JSON profile. With this fix, the Swagger Visualization Portal shows the array type in the JSON profile. (APIM-1910)

    Note: This fix has companion changes covered in the Connectivity section of these release notes.

Boomi Flow

The following information identifies the new features and fixes in Boomi Flow releases Azure Service 1.3.0, Core 1.164.0, 1.165.0, 1.166.0, 1.167.0, 1.167.1, 1.168.0, Hub Service 1.3.0, System Flows 1.58.0, Tooling 2.29.0, 2.30.0, 2.31.0, and User Interface 3.27.0, 3.28.0.

Note: The Boomi Integration Flow Client connector is updated in this release. For information about the update, see the Connectivity section of these release notes.

Azure Service

Feature:
  • Guest users can authenticate with Azure AD, allowing applications to be configured as single-tenant or multi-tenant. To support this capability, a new optional Tenant configuration value is added to the service, to indicate which Azure tenant is used for the authentication. The Tenant configuration value can be set to either the Tenant_ID or the Org_domain — for example, ‘manywho.com’. If the Tenant configuration value is not provided, the flow has multi-tenant access, but if the Tenant configuration value is provided, only the specified tenant is used for the authentication. (FLOW-2091)

Core

Feature:
  • An additional objectData field is added to the translation POST endpoints to allow the posting of updated translations for complex object types ContentObject/ContentList. (FLOW-2315)

  • API modifications have been made to support future Multi-cloud Runtime functionality, allowing Organization Administrators to add, edit, and delete runtime connections. (FLOW-1441, FLOW-1445, FLOW-1446, FLOW-2205, FLOW-2208)

  • Modifications in support of future Multi-cloud Runtime functionality. (FLOW-2207, FLOW-2246)

Fixes:
  • Deleting a page layout component did not also delete translation values defined for the component. With this fix, deleting a page layout component also deletes any translation values defined for the component. (FLOW-2247)

  • The JSON data structure for ContentList objects was incorrectly passed when performing a POST request to the translation API endpoint. With this fix, POST requests to the translation API endpoint that contain ContentList data correctly pass the JSON data structure. (FLOW-2363)

  • When using the GET /api/translate/1/element/value/{id} API translation endpoint, the endpoint incorrectly returned values for complex types (ContentObject/ContentList) as Base64-encoded strings. With this fix, the API response correctly populates the objectData field with the deserialized object data. (FLOW-2199)

Hub Service

Fix:
  • Boolean values were not being passed correctly to Master Data Hub using the Hub service. With this fix, Boolean values are passed correctly. (FLOW-2272)

System Flows

Fix:
  • Optimization improvements have been made to the Select Page drop-down menu on the Page configuration panel. With this fix, slow population of the drop-down menu in tenants with extremely large numbers of page layouts does not occur. (FLOW-2214)

Tooling

Feature:
  • The forgotten password functionality in Boomi Flow is updated to match the style of the AtomSphere platform. If you have forgotten your password, click Forgot Password?. Then enter the email address for which to reset the password in the Password Reset form. (FLOW-2308)

Fixes:
  • Font and text styles were not consistently applied, resulting in an inconsistent user experience. With this fix, font and text styles are aligned throughout the application to ensure a consistent user experience. (FLOW-1316)

  • When changing tenant, if the tenant search on the Select a Tenant form did not return any matching tenants, the error message erroneously directed the user to Boomi Support. With this fix, the error message informs the user that they should adjust their search term or contact their administrator. (FLOW-2228)

User Interface

Fixes:
  • Client-side validation using a regular expression that did not allow for a null input would prevent the user from advancing in the flow if they left an optional validation field blank. With this fix, the user can advance in a flow if they leave an optional validation field blank, even if the regular expression does not allow for a null input. (FLOW-2129)

  • Combobox, Select, and Toggle page components were incorrectly displayed on a page in the layout order in which they were added to containers of either the inline or column layout type. Input boundaries were also not respected on a page, resulting in some page components overlapping. With this fix, the ordering of these page components matches the layout order in the page layout, and overlapping of page components does not occur. (FLOW-2101)

  • Labels on Toggle components were restricted to a width of 60px, and Outcomes from Select components had incorrect spacing. With this fix, labels on Toggle components are not restricted in width, and Outcomes from Select components have spacing consistent with other component Outcomes. (FLOW-2381)