Appronto

Global navigation

Features:

• 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: This feature was deferred from the September 2020 release and is included in the October 2020 release.

• For users who have access to multiple accounts, your five most recent accounts are now available in a quick selection option from the Account switching menu. (DS-2503)

  To learn more about this feature, see the topic Account switching menu.

Boomi Atom Clouds

Feature:

• All Boomi Atom Clouds now provide the capability to connect to outbound API endpoints requiring SNI (Server Name Indication) support. Previously, the Boomi US Atom Cloud (Legacy), Boomi US Test Atom Cloud (Legacy), and Boomi GBR Integration Cloud did not support SNI. (RUN-1175)

Atom Cloud management

Feature:

• Atom Cloud owners can set the Cloud Attachment property Enable Download of Execution Artifacts and Atom Worker Logs to true, per tenant, which allows Atom Cloud users to download execution artifacts and Atom worker logs. (RUN-238)

  Note: This feature has companion changes covered in the Boomi Integration and AtomSphere API and Partner API sections of these release notes.

  To learn more about this feature, see the Attachment Quotas tab topic.

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_261. Boomi Atom Clouds are also modified to use Java 1.8.0_261. (RUN-961, RUN-969)

Known limitation:

• After Boomi Test Atom Clouds were upgraded to Java 1.8.0_261, processes running on those Atom Clouds were failing if they used Groovy scripts that calculate cryptographic hashes. Atom v20.10.1 was applied to those Atom Clouds to resolve the issue. If you encounter this issue on your private Atom Clouds, request Atom v20.10.1 from Support. (RUN-1253)

  Note: Atom v20.10.1 is being applied to Boomi public Atom Clouds as part of the October 2020 release.

API components

Fix:

• If an API is created in Boomi Integration using a JSON profile where the root node type is an array, an incorrect Swagger model was generated. With this fix, a correct Swagger model is generated, and you can use the JSON profile structure from the Swagger Visualization Portal. (APIM-2289)

Atom Workers panel

Feature:

• Atom Cloud users can download Atom worker logs from the Atom Workers panel in Atom Management. (RUN-718)

  Note: Atom Cloud owners must set the Enable Download of Execution Artifacts and Atom Worker Logs property to true in Cloud Management before logs can be downloaded.
  Note: This feature has companion changes covered in the Atoms, Molecules, and Atom Clouds and AtomSphere API and Partner API sections of these release notes.

  To learn more about this feature, see the topics Atom Workers panel and Attachment Quotas tab.

Audit logs

Features:

• An audit log entry is created when a user is locked from the AtomSphere platform. (ADSEC-668)

  To learn more about this feature, see the topics Audit log entries and Audit log query construction.

• An audit log entry is created for an AtomSphere API request from a user to update their containers to the latest supported version of Java. (RUN-833)

  To learn more about this feature, see the topics Audit log entries and Audit log query construction.

• An audit log entry is created for an AtomSphere API request from an Atom Cloud owner for the immediate purging of process execution data. (RUN-743)

  To learn more about this feature, see the topics Audit log entries and Audit log query construction.

• An audit log entry is created when Atom Worker Logs are downloaded. (RUN-718, RUN-721)

  To learn more about this feature, see the topics Audit log entries and Audit log query construction.

• An audit log entry is created when execution artifacts are downloaded. (RUN-238, RUN-720)

  To learn more about this feature, see the topics Audit log entries and Audit log query construction.

Cross Reference Table components

Fix:

• When importing a CSV file into a Cross Reference Table, backslash characters in the file were erroneously treated as escape characters and thus not imported. With this fix, all special characters are properly imported from CSV files. (INT-1633)

Environment extensions

Feature:

• A warning message is displayed in the environment Extensions dialog if an overridden process property value no longer matches an allowed value. This can happen if the allowed values for the property were modified after the override value was set. (INT-69)

  Note: The original override value is used for process executions until modified.

Fix:

• An error occurred upon clearing and saving numeric fields in connection settings extensions. With this fix, numeric fields in connection settings extensions can be cleared and saved, as expected. (INT-2822)

  Note: If, as a result of this defect, numeric fields in your environment’s connection settings extensions were erroneously set to null values, you need to reset those values. You can reset the values using either the environment Extensions dialog or an AtomSphere API Update request on the Environment Extensions object. The latter method is described in the Boomiverse article Known issue – Field Disappears From Environment Extensions UI When The Field Value is Cleared.

JSON profiles

Fixes:

• In the Data Element tab’s Element Details panel, in the Qualifiers section, the error message in response to a Remove All action request where there were no qualifiers was the same as the error message in response to a Remove Selected action request where no qualifiers were selected. With this fix, the error message is generalized to cover both scenarios. (B2B-1157)

