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


Connector browse cookie size

Feature:

  • The platform and Atom impose the maximum browse cookie size for connectors. Previously, this limitation was only imposed by the Atom. As a part of these changes, the maximum browse cookie size is increased to 307,200 characters for both the Atom and platform. (CON-647)

Atoms, Molecules, and Atom Clouds


Public Atom Clouds

Boomi is committed to modernizing its integration platform to ensure ongoing reliability, performance, and scalability. As part of this effort, migration of the Boomi USA East Hub Cloud (formerly US Hub Cloud) occurred February 22, 2020.

To learn more about the transition plans, see the Boomi's Planned Improvements to its Hosting Environment article in the Community. For an updated list of Atom Cloud IP addresses, see the topic Hostnames and IP addresses for the Boomi Atom Clouds.

Connector browse cookie size

Feature:

  • The maximum browse cookie size for connectors is increased, reducing the chance an import will fail when browsing object types. If the new 307,200 character limit is exceeded for the input or output cookie, an error will be reported and the browse will fail. Previously, these limitations were only imposed by the Atom. Now, they are imposed by the platform, too. (CON-647)

Disk space monitoring

Feature:
  • Logging for disk space monitoring is improved to include additional log messages if disk space consumption continues beyond the threshold set in the Disk Space Warning Limit property. This enhancement allows you to properly gauge trends in the severity of disk space consumption, or whether a temporary, inconsequential spike has occurred. (RUN-366)

To learn more about this feature, see the Disk Space Monitoring for Atom Clouds and the Properties Panel, Advanced tab topics.

Docker installer

Fix:
  • Recent installer updates prevented users from adding Molecule or Atom Cloud Docker nodes. With this fix, users can again add Molecule and Atom Cloud nodes with Docker. (RUN-401)

Runtime stability

The stability of private Molecules and Atom Clouds is found to be unpredictable in Windows environments. Going forward, Boomi recommends users install Molecules and Atom Clouds for production use in Linux environments. (RUN-445)

To learn more about Boomi's supported operating systems for Molecules and Atom Clouds, see the topics Molecule system requirements and Atom Cloud system requirements.

Boomi Integration


Advanced schedules

Fix:
  • Users previously experienced the following issues when attempting to edit, save, and delete advanced schedules:

    • It was not possible to save the deletion of a schedule containing an invalid value if that schedule had been previously saved.

    • When attempting to delete an invalid schedule, saving and refreshing the page reverted the schedule to a previous version and did not delete the schedule as expected.

    • When generating multiple advanced schedules at one time, it was possible to successfully save all schedules if the currently displayed schedule contained only valid values, but another schedule contained invalid values.

  • With this fix, the save or delete functionalities for advanced schedules work as intended. (INT-1590)

Custom roles

Fix:
  • The Atom Management screen erroneously displayed the option to create environments for those users without the Environment Management privilege, although the option was non-functional due to user permissions. With this fix, the Environment Management privilege is required to enable the option to create environments. (INT-917)

Import Wizard

Feature:
  • The Import Wizard for connectors provides an improved user experience and error messaging when the browsed service does not return any object types for the selected action. (CON-627)

JSON profile generation

Feature:
  • To optimize platform performance when importing a new JSON profile from the API Service’s Swagger specification file, it is now not possible to generate more than 5,000 defined or anonymous types, 10,000 nodes, or two levels of recursion. This limitation applies only to imported JSON profiles; you can manually add new types beyond these limits. (INT-1285)

    To learn more about this feature, see the Import endpoints and Generating API endpoints in an API Service component from an external URL topics.

AtomSphere API and Partner API

AS2 Connector Record object

Fix:

  • Beginning in the January 2020 release, the size field in the JSON response was a number, for example "size" : 3138. With this fix, the size field in the JSON response now returns an array, for example "size" : [ "Long", 3138 ]. This returns the behavior of the JSON response to the behavior from before the January release. (APIM-1088)
    Note: This fix required the re-release of the AtomSphere platform.

EDI Custom Connector Record object

Fix:

  • Beginning in the January 2020 release, the size field in the JSON response was a number, for example "size" : 3138. With this fix, the size field in the JSON response now returns an array, for example "size" : [ "Long", 3138 ]. This returns the behavior of the JSON response to the behavior from before the January release. (APIM-1088)
    Note: This fix required the re-release of the AtomSphere platform.

EDIFACT Connector Record object

Fix:

  • Beginning in the January 2020 release, the size field in the JSON response was a number, for example "size" : 3138. With this fix, the size field in the JSON response now returns an array, for example "size" : [ "Long", 3138 ]. This returns the behavior of the JSON response to the behavior from before the January release. (APIM-1088)
    Note: This fix required the re-release of the AtomSphere platform.

Execution Record object

