These release notes identify the new features and bug fixes slated for release in AtomSphere in January 2021. 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

Sign-in

Fix:

  • An error occurred in some cases when attempting to sign in to an account for which two-factor authentication is required and either the account usage agreement option or the concurrent session limitation option is enabled. With this fix, sign-in works as expected. (ADSEC-985)

    This fix is not available for use during Release Control.

Boomiverse access

Fix:

  • Users of Google Chrome and Microsoft Edge versions 85 or later could not successfully sign in to Boomiverse with AtomSphere platform credentials from https://community-dellboomi.cs66.force.com/community/s/login/. With this fix, Chrome and Edge users can successfully sign in to Boomiverse with AtomSphere platform credentials. (ADSEC-957)

    This fix is not available for use during Release Control.

Atoms, Molecules, and Atom Clouds

Atom workers

Fixes:

  • 10 percent of Atom workers in an Atom Cloud erroneously restarted on every attachment after 12 hours, rather than 10 percent of total Atom workers across the Atom Cloud. With this fix, Atom workers restart as expected. (RUN-1286)

    This fix is available for use during Release Control.

  • Some executions failed as a result of an Atom worker being shut down. With this fix, executions no longer fail in this scenario. (RUN-647)

    This fix is available for use during Release Control.

Java security compatibility

Features:

  • To maintain compatibility with Java 1.8.0_271 version upgrades, the security property jdk.disabled.namedCurves is set to blank for 2019.01 security compatibility and earlier. This setting re-enables Weak named curves that Java disabled in version 1.8.0_271. (RUN-1424)

    This feature is available for use during Release Control.

  • For Atoms that are installed after the January 2021 release, the security property com.boomi.container.securityCompatibility is set to 2021.01 by default. You can manually set this property to 2021.01 for previously installed Atoms. (RUN-1425)

    This feature is not available for use during Release Control. 

Java upgrades

Feature:

  • The Atom, Molecule, and Atom Cloud installers and updaters, and the corresponding Docker images, are modified to use Java 1.8.0_271. Boomi Atom Clouds are also modified to use Java 1.8.0_271. (RUN-1418, RUN-1419, RUN-1420)

    During Release Control, the upgrade is applied only to the Test Atom Clouds.

Runtime release

Feature:

  • The process for releasing Atom patches is improved to prevent an Atom from taking the release again if it is already on the latest version. (RUN-1137)

    This feature is not available for use during Release Control. 

Singleton Listen operations

Features:

  • A new com.boomi.container.bounded.listen.refresh.interval custom container property enables automatic failover (default of 5 minutes) for Singleton Listen operations to ensure the listener is always up and running. If a listener node fails and goes offline, another available node in the Molecule or Atom Cloud ensures the listener is available. (CON-1930)

    This feature is available for use during Release Control.

  • When attempting failover, refreshing a Singleton Listen operation on a node prevents a different Singleton Listen operation from starting on the same node. With this feature, refreshing an instance of a Singleton Listen operation on a node is less likely to impact other Singleton Listen operations when attempting to start the listener on a new node. (CON-2208)

    This feature is available for use during Release Control.

  • Singleton Listen operations currently obtain a file lock, and the lock file is written to a dedicated bounds directory (<ATOM_HOME>/bounds), indicating where the service starts. With this feature, file locks for multi-tenant Atom Clouds are written to an account subdirectory of the <ATOM_HOME>/bounds directory. The subdirectory name is the ID of the account deploying the listener. File locks for Atoms, Molecules, and single-tenant Atom Clouds are written to the root bounds directory (<ATOM_HOME>/bounds), and an account subdirectory is not created. (CON-2102)

    This feature is available for use during Release Control.

Boomi Integration

API Service components

Fix:

  • If you did not specify a Resource Path/Object was appended to the Endpoint Path for the REST endpoint within the Configure APIs and Applications > Deployed APIs page in API Management. However, the endpoint did not actually include the appended /Object. With this fix, /Object is not appended to the Endpoint Path for the REST endpoint within the Configure APIs and Applications > Deployed APIs page in API Management when you do not specify a Resource Path for the endpoint. (APIM-2504)

    This fix is not available for use during Release Control.