• The following fixes relate to the adding of instance identifiers to repeating array elements: (B2B-1160)

  • It was possible to add an instance identifier to an element after selecting Identify By Occurrence in the Add/Edit Instance Identifier dialog and then setting Occurrence to a null or invalid value. With this fix, an instance identifier defined in this manner cannot be added; an error message appears in the dialog.

  • It was possible to add an instance identifier to an element in which the instance was defined using multiple qualifier values for the same element. With this fix, an instance identifier defined in this manner cannot be added; an error message appears in the dialog.

  • Although defining a profile that contains duplicate instance identifiers is not recommended, saving such a profile did not require confirmation. With this fix, saving a profile that contains duplicate instance identifiers requires confirmation.

• The instructions in the Select Qualifiers dialog (formerly the Choose Qualifier(s) dialog) incorrectly stated that only standard qualifiers are available for selection. In fact, only custom qualifiers are available for selection; standard qualifiers are not applicable to JSON profiles. With this fix, the dialog contains correct instructions. (B2B-1164, B2B-1165)

Process extensions

Fix:

• It was not possible to access the process Extensions dialog for processes which called recursive secondary processes. With this fix, process extensions are accessible for all processes, as expected. (INT-2339)

Process reporting

Feature:

• Users can download execution artifacts from the Extended Execution Information dialog in Process Reporting. (RUN-238)

  Note: Atom Cloud owners must set the Enable Download of Execution Artifacts and Atom Worker Logs property to true in Cloud Management before execution artifacts can be downloaded.

  Note: This feature has companion changes covered in the Atoms, Molecules, and Atom Clouds and AtomSphere API and Partner API sections of these release notes.

  To learn more about this feature, see the Extended Execution Information dialog and Attachment Quotas tab topics.

Shared web server

Fixes:

• HTTP headers that are protected in the Atom’s Shared Web Server configuration were erroneously passed into processes. With this fix, protected HTTP headers are not passed into processes. (APIM-2249)

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

• The incorrect character encoding value was sent to the Content-Encoding HTTP header. With this fix, the value set in the inheader_Content-Encoding document property is set as the Content-Encoding HTTP header. (APIM-2282)

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

SSO options

Feature:

• In addition to SSO users, SSO administrators can use the Sign Out Redirect URL field in Setup > SSO Options to specify the URL to which they are redirected upon signing out of the AtomSphere platform. (ADSEC-906)

  To learn more about this feature, see the topic SSO Options tab.

XML profiles

Feature:

• When generating XML profiles through a WSDL import for an API component or when browsing a Web Services SOAP Client operation, a warning message is displayed if the limit on the number of nodes, recursion levels, or types that can be generated within a profile is reached. (INT-1440, INT-1441)

Fixes:

• In the Data Element tab’s Element Details tab, in the Qualifiers section, the error message in response to a Remove All action request where there were no qualifiers was the same as the error message in response to a Remove Selected action request where no qualifiers were selected. With this fix, the error message is generalized to cover both scenarios. (B2B-1157)

• The following fixes relate to adding instance identifiers to repeating elements: (B2B-1160)

  • It was possible to add an instance identifier to an element after selecting Identify By Occurrence in the Add/Edit Instance Identifier dialog and then setting Occurrence to a null or invalid value. With this fix, an instance identifier defined in this manner cannot be added; an error message appears in the dialog.

  • It was possible to add an instance identifier to an element in which the instance was defined using multiple qualfier values for the same element. With this fix, an instance identifier defined in this manner cannot be added; an error message appears in the dialog.

  • Although defining a profile that contains duplicate instance identifiers is not recommended, saving such a profile did not require confirmation. With this fix, saving a profile that contains duplicate instance identifiers requires confirmation.

• The instructions in the Select Qualifiers dialog (formerly the Choose Qualifier(s) dialog) incorrectly stated that only standard qualifiers are available for selection. In fact, only custom qualifiers are available for selection; standard qualifiers are not applicable to XML profiles. With this fix, the dialog contains correct instructions. (B2B-1164, B2B-1165)

Deployed Package object

Fix:

• Create operations on Deployed Package objects produced a large volume of errors when deploying packaged components that included secondary processes shared across many parent processes. With this fix, performance is improved when deploying packaged components that include shared secondary processes. (INT-2287)

Download Atom worker log operation

Feature:

• As an Atom Cloud user, you can programmatically request a download of Atom worker logs by means of a Create operation on an Atom Worker Log action. (RUN-721)

  Note: Atom Cloud owners must set the Enable Download of Execution Artifacts and Atom Worker Logs property to true in Cloud Management before Atom Worker logs can be downloaded.

  Note: This feature has companion changes covered in the Atoms, Molecules, and Atom Clouds and Boomi Integration sections of these release notes.

  To learn more about this feature, see the topic Download Atom worker log operation.