Fix:

  • Beginning in the January 2020 release, the executionDuration, inboundDocumentSizem and outboundDocumentSize fields in the JSON response were a number, for example "executionDuration" : 5706, "inboundDocumentSize" : 1686, "outboundDocumentSize" : 11,. With this fix, the executionDuration, inboundDocumentSizem and outboundDocumentSize fields in the JSON response now return an array, for example "executionDuration" : [ "Long", 180 ], "inboundDocumentSize" : [ "Long", 0 ], "outboundDocumentSize" : [ "Long", 0 ]. This returns the behavior of the JSON response to the behavior from before the January release. (APIM-1088)
    Note: This fix required the re-release of the AtomSphere platform.

HL7 Connector Record object

Fix:

  • Beginning in the January 2020 release, the size field in the JSON response was a number, for example "size" : 3138. With this fix, the size field in the JSON response now returns an array, for example "size" : [ "Long", 3138 ]. This returns the behavior of the JSON response to the behavior from before the January release. (APIM-1088)
    Note: This fix required the re-release of the AtomSphere platform.

RosettaNet Connector Record object

Feature:

  • The object is extended to support the capability to set the following fields in the RosettaNet Service Header using a document property.
    • RosettaNet v2.0 (B2B-829)
      • Is Secure Transport Required

    • RosettaNet v1.1 (B2B-860)
      • Time to Acknowledge Acceptance

      • Time to Acknowledge Receipt

      • Time to Perform

    To learn more about this feature, see the topic RosettaNet Connector Record object.

Fix:

  • Beginning in the January 2020 release, the size field in the JSON response was a number, for example "size" : 3138. With this fix, the size field in the JSON response now returns an array, for example "size" : [ "Long", 3138 ]. This returns the behavior of the JSON response to the behavior from before the January release. (APIM-1088)
    Note: This fix required the re-release of the AtomSphere platform.

X12 Connector Record object

Fix:

  • Beginning in the January 2020 release, the size field in the JSON response was a number, for example "size" : 3138. With this fix, the size field in the JSON response now returns an array, for example "size" : [ "Long", 3138 ]. This returns the behavior of the JSON response to the behavior from before the January release. (APIM-1088)
    Note: This fix required the re-release of the AtomSphere platform.

Connectivity

The new release brings you new features and fixes to help you work smarter and be more efficient.

Amazon SQS connector

Fix:

  • The connector was not reporting results and metadata to Process Reporting for Receive operations. As a result, the Queue Name, Message Id, Receipt Handle, and Sequence Number properties were missing values in Process Reporting even if the connector retrieved a message. Additionally, even if a message was retrieved, the document payload was always 0.0 KB. With this fix, the connector reports results and associated metadata for Receive operations as expected, and the correct document payload size is displayed. (CON-257)

NetSuite connector

Fix:

  • Previously, browsing object types having a large number of custom fields could result in browse operations failing. This occurred because the length of the NetSuite cookie, generated when browsing, exceeded the maximum cookie limit (204,800) imposed by the Atom. With this fix, a new compression algorithm compresses cookies more efficiently, increasing the likelihood that the cookie will not exceed the limit and browse operations will succeed. To enable the corrected behavior, you need to re-import the object type. (CON-60)

Salesforce Platform Events connector

Feature:

  • The connector now uses the Connector SDK Listener API. This is not a functional change. (CON-398)

Shopify connector

Features:

  • A new Query operation field, Query Page Size, is available, enabling you to set the number of results to return for each page. Use this setting to maximize performance and reduce the number of requests required to retrieve a full data set from the service. (BOOMI-40131)

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

  • The Query and Advanced Query operations support cursor-based pagination, introduced in the Shopify API release 2019-07 for the Product object type and continuing in the 2019-10 API release for the other object types. With this feature, the connector uses the Next link provided by the API internally to navigate through multi-page results. (BOOMI-40268)

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

Web Services Server connector

Fix:

  • The query parameter used in AtomSphere API queryMore requests was incorrect. With this fix, the correct query parameter is used. (APIM-841)

Connectivity development

There are no updates to Connectivity development in the February 2020 release.

Master Data Hub

Deployment

Feature:

Golden record version detail

Fix:

  • Duplicate collection item entries appear in a golden record’s version detail view if that collection item data is referenced and the referenced golden record is end-dated and reactivated during the version's lifetime. With this fix, collection item entries are not erroneously duplicated. (HUB-637)

B2B/EDI Management


HL7 document handling