Audit logs

Feature:

  • The WHITELISTING modifier is changed to TRUSTEDIP for newly-generated audit log entries. This change is part of the Boomi-wide initiative to remove racist and exclusionary terminology from the platform and content. (ADSEC-919)

    Note: Historical audit log entries with the WHITELISTING modifier that were generated before the January 2021 release date remain as is.

    This feature is not available for use during Release Control. 

Environment extensions

Fix:
  • Editing capability was erroneously removed from the Client SSL Certificate and Trusted SSL Server Certificate fields in the Connection Settings tab. With this fix, editing capability is restored. (INT-2916)

    This fix is not available for use during Release Control.

JSON profiles

Features:

  • When a JSON profile is created via connector browsing or API Service, the Field Length Validation option is automatically selected when either the Min Length or Max Length field is populated in the Data Elements tab. (INT-2966)
    Note: This configuration is not applied when re-importing an existing JSON profile to ensure backward compatibility.

    This feature is not available for use during Release Control. 

  • When a JSON profile is created via connector browsing or API Service, if in the JSON schema an attribute’s format is “date-time”, “date”, or “time”, the resulting profile element is configured as a Date/Time type with a respective Date Format in the Data Elements tab. (INT-2954)
    Note: This configuration is not applied when re-importing an existing JSON profile to ensure backward compatibility.

    This feature is not available for use during Release Control. 

Fix:

  • An error message was displayed in the Add/Edit Instance Identifier dialog upon an attempt to add an instance identifier to a repeating array element, identifying by the same qualifier value from different child elements. With this fix, it is possible to add an instance identifier to a repeating array element, identifying by the same qualifier value from different child elements. (B2B-1250)

    This fix is not available for use during Release Control.

XML profiles

Fix:

  • An error message was displayed in the Add/Edit Instance Identifier dialog upon an attempt to add an instance identifier to a repeating element, identifying by the same qualifier value from different child elements or attributes. With this fix, it is possible to add an instance identifier to a repeating element, identifying by the same qualifier value from different child elements or attributes. (B2B-1250)

    This fix is not available for use during Release Control.

AtomSphere API and Partner API

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

Environment object

Feature:

  • Query processing performance is enhanced to reduce query response time. (INT-2852)

Execution Request object

Feature:

  • The new Execution Request object leverages the Execute Process operation giving users the ability to programmatically and asynchronously execute a process on a given Atom by means of a Create operation. (INT-2410)

    The new object provides a requestId allowing the caller to find the execution record that was created from their original request to reliably determine the outcome of a requested execution. Additionally, the object provides improved validation and the ability to pass both dynamic and regular Process Property component properties in the request.

Packaged Component object

Feature:

  • Query processing performance is enhanced to reduce query response time. Additionally, error messaging is added for the case of an attempt to deploy a deleted packaged component. (INT-2820)

Connectivity

OAuth 2.0 authentication and extensions

Fix:

  • When generating an access token for a connection utilizing the Authorization Code or Resource Owner Credentials grant types requiring an OAuth 2.0 scope, the access token is successfully generated. However, when using the Environment Extensions dialog to generate a new access token having the same details as the initial connection, an error occurred in some cases when the scope was required. This is due to the scope not being persisted across connections. With this fix, the scope is persisted as expected, and the access token is generated successfully. (CON-1998)

    This fix is available for use during Release Control.

Agiloft CLM connector

Feature:

  • The new Agiloft CLM connector simplifies the automation of a wide range of business processes, from simple data export to complex inter-application workflows, such as contract lifecycle management and proposal management. (CON-2133)

    This connector is available for use as of Release Control.

    To learn more about this connector, see the topic Agiloft CLM connector.

Coupa connector