Download execution artifacts operation

Feature:

• You can programmatically download execution artifacts by means of a Create operation on an Execution Artifacts action. (RUN-720)
  Note: Atom Cloud owners must set the Enable Download of Execution Artifacts and Atom Worker Logs property to true in Cloud Management before execution artifacts can be downloaded.
  Note: This feature has companion changes covered in the Atoms, Molecules, and Atom Clouds and Boomi Integration sections of these release notes.

  To learn more about this feature, see the topic Download execution artifacts operation.

Environment Extensions object

Fix:

• Previously, updating empty default values for Process Property, Trading Partner, Communication Channel, Connection, and Operation extensions resulted in an error. With this fix, the Environment Extensions object is properly updated when a request specifies empty values for non-overridden fields. (INT-2264, INT-2347)

Purge Atom Cloud attachment operation

Feature:

• As an Atom Cloud owner, you can programmatically request the purging of Atom Cloud attachment data by means of an Execute operation on an Purge Atom Cloud attachment action. This action honors existing purge schedule settings set in the Boomi Integration user interface. (RUN-743)

  To learn more about this feature, see the topic Purge Atom Cloud attachment operation.

Upgrade Java operation

Feature:

• You can programmatically upgrade your Atoms, Molecules, and Atom Clouds to Boomi’s latest supported version of Java by means of the Upgrade Java action. (RUN-833)

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

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

Known issue:

• When the migrateCertificate attribute or the JavaUpgradeOptions element is omitted in the request body, an error is returned. To avoid this issue until it is fixed in a future sprint, it is recommended that you always set these parameters in your request. (RUN-1216)

Connector availability

Feature:

• The following connectors, formerly Tech Previews, are Generally Available for production use with this release. (CON-1787)

  • Amazon EventBridge
  • FTP V2
  • Live Optics
  • Microsoft Azure Cosmos DB
  • OpenManage Enterprise
  • SAP JCo V2
  • SFTP V2
  • Workday Prism Analytics

Custom connectors

Fix:

• When overriding JARs for a custom connector and using a high security policy on the Atom Cloud or Molecule, the operation using the JAR resulted in an error. With this fix, the operation works as expected. (CON-1617)

HTTP PATCH Client connector

Feature:

• Previously, you could not utilize private client certificates and public certificates for SSL authentication when creating a connection. With this feature, two new connection fields are available, Client SSL Certificate and Trust SSL Server Certificate, enabling you to configure client and trust SSL certificates when creating the connection. The connection now utilizes certificates deployed to the Atom. Any certificates configured with these fields take precedence over certificates deployed to the Atom. (CON-1698)

  To learn more about this feature, see the topic HTTP PATCH Client connection.

Mail connector

Feature:

• The connector supports the TLSv1.2, TLSv1.1, and TLSv1.0 security protocols for encrypted communication to send and retrieve email. (CON-2158)

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

Mail (IMAP) connector

Fix:

• The default 16 KB fetch size for Receive operations caused those operations to take longer than expected. With this fix, the fetch size is increased to 1 MB to quickly return email messages. (CON-1428)

Microsoft Dynamics 365 for Customer Engagement connector

Feature:

• Previously, you could not set timeouts for the connection, resulting in certain processes waiting indefinitely for a response from the server. In some cases, the process continued to run or the Atom stopped it after 24 hours. With this feature, two new connection settings are available, Connection Timeout (ms) and Read Timeout (ms), enabling you to determine the timeout for both the connection and data transfer. (CON-1951)

  To learn more about this feature, see the topic Microsoft Dynamics 365 for Customer Engagement connection.

Microsoft Dynamics 365 for Finance and Operations connector

Feature:

• Previously, you could not set timeouts for the connection, resulting in certain processes waiting indefinitely for a response from the server. In some cases, the process continued to run or the Atom stopped it after 24 hours. With this feature, two new connection settings are available, Connection Timeout (ms) and Read Timeout (ms), enabling you to determine the timeout for both the connection and data transfer. (CON-1952)

  To learn more about this feature, see the topic Microsoft Dynamics 365 for Finance and Operations connection.

NetSuite connector

Feature:

• The NetSuite connector supports connecting to NetSuite Version 2020 Release 1 (also known as v2020.1). (CON-1969)

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

OData Client connector

Feature:

• Previously, you could not set timeouts for the connection, resulting in certain processes waiting indefinitely for a response from the server. In some cases, the process continued to run or the Atom stopped it after 24 hours. With this feature, two new connection settings are available, Connection Timeout (ms) and Read Timeout (ms), enabling you to determine the timeout for both the connection and data transfer. This feature applies only to OData V4.0. (CON-1082)

  To learn more about this feature, see the topic OData Client connection.