Features:

  • The option to configure a trading partner for outbound validation of documents at the interchange level is now available. When using this option, you can configure the trading partner to filter either the error documents or the entire interchange. The level of validation performed on outbound documents is the same as inbound documents. The new settings are extensible. (B2B-150)

    To learn more about this feature, see the topic Outbound EDI document validation.

    Note: This feature had companion AtomSphere API and Partner API updates in the January 2020 release. (B2B-697, B2B-844)
  • As a means of faciliating exception processing, if, in a Trading Partner component’s Document Types tab, you create a document type or update the settings for a previously defined type and set Invalid Inbound Document Routing for that type to Errors path (the default), invalid inbound documents of that type are subsequently sent to the Trading Partner Start shape’s Errors path.

    Otherwise, to preserve backward compatibility, invalid inbound documents of previously defined types are sent to the shape’s Documents path. However, to maintain this behavior for a previously defined type when you update its settings, you must manually set Invalid Inbound Document Routing for that type to Documents path. (B2B-490)

    To learn more about this feature, see the topic Inbound EDI document validation and acknowledgment.

RosettaNet document handling

Features:

  • You can now set the Is Secure Transport Required field in the RosettaNet v2.0 Service Header using a document property. (B2B-829)

    To learn more about this feature, see these topics:
    Note: This feature has a companion AtomSphere API and Partner API update: The RosettaNet Connector Record object is extended to include the Is Secure Transport Required field.
  • You can now set the following fields in the RosettaNet v1.1 Service Header using document properties:

    • Time to Acknowledge Acceptance

    • Time to Acknowledge Receipt

    • Time to Perform (B2B-860)

  • To learn more about setting document properties for Trading Partner information, see the topic Trading Partner information document properties.

    Note: This feature has a companion AtomSphere API and Partner API update: The RosettaNet Connector Record object is extended to include the three fields.

API Management

Authentication Brokers and API Gateways

Feature:

  • You can now configure the remote JMX (Java Management Extensions) on an API Gateway through the JVM command line. (APIM-437)

     

Developer Portal

Fixes:

  • The Developer Portal and the Swagger Visualization Portal used the incorrect query parameter in AtomSphere API queryMore requests. With this fix, the correct query parameter is used. (APIM-841)

    Note: This fix has a companion Web Services Server connector update.
  • Executing an API through the Execute button in the Developer Portal did not work when a routing header was defined. With this fix, clicking Execute on a subscribed API with a routing header in the Developer Portal executes the API as expected. (APIM-866)

Boomi Flow

The following information identifies the new features and fixes in Boomi Flow Core releases 1.141.1 and 1.142.0, Runtime 3.13.0, SAML service 1.1.0 and 1.1.1, Tooling 2.14.1, and User Interface 3.12.1.

Core

Fix:

  • Cultures were being cached incorrectly, resulting in the inability to translate a single state between different languages. With this fix, single state translation is now performed correctly. (CORE-5584)

  • Installing or updating services containing a ContentList or ContentObject value was causing an error to be displayed. With this fix, installation or updates of services that contain these kinds of values no longer causes this error. (CORE-5583)

Runtime

Fix:

  • After user authentication had expired during runtime (using the 15 minutes expiry duration period), the user was not being redirected to their IdP login page. With this fix, the user is now able to re-authenticate against the runtime flow. (FLOW-856)

SAML service

Fixes:

  • Assertions configured without an expiration time are now by default valid only for a period of up to 14 minutes. With this fix, a user running a flow protected by the SAML Service will be redirected to the Identity Provider (IdP) after 15 minutes to obtain a new assertion, if the IdP is sent an assertion without an expiration time (NotAfter condition). (FLOW-862)

  • Previously, the SAML service did not perform a re-check of assertion values when the service authorization point was called for a second time (joining the flow for example). With this fix, the SAML service now performs a re-check of assertion values for the user, ensuring that user authorization is performed correctly. This fix also aligns the token validity window with the SAML assertion conditions NotBefore and NotOnOrAfter. (FLOW-692)

  • The login URL is no longer populated when a SAML authenticated user tries to run a flow that is then restricted for them by user or group permissions configured within Boomi Flow itself. (FLOW-863)

  • Previously, the login URL for the login redirection was not being correctly formatted when the login URL included query parameters. This was affecting some IdP such as PingFederate. With this fix, the login URL is now correctly formatted. (FLOW-909)

  • Group authorization for flows that were protected by the SAML Service was not being applied correctly. With this fix, group authorization is now performed correctly against the Group ID. (CORE-5592)

Tooling

Feature:

  • The Notifications icon now changes to inform a flow builder that they have new unread notifications. Individual notifications can be marked as "read" by clicking on the envelope icon next to each notification. All notifications are then subsequently marked as read in the main Notifications page. (FLOW-780)

User Interface

Fix:

  • Selection boxes were causing an error to be shown if pagination was configured when a flow was run in Internet Explorer. With this fix, this error no longer occurs and pagination is now configured correctly for selection boxes. (FLOW-890)