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


User guide

Topic filenames in this user guide’s URLs are shortened, as a result of the removal of the underscore _ and the 36-character unique identifier that immediately preceded the .html file extension.

For example, the filename for the topic “Salesforce connector” is shortened as follows:

Atoms, Molecules, and Atom Clouds


Installers

Note: Support for the Docker installer script is removed from the AtomSphere platform. As a result, you can no longer select Docker in the list of operating systems available for Atom, Molecule, or Atom Cloud installers. However, you can still pull the appropriate Docker image directly from Docker Hub and issue a Docker run command. (RUN-821)

To learn more about this change, see the topic Docker installation of an Atom, Molecule, or Atom Cloud.

Note: The Community Bitbucket for Atom, Molecule, and Atom Cloud Docker images has moved to https://bitbucket.org/officialboomi/docker-images/src/master/. The previous location is deprecated and includes information for accessing the new Bitbucket. (RUN-922)
Feature:
  • During installation, you can select an environment to which to attach your new Atom, Molecule, or Atom Cloud. This capability is particularly useful for automated installation scenarios. (RUN-590)
    Note: Subsequent to the start of the August 2020 Release Control period, the installer updates were postponed and will be rescheduled.

Atom Cloud properties

Feature:
  • The new Early Stale Worker TTL Percentage property allows an Atom worker to be eligible for early replacement, and staggers Atom worker restarts to improve Atom Cloud performance. (RUN-4)

    To learn more about this feature, see the topic Properties panel, Advanced tab.

Boomi Integration


Account Dashboard page

Fix:
  • For API Management users with Brokers and Gateways in their account, the All Atoms and Environments filter erroneously included Brokers and Gateways in the list of available filter options. The Offline Atoms gadget also displayed Brokers and Gateways among the list of offline Atoms. With this fix, Brokers and Gateways no longer appear in either location. (ADSEC-791)

Audit logs

Features:
  • An audit log entry is created when an Atom log is downloaded from the Log Files page in Atom Management. (RUN-228)

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

  • An audit log entry is created when an Atom Cloud owner requests the disk space usage for an Atom, Molecule, or Atom Cloud. (RUN-741)
    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 Audit log query construction and Audit log entries topics.

Cluster Status panel

Fix:
  • Molecule clusters do not yet support the deletion of nodes with Atom Queue listeners. However, the delete button was erroneously available for such nodes on the Cluster Status panel though the button remained nonfunctional. With this fix, the button does not appear for nodes with Atom Queue listeners. (RUN-716)

JSON profiles

Feature:

  • The user interface for defining instance identifiers for repeating array elements is improved as follows (B2B-891):

    • The look and feel of the newly renamed Add/Edit Instance Identifier dialog — in particular, the qualifier value list — is modernized, and help content is added.

    • A search filter is added to the newly renamed Select Qualifier dialog.

Fix:

  • Incorrect mapping results occurred in some cases when using profiles in which instance identifiers were defined. With this fix, mapping results in these cases should be correct. (B2B-1094)

Process Reporting

Fixes:
  • For API Management users with Brokers and Gateways in their account, the Atom filter erroneously included Brokers and Gateways in the list of available Atoms. With this fix, Brokers and Gateways no longer appear in the list of Atom filter options. (ADSEC-791)

  • Downloading a process log before the process finished executing resulted in an incomplete log. Attempting to re-download the log after the execution completed also produced an incomplete log. With this fix, process logs always produce the latest execution results available, regardless if the download is initiated during or after the execution completes. (RUN-596)
    Note: This fix does not guarantee live updates for your process executions; process logs may not immediately provide the latest execution results.

XML profiles

Feature:

  • The user interface for defining instance identifiers for repeating elements is improved as follows (B2B-891):

    • The look and feel of the newly renamed Add/Edit Instance Identifier dialog — in particular, the qualifier value list — is modernized, and help content is added.

    • A search filter is added to the newly renamed Select Qualifier dialog.

Fix:

  • Incorrect mapping results occurred in some cases when using profiles in which instance identifiers were defined. With this fix, mapping results in these cases should be correct. (B2B-1094)

AtomSphere API and Partner API

Account User Role object

Feature:
  • Previously, when a user was programmatically added to an account, the user's first and last name was derived from the user's email address. With this release, you can optionally set the object's firstName and lastName fields in Create requests. The firstName and lastName fields are not queryable. (ADSEC-815)