Feature:

  • Previously, in certain cases the Query operation returned duplicate records. With this feature, queries request data from Coupa, ordered by Id, to prevent the same record from being returned by the Coupa API in more than one page. (CON-2345)

    This feature is available for use during Release Control.

JMS connector

Fix:

  • The JMS connection was inadvertently updated to have a customProperty field type for a connection act as the JMS Properties. The JMS Properties in the connection do not support decryption, so any new connections having encrypted key-value pairs resulted in the value not being utilized and encrypted as expected. With this fix, the ability to encrypt key-value pairs for a connection is removed. (CON-2275)

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

    This fix is not available for use during Release Control.

Microsoft Azure Cosmos DB connector

Fix:
  • Updating a record fails, with a record not found 404 error, when the ID field contained within the update request object is positioned before the partition key (request ID) field. With this fix, the ID and partition key fields do not have any inherent dependency in the order in which they occur. (DBOETKZW-2416)

    This fix is available for use during Release Control.

Microsoft Teams (Tech Preview) connector

Feature:

  • The new Microsoft Teams (Tech Preview) connector enables operations on Microsoft Teams resources — for example, Team, Channel, Chat message, Team member. The connector supports the Create, Get, Manage, Execute, List, and Delete operations. (CON-2317)

    This connector is available for use as of Release Control.

    To learn more about this connector, see the topic Microsoft Teams (Tech Preview) connector.

Oracle E-Business (EBS) connector

Fixes:

  • Processes containing an Oracle EBS Query operation did not result in an error, as expected, when a database error occurred — for example, invalid connection settings. Instead, the process containing the operation executed successfully, stopped at the Connector shape, and did not continue, and just logged a message in the container log. With this fix, the Query operation provides a Fail on database errors option. This option is selected by default but is not effective for existing processes unless the operation is opened and saved and the process is then redeployed. Deselect this option for a Query operation that relies on the previously existing behavior. (CON-1429)

    This fix is not available for use during Release Control.

  • The Import Wizard did not handle errors appropriately while browsing the Query and Execute operations, resulting in unexpected behavior. In some cases, a misleading message appeared, indicating that no object types were found — for example, when invalid connection credentials were provided. In other cases, browsing was successful even when there was a database error, resulting in generation of an invalid profile. With this fix, the Import Wizard correctly handles errors, and when appropriate, provides a meaningful error message to aid in troubleshooting. (CON-2259)

    This fix is available for use during Release Control.

Oracle E-Business Suite V2 (Tech Preview) connector

Feature:

  • In this release, there are several enhancements to the connector:
    • Support is added for using the Oracle Database Connector Descriptor (DBC) to connect to Oracle EBS databases.

    • Existing operations associated with REST APIs (QUERY and EXECUTE) are renamed to REST_EXECUTE and REST_QUERY to support the following enhancements and future flexibility:

      • PLSQL_EXECUTE supports execution of PL/SQL Store Procedures available in the Oracle Integration Repository.

      • PLSQL_QUERY supports Query, an inbound operation, and performs SQL SELECT queries against the database schema, allowing Boomi Integration to look up a single object record based on specific search criteria.

    • Support for the TIMESTAMP data type and correct handling of empty XML elements leverage a recent update to the legacy Oracle E-Business connector.
  • (CON-2322)

    These enhancements are not available for use during Release Control.

SAP aXis connector

Feature:

  • The new SAP aXis connector is part of the Boomi aXis for SAP offering, providing easy access to SAP data by discovering services that expose business data so it can be extracted from SAP. (CON-1719)

    This connector is available for use as of Release Control.

    To learn more about this connector, see the topic SAP aXis connector.

SFTP V2 connector

Feature:

  • In this release, there are several enhancements to the connector:
    • The List operation not only lists the files and folders in the root folder, but also from one level deeper. Additionally, the List operation response includes file size.

    • Support is added for connection pooling — the number of connections in the pool — with a default of 10.

    • Flexible file naming configuration options are provided, allowing users to create unique temporary and target file names using predefined parameters — for example, $DATE, $BASE, $EXTENSION. Use the options to ensure file uniqueness and to avoid overwriting files when many are being written in a short time span.

    (CON-2318)

    These enhancements are not available for use during Release Control.