SAP JCo V2 connector

Feature:

• The connector is no longer a Tech Preview and is now classified as an Enterprise connector, similar to the SAP connector. Your available license count does not change until you redeploy a component using the connection. Once the connection is redeployed, your usage quotas are recalculated and display on the Licensing page. (CON-1489)

Shopify connector

Feature:

• To align the connector operations with the supported Shopify objects, the connector supports the Shopify API version 2020-07. (CON-2025)

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

Web Services Server connector

Fixes:

• HTTP headers that are protected in the Atom’s Shared Web Server configuration were erroneously passed into processes. With this fix, protected HTTP headers are not passed into processes. (APIM-2249)

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

• The incorrect character encoding value was sent to the Content-Encoding HTTP header. With this fix, the value set in the inheader_Content-Encoding document property is set as the Content-Encoding HTTP header. (APIM-2282)

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

Connector SDK

Feature:

• With this release, the Connector SDK is updated to version 2.8.1. For information about the updates in this release, see the SDK changelog. (CON-2107)

EDI profiles

Feature:

• This release adds support for X12 versions 7050, 7060, and 8010. These versions are added to the list of X12 versions available for selection in the Select Transmission dialog, which is used to select the X12 transaction set with which a profile is associated. The dialog opens from the X12 Version Information section of a profile’s Options tab. (B2B-1169)

Fixes:

• In the Data Element tab’s EDI Element Details tab, in the Qualifiers section, the error message in response to a Remove All action request where there were no active qualifiers was the same as the error message in response to a Remove Selected action request where no qualifiers were selected. With this fix, the error message is generalized to cover both scenarios. (B2B-1157)

• The following fixes relate to adding instance identifiers to loops and segments: (B2B-1160)

  • It was possible to add an instance identifier to an element after selecting Identify By Occurrence in the Add/Edit Instance Identifier dialog and then setting Occurrence to a null or invalid value. With this fix, an instance identifier defined in this manner cannot be added; an error message appears in the dialog.

  • It was possible to add an instance identifier to an element in which the instance was defined using multiple qualfier values for the same element. With this fix, an instance identifier defined in this manner cannot be added; an error message appears in the dialog.

  • Although defining a profile that contains duplicate instance identifiers is not recommended, saving such a profile did not require confirmation. With this fix, saving a profile that contains duplicate instance identifiers requires confirmation.

• The instructions in the Select Qualifiers dialog (formerly the Choose Qualifier(s) dialog) incorrectly stated that only standard qualifiers are available for selection. With this fix, the instructions reflect the fact that both standard and custom qualifiers are available for selection. (B2B-1164, B2B-1165)

Trading partner document archiving

Feature:

• There is a new Archiving tab in Communication Channel components. In that tab, a new option, Archive document data that passes through this trading partner, enables precise control of the archiving of processed documents in a process in which trading partners share a communication channel.

  • If the new archiving option for the shared communication channel is not selected, which is the case by default, the archive directory and filename prefix for documents processed by trading partners sharing the channel are determined in the same manner as before.

  • If the new archiving option for the channel is selected, the archive directory for documents processed by trading partners sharing the channel is set in the Communication Channel component’s Archiving tab, and the filename prefix is the name of the component. Documents processed by trading partners sharing the channel are archived, regardless of whether Archive document data that passes through this trading partner is selected in those trading partners. (B2B-982)

• Note: EDI connectors are updated to support this feature. (B2B-583)

  To learn more about this feature, see the topics Trading Partner Archiving tab and Communication Channel components.

Authentication Brokers and API Gateways

Features:

• Authentication Broker and API Gateway installers and updaters are modified to use Java 1.8.0_261. (RUN-961, RUN-969)

• You can programmatically upgrade Authentication Brokers and API Gateways to Boomi’s latest supported version of Java by means of the Upgrade Java action. (RUN-833)

  Note: This feature has companion changes covered in the AtomSphere API and Partner API section of these release notes.

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

• The API Gateway passes the original Authorization header from the client’s request through to the dynamic document property inheader_Authorization within a Boomi Integration process. (APIM-1890)

  In order for this change to take effect, refresh the API. To refresh the API, migrate the environment containing the API off of its API Gateway and then reattach it. Or, to refresh an individual API, update the custom URL of the API.

Developer Portal

Feature:

• Developer Portal theming is introduced. With the capability to theme your Developer Portal, you can modify your Developer Portal to use your organization’s logo and color palette. (APIM-40, APIM-2096)

  To learn more about this feature, see the topics Configuring your Developer Portal and Publish screen.

Azure Service

Core

Hub Service

Tooling