To learn more about this feature, see the topic Account User Role object.

Account Group User Role object

Feature:
  • Previously, when a user was programmatically added to an account group, the user's first and last name was derived from the user's email address. With this release, you can optionally set the object's firstName and lastName fields in Create requests. The firstName and lastName fields are not queryable. (ADSEC-815)

To learn more about this feature, see the topic Account Group User Role object.

Atom Disk Space object

Feature:
  • The new Atom Disk Space object allows Atom Cloud owners to programmatically Get the disk space usage for a given Atom Cloud attachment. (RUN-741)

To learn more about this feature, see the topic Atom Disk Space object.

Environment Extensions object

Feature:

  • You can set the new useDefault attribute to true to override extension values in both full and partial Update requests. (INT-2172)

    Additionally, the new useDefault attribute can be used to identify whether a field has been overridden in Get responses. (INT-2460)

    Note: The useDefault attribute is not applicable to Cross Reference Table and Dynamic Process Property extensions.

    To learn more about this feature, see the Environment Extensions object and Working with the Environment Extensions object topics.

Note: Partial extension updates remains a Tech Preview. General Availability is deferred to the September 2020 release.

Process object

The following feature was released off-cycle into production after the August 2020 release.
  • The Process object's performance is enhanced to produce faster response times, particularly when calling complicated processes. (INT-2528)

Connectivity


LDAP connector

Fix:

  • Occurrence of a Query operation error resulted in an incomplete error message in the process log. The message did not include the source of the actual error. With this fix, the error message is complete, enabling you to research where the process failed and why. (CON-1546)

Listen connectors

Feature:

  • For SDK connectors with listeners, the Listener PayloadBatch implementation handles any exception that occurs when it closes after submitting a batch. If an exception occurs, the listener logs a FINE Warning. (CON-1496)

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

Marketo REST connector

Fix:

  • Filtering a Query operation by Id for all Lead object fields resulted in an error. However, filtering by fewer objects resulted in a successful operation. With this fix, filtering by all Lead object fields results in the operation completing successfully. (CON-969)

Salesforce connector

Feature:

  • The new Batch Size setting for the Send operation lets you adjust the amount of data to send to Salesforce in one batch. The range of valid values, in MB, is 1–150. The default is 10 MB. (CON-1515)

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

Salesforce Platform Events connector

Features:

  • The connector implements the SingletonListenOperation interface, allowing the connector’s Listen operations to run in singleton mode if the com.boomi.container.bounded.listen.enabled container property is set to true. (CON-1245)

    To learn more about this feature, see the topics Salesforce Platform Events connector and Salesforce Platform Events operation.

  • In the unlikely event of connection failure, the new Replay Option setting in the connection lets you determine how subscribers catch up on missed events after the listener restarts. Subscribers can retrieve all retained events and new events from a queue or topic, or retrieve only new events. (CON-1348)

    To learn more about this feature, see the topic Salesforce Platform Events connection.

SAP JCo V2 (Tech Preview) connector

Feature:

  • The new SAP-certified connector delivers the following enhancements in addition to existing SAP connector functionality: (CON-1533)

    • Availability of relevant IDOC EDI header fields as tracked fields for routing and process reporting for the Listen operation.

    • Transaction ID is accessible as a document property for the Send operation.

    • Filtering of Application and Release versions, providing access to application version-specific IDocs, including versions not released and in progress.

    • Support for SAP JCo 3.1.

  • To learn more about this feature, see the topic SAP JCo V2 (Tech Preview) connector.

SAP S/4HANA OData Cloud (Tech Preview) connector

Feature:

  • The initial release of the SAP S/4HANA Cloud OData (Tech Preview) connector will support the OData APIs as defined in the SAP API Business Hub in June 2020. It will support Get, Create, Update, Delete and Query connector operations with embedded X-CSRF and ETag implementation where required. (CON-1710)

    Note: Subsequent to the start of the August 2020 Release Control period, the release of this connector was postponed and will be rescheduled.

SFTP V2 (Tech Preview) connector

Feature:

  • This connector is built using the Boomi Connector SDK, providing the flexibility to address customer needs at a higher velocity. This update extends previously existing functionality with the following new operations: (CON-1081)

    • Query — Query the files in the target directory using specified filter criteria.

    • List — List files in the target directory using specified filter criteria.

    • Upsert — Update or insert a new file into the target directory.

    • Delete — Delete a file from the target directory.

  • To learn more about this feature, see the topic SFTP V2 (Tech Preview) connector.