Connectivity development

Connector SDK

Features:

  • With this release, the Connector SDK is updated to version 2.9.0. (CON-2363)

  • SDK connectors with custom properties operation fields can be overridden on the Dynamic Operation Properties tab of the Connector shape. This feature extends previously existing functionality which limited override capability to simple operation fields (strings, integers, and Booleans). (CON-1985)

    This feature is not available for use during Release Control. 

  • A previous release introduced Singleton Listen operations, for which the default setting for the com.boomi.container.bounded.listen.enabled container property was false. With this feature, the default property setting for Atoms, Molecules, and single-tenant Atom Clouds is true. The previously existing behavior and default property setting of false remains for multi-tenant Atom Clouds. (CON-1718)

    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.

Master Data Hub Platform API

Features:

  • You can programmatically retrieve a list of the Hub Clouds accessible to your account. (HUB-717)

  • You can programmatically create a repository on a Hub Cloud accessible to your account. (HUB-714, HUB-842)

  • You can programmatically create a source under your account. (HUB-497)

  • You can programmatically add a staging area for a source attached to a universe (domain). (HUB-501, HUB-853)

Quarantine entry resolution

Fix:

  • Where an incoming entity was quarantined as a potential duplicate and the quarantine entry was then resolved by selectively merging some of the fields from the entity into the matching golden record, if Channel updates contain for the contributing source’s channel was set to Changed Fields Only, the update request propagated on that channel erroneously contained only the fields in the quarantined entity. With this fix, in this scenario the propagated update request contains only the merged fields, as expected. (HUB-1124)

Stewardship

Fix:

  • A low memory condition occurred on the USA East Hub Cloud during processing of a purge request for an end-dated golden record having a large number of historical versions, resulting in the automatic restarting of some of the Hub Cloud’s nodes. With this fix, purge requests for end-dated golden records are handled properly, regardless of the number of historical versions. (HUB-1195)

    Note: This fix was applied to Hub Clouds during Release Control.

Transactional workflow

Fixes:

  • Where processing of an incoming entity resulted in the establishment or re-establishment of a link from a matching golden record to the specified source entity, without there being an update to that golden record, an update request was not propagated to the contributing source on its channel. With this fix, when a link from a matching golden record to the specified source entity is established or re-established, an update request is propagated to the contributing source regardless of whether the golden record is updated. (HUB-1108, HUB-1114)

  • The defect scenario necessitating this fix started with processing of an incoming entity that resulted in both a golden record update and a change of the golden record’s existing link to the specified source entity from a different source entity, due to the presence of the grid attribute in the incoming entity. An entity from the same source was then contributed to change the link back to the previous source entity or to some other entity and to apply the data from the golden record’s previous version. The link was updated as expected, but the field values in the entity from the golden record’s previous version were ignored. With this fix, in this scenario field values in the entity from the golden record’s previous version are applied in the golden record update, as expected. (HUB-1163)

B2B/EDI Management

EDIFACT trading partners

Fix:

  • Previously, it was not possible to set Release Number (UNH02:3) to version 16A or later. With this fix, versions 16A and later are added to the versions available for selection. (B2B-1109)

    This fix is not available for use during Release Control.

EDI profiles

Feature:

  • You can import values defined for elements in the EDIFACT standard as standard qualifiers to data elements in EDIFACT EDI profiles. (B2B-1056)

    This feature is not available for use during Release Control. 

Fixes:

  • It was not possible to import segments defined as needed for creating an EDIFACT-compliant profile for Version D, Release 97A and Message Type DELFOR messages. With this correction to the template used to import segments for this version, release, and message type, segments available for import are defined in a manner consistent with the standard. (B2B-247)

    This fix is not available for use during Release Control.

  • It was not possible to import the CPS segment for Version D, Release 93A and Message Type DESADV messages. With this correction to the template used to import segments for this version, release, and message type, the CPS segment is available for import. (B2B-1141)

    This fix is not available for use during Release Control.

  • An error message was displayed in the Add/Edit Instance Identifier dialog upon an attempt to add an instance identifier to a loop or segment, identifying by the same qualifier value from different child elements. With this fix, it is possible to add an instance identifier to a loop or segment, identifying by the same qualifier value from different child elements. (B2B-1250)

    This fix is not available for use during Release Control.

SFTP communication method

Feature:

  • You can configure a proxy for SFTP communication in trading partners, “My Company” trading partners, and shared Communication Channel components. Selecting the Use Proxy option in the component configuration dialog reveals the Choose Proxy Type list and, depending on the selected proxy type, fields for setting the Proxy HostProxy PortProxy User, and Proxy Password. (B2B-1232)

    This feature is not available for use during Release Control. 

API Management

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

Authentication Brokers and API Gateways

Features:

  • The API Gateway’s Gateway Settings panel is renamed to the Location Settings panel. (APIM-2486)

  • You can set a custom API Gateway com.boomi.container.apigateway.init.param property to include -javaagent:jar_file_path, where jar_file_path is the full path to your user-defined Java agent, in order to monitor and profile the API Gateway sidecar JVM (Java Virtual Machine). (APIM-2497)

Fix:

  • When calling an API through the API Gateway that used a Basic Authentication Source, an error was returned if the user had a password containing a colon (:). With this fix, a Basic Authentication Source password that contains a colon (:) is accepted and will not return an error when the API is called through the API Gateway. (APIM-2604)

Deployed APIs

Fix:

  • If you did not specify a Resource Path for the REST endpoint in an API Service component within Boomi Integration/Object was appended to the Endpoint Path for the REST endpoint within the Configure APIs and Applications > Deployed APIs page. However, the endpoint did not actually include the appended /Object. With this fix, /Object is not appended to the Endpoint Path for the REST endpoint within the Configure APIs and Applications > Deployed APIs page when you do not specify a Resource Path for the endpoint in an API Service component within Boomi Integration. (APIM-2504)

Developer Portal

Features:

  • The environment name is added to the API Catalog page within your Developer Portal. (APIM-68)

  • You can specify a Published Name for your environments on the Publish screen under the Developer Portal's Environments panel. The Published Name is the name published externally on your Developer Portal. (APIM-2115)

Boomi Flow

The following information identifies the new features and fixes in Boomi Flow Engine 2020-11-16.1029, 2020-11-23.1702, 2020-11-26.1559, and Tooling 2.40.0, 2.40.1.

Engine

Features:
  • Modifications support future Multi-cloud Runtime functionality. (FLOW-2602)

  • Modifications support future Organizations functionality. (FLOW-2731, FLOW-2696, FLOW-2686)

Fixes:
  • Audit logs that use the /api/metrics/1/search? API endpoint did not include details of tenant creation. With this fix, details are available for tenant creation events (such as subtenant creation), including details of the user that created the tenant and the date and time the tenant was created. (FLOW-2539)

  • Duplicate dependencies and dependencies without names were erroneously included in the dependencies table displayed when deleting items from a tenant. With this fix, incorrect dependency entries are not included in the dependencies table. (FLOW-2408)

Tooling

Features:
  • Modifications support future Multi-cloud Runtime functionality. (FLOW-2696)

  • Modifications support future Organizations functionality. (FLOW-2685, FLOW-1351, FLOW-796)

  • Modifications support future SAML single sign-on (SSO) functionality. (FLOW-2707)

Fixes:
  • Adding a new container to a page layout would result in an error. With this fix, containers can be added to page layouts. (FLOW-2751)

  • Saving a new page on the flow canvas after the metadata had been edited would result in the Create New Page form being displayed. With this fix, the Create New Page form is no longer displayed in this scenario. (FLOW-2649)