Solace PubSub+ connector

Feature:

  • This connector was released off cycle into production after the August, 2020 release. The Solace PubSub+ connector provides a fast, robust, and secure data transport layer that enables events to move freely and easily across a distributed enterprise, and ensures seamless collaboration between Boomi’s iPaaS and Solace’s advanced event broker services. (CON-1889)

    To learn more about this connector, see the topic Solace PubSub+ connector.

Connectivity development


Connector SDK

Feature:

  • The Connector SDK is updated to version 2.7. For information about the updates in this release, see the SDK changelog.

Fixes:

  • When accessing the properties of 'customproperties' type fields in the PropertyMap, the returned Map<String, String> was mutable if you used the native Map get(String key) method off of PropertyMap. With this fix, the returned Map<String, String> is immutable regardless of the method used to access the property’s value from the PropertyMap. (CON-1325)

  • When an importable operation field was defined in the descriptor and used when browsing (Import Wizard) with the same ID, the component XML and data were successfully saved. However, the correct field value did not appear in the operation upon closing and reopening the component. The value was either blank or incorrect. With this fix, the operation shows the correct field value, as expected. (CON-1634)

Connector packaging

Feature:

  • The maximum size limit for connector archive file uploads is increased from 20 MB to 30 MB. (CON-1692)

    To learn more about this feature, see the topic Connector packaging.

Custom connector deployment

Feature:

  • Previously, users having a trial account could submit a custom connector for review, approval, and deployment to make it available for use in Boomi Integration. This presented challenges when the trial expired because Boomi could not access the trial account to either approve or reject the connector. Effective with this release, users of trial accounts can no longer submit custom connectors for review, approval, and deployment. To submit custom connectors, upgrade to a Boomi Integration edition enabling this feature. (CON-357)

    To learn more about this feature, see the topic Deploying a custom connector.

Master Data Hub


There are no updates to Master Data Hub in the August 2020 release.

B2B/EDI Management


EDI profiles

Feature:

  • The user interface for defining instance identifiers for segments and loops is improved as follows (B2B-891):

    • The look and feel of the newly renamed Add/Edit Instance Identifier dialog — in particular, the qualifier value list — is modernized, and help content is added.

    • A search filter is added to the newly renamed Select Qualifier dialog.

Fix:

  • Incorrect mapping results occurred in some cases when using profiles in which instance identifiers were defined. With this fix, mapping results in these cases should be correct. (B2B-1094)

RosettaNet trading partner components

Fixes:

  • The name of the Partner Location field in the Control Information section of the ROSETTANET Standard tab was misleading in that the field value is used in the delivery header’s locationID field in RosettaNet messages. With this fix, the Partner Location field is relabeled Partner Location ID. (B2B-241)

  • In the Message Options section of the ROSETTANET Standard tab, settings dependent on selection of the Sign Messages and Encrypt Messages options were erroneously accessible while those options were not selected. With this fix, each of the settings in question is visible and adjustable only while the respective related option is selected. (B2B-319)

API Management

Authentication Brokers and API Gateways

Fixes:

  • Renaming an Authentication Broker the name of a previously deleted Broker caused an error. With this fix, you can rename an Authentication Broker the name of a previously deleted Broker without error. (APIM-1961)

  • After a restart, an API Gateway could reference an old JDBC connection, which could cause the API Gateway to fail if the head node changed. With this fix, an API Gateway will restart correctly when the head node changes. (APIM-2051)

Known Issue:

  • If you select 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 displays whether or not your changes were saved. Ensure that you click Save and then navigate away from the page, despite the warning message. Your changes were saved. This issue will be addressed as part of the September 2020 release.

Developer Portal

There are no updates to the Developer Portal in the August 2020 release.

External Authentication

Feature:

  • A new Identity Provider Type, JWT (JSON Web Token), is added for Authentication Sources. You can select JWT as your Identity Provider Type when creating an Authentication Source and configure your Identity Provider URL for the JWT Authentication Source. (APIM-731)

    To learn more about this feature, see the topic Authentication Source settings for JWT.

Boomi Flow

The following information identifies the new features and fixes in Boomi Flow Azure Service 1.2.0, Core 1.159.0, 1.160.0, 1.160.1, 1.161.0, 1.162.0, 1.163.0, Email Service 1.1.5, Hub Service 1.2.0, Salesforce Service 1.19.0, SAML Service 1.2.0, System Flows 1.55.0, 1.56.0, 1.57.0, Tooling 2.26.0, 2.26.1, 2.27.0, 2.28.0, and User Interface 3.22.0, 3.23.0, 3.24.0, 3.25.0, 3.26.0, 3.26.1.

Azure Service

Fix:
  • The Azure service previously could return a maximum of 100 Users and Groups, meaning that a flow builder would be unable to select from Users/Groups beyond this limit on the Flow Properties form. With this fix, the maximum number of Users and Groups returned with the Azure service is increased from 100 to 999. (FLOW-2144)

Core

Features:
  • A new authRedirectToRegionalInstance option is added to the /api/admin/1/tenant API endpoint to allow users to specify that any redirection that occurs during redirect-based authentication is routed to the appropriate regional Boomi Flow instance. (FLOW-1612)
    • This option is disabled by default, meaning that a flow returns a login URL containing a redirect_uri of [platform_base]/api/run/1/[auth_type], where [platform_base] is the platform base (such as https://flow.manywho.com) and [auth_type] is either oauthoauth2 or saml.

    • Enabling this option results in a flow returning a login URL containing a redirect_uri of https://[host_header]/api/run/1/[auth_type] , where [host_header] is the domain as defined in the host header of the request (such as flow-gb.manywho.com) and [auth_type] is either oauthoauth2 or saml. The tenantSettings setting is also required if this is enabled.

  • Historical navigation breadcrumb links can now be translated. When saving a map element that will be displayed in the breadcrumb link trail, the Label of the map element will be made available for translation. When a user runs a flow that uses historical navigation, the translated version is displayed if the player culture is set and matches the user browser culture. An event handler for the ‘history’ event will need to be added to the manywho.settings.initialize function in the player. (FLOW-2010)

Fixes:
  • A 'The flow has a circular dependency' error was displayed when a flow builder attempted to run and create a snapshot of a flow that allowed child subflows to loop back to the parent flow. With this fix, flows can be called in a loop using subflow/return map elements, without a circular dependency looping restriction being applied. (FLOW-1805)

  • Execution of certain complex page conditions resulted in an ‘Object reference not set to an instance of an object’ error in some cases. With this fix, the error no longer occurs and the condition executes as expected. (FLOW-1998)

  • Configuration changes are applied to optimize the resiliency of platform messaging. (FLOW-2170)

  • System logging is improved. (FLOW-1950)

  • Optimizations are applied to improve performance when deleting a large amount of flow states. (FLOW-2143)

  • The Dependencies table on the ValuesTypes, and Services pages previously displayed only the first 10 dependencies, which in some cases prevented viewing of all dependencies. With this fix, pagination for the dependency tables on these pages is applied, enabling the viewing of all dependencies for values, types, and services. (FLOW-1887)

  • When using an identity provider (IdP) for flow authorization, if the IdP set error and error_description query parameters in the callback URL in order to report an error, the resulting error message was incorrectly displayed to the flow user. With this fix, the error message is correctly displayed. (FLOW-1342)

Email Service

Fix:
  • If operator map elements were used after a message map element in a flow, this would sometimes result in the display of an error message. With this fix, this error message is no longer displayed. (FLOW-1488)

Hub Service

Feature:
  • Column ordering for data returned from the Hub service was incorrectly applied. For example, adding a data action filter and selecting a column in the Which column should the data be ordered by? drop-down menu did not result in the data being ordered when loaded into a combobox or table component. The OrderBy metadata setting was also not being correctly applied. With this fix, both data action filter column ordering and ordering via the OrderBy metadata setting are correctly applied. (FLOW-2085)

Salesforce Service

Fix:
  • The Click to Join Flow link created in a social feed did not successfully allow a user to join a flow using the social feed collaboration feature —for example, when integrating Chatter with Salesforce into a flow. With this fix, clicking the Click to Join Flow link successfully directs a user to the correct Join URL for the flow. (FLOW-2104)

SAML Service

Features:
  • An additional Compress request configuration value enables SAML requests to be automatically compressed before being sent to an Identity Provider (IdP). This functionality is provided to support IdPs that require SAML request compression. (FLOW-1368)

  • Two additional claim attributes are supported when configuring an IdP assertion package. (FLOW-2100)
    • Primary Group Name: The primary name of the group of which the user is a member. This is optional, depending on your configuration. The URI is: http://schemas.manywho.com/2020/identity/claims/primarygroupname

    • Primary Group Id: The primary ID of the group of which the user is a member. This is optional, depending on your configuration. The URI is: http://schemas.manywho.com/2020/identity/claims/primarygroupid

System Flows

Fixes:
  • It was possible to save a complex Page Condition even if a Page Operation or Page Rule had not been added. A 'Value cannot be null' error was also displayed. With this fix, the Condition panel states that at least one Page Rule and one Page Operation must be added before the Page Condition can be saved. The panel’s Save button is disabled until both sections have had at least one item added. (FLOW-2001)

  • Once Voting was added to a step or page map element, it would persist even after being removed. With this fix, Voting no longer persists after its removal from step and page map elements. (FLOW-450)

  • The Flows page listed available flows twice in certain scenarios, such as when changing between tenants containing a large number of flows. With this fix, these scenarios no longer cause duplicate entries in the list. (FLOW-2020)

Tooling

Fixes:
  • Changes made to a component type in the page metadata of the Page Layout Editor were not saved correctly or updated in the user interface, resulting in the edited metadata reverting back to the previously saved component type. With this fix, changes made to components in the page metadata are saved correctly, and the user interface is updated to reflect the edited page metadata. (FLOW-2098)

  • If searching for a tenant in the tenant switch dialog returned no results, the displayed warning erroneously read “You don’t seem to be a builder in any tenants”. With this fix, when a search returns no results, the displayed warning reads “Sorry, it doesn’t look like your search matches any tenants”. (FLOW-986)

  • System logging is improved. (FLOW-2146)

  • The Flows page listed available flows twice in certain scenarios, such as when changing between tenants containing a large number of flows. With this fix, these scenarios no longer cause duplicate entries in the list. (FLOW-2020)

  • When saving changes using the page metadata editor, if an error occurred the page user interface would refresh, resulting in the loss of any unsaved changes. No error message was displayed to the user to inform them that the error had occurred. With this fix, the user interface does not refresh, and an error message is displayed if an error occurs. (FLOW-2201)

User Interface

Features:
  • Flow users are able to more easily delete individual values from a multi-select Combobox on a page. When a value is selected, it is added to the Combobox selection field to indicate it has been selected, and an 'x' icon is displayed on the value. Simply clicking the value removes it from the selection. (FLOW-1800)

  • Historical navigation breadcrumb links can now be translated. When saving a map element that will be displayed in the breadcrumb link trail, the Label of the map element will be made available for translation. When a user runs a flow that uses historical navigation, the translated version is displayed if the player culture is set and matches the user browser culture. An event handler for the ‘history’ event will need to be added to the manywho.settings.initialize function in the player. (FLOW-2010)

Fixes:
  • It was possible to save a complex Page Condition even if a Page Operation or Page Rule had not been added. A 'Value cannot be null' error was also displayed. With this fix, the Condition panel states that at least one Page Rule and one Page Operation must be added before the Page Condition can be saved. The panel’s Save button is disabled until both sections have had at least one item added. (FLOW-2001)

  • Applying the justify attribute to an outcomes component did not modify the justification for the button group when viewed in a browser. With this fix, applying this attribute has the expected effect, allowing you to define whether an outcomes component should be aligned to the left, center, or right of a container. To learn more about using the justify attribute, see the topic Outcomes component attributes. (FLOW-1910)

  • Items were not being correctly added to or removed from a list in an offline flow. With this fix, items can be added to/removed from lists in an offline flow. (FLOW-2102)

  • Optimizations are applied to offline flow functionality to ensure consistent performance. (FLOW-1619)

  • Resizing editable fields in a table component could result in visual misalignment of the field columns, as a flow user could drag-resize fields without any width or height restrictions. With this fix, editable fields can only be resized in height, and have been enhanced so that double-clicking an editable table cell displays the editable contents in a separate modal pop-up window. (FLOW-471)

  • The current map element name was incorrectly displayed in the breadcrumb link trail for some flows with historical breadcrumb navigation enabled. With this fix, the current map element name is correctly displayed for all such flows. (FLOW-2223)

  • When entering text into a searchable combobox field to filter/search the options (such as the Select Page field on the Page form), the focus would shift into the initial input field on the page as the text was being entered. This behavior occurred because the autofocusinput player setting would shift focus whenever a component on the page made an object data request, such as populating a combobox with data from an external service. With this fix, focus shifting when entering text does not occur in fields of this type. (FLOW-1402)