These release notes identify the new features and bug fixes released in AtomSphere for July 2020.

Subject to the terms and conditions of our existing contract with your firm, and liability provisions and limits therein, we confirm that Boomi has successfully passed all applicable test cases associated with the updates identified in this product release.

Release notes for the 12 months preceding the current release are archived.

AtomSphere platform


Global and service navigation

Feature:

  • In order to make the navigation menus easier to navigate, a new responsive navigation menu is released. The new navigation menu splits the global navigation items in the masthead from the active service navigation. (DS-3257)

    In the global navigation:

    • Switching to a different service is moved to greater prominence, next to the link to the Home page.

    • The Help menu is given greater prominence and expanded to include a link to Training, in addition to the Documentation, Support, and Community links previously included in the Help menu.

    • Viewing and configuring your user and account settings is moved to the global navigation menu.

    • If you have access to multiple accounts, the account that you are in is given greater prominence and remains your account switcher. If you only have access to a single account, your account name is visible only in the Settings drop-down menu.

    • The Sign Out button is moved to the global navigation menu.

  • In the service navigation:

    • The active service is moved to greater prominence in the service navigation menu, instead of being listed in the service switcher menu within the global navigation.

SSO certificate update

The certificate that Boomi uses to sign authentication requests as part of the single sign-on (SSO) is due to expire July 24, 2020. An updated certificate is therefore deployed July 20, 2020. If your SSO to the platform is a service provider-initiated sign in, your identity provider administrator must update the signing certificate in your identity provider. The exact steps vary depending on the identity provider.
  • Some identity providers allow the administrator to update the certificate by refreshing the platform metadata for the account. Boomi recommends this method of updating the certificate if the identity provider supports it.
  • Other identify providers require the administrator to manually upload the updated certificate. For more information, please see the Boomiverse Community article about updating SSO certificates.

(ADSEC-818)

Feature:
  • Boomi has updated the AtomSphere MetaData URL to now support the SAML 2.0 standards for sharing multiple certificates. (ADSEC-841)

    This feature required the re-release of the AtomSphere platform.

Atoms, Molecules, and Atom Clouds


Container properties

Features:

  • The new Maximum Size for Update Operation property lets you adjust the maximum size for input documents. The default value is 1 MB. (CON-956)

    Note: This feature has companion Connector SDK changes that allow connector developers to set the maximum size for input documents at the connector level — see the Connectivity development section of these release notes.

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

  • The new Maximum Number of Active Batches per Listener property lets you adjust the number of listener batches that a listener instance is allowed to create for SDK connectors with listeners. The default value is 5. (CON-1322)

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

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

Cloud properties

Fix:
  • Previously, the Disk Space Monitoring Verbose Logging advanced Cloud property returned excessive log data. With this fix, logging is improved to be more succinct. (RUN-745)

Cluster Status panel

Known issues:
  • When a node is deleted, in some cases it may erroneously show an “Online” status rather than the expected “Deleting” status.

  • In Advanced Cloud property settings, the Async Message Poller Timeout for Molecule Scaledown property value must be greater than that set in the Force Restart Override for Molecule Scale Down property.

  • When a node is deleted and restarted, the node temporarily shows a “Deleting” status in the Cluster Status panel. It eventually corrects itself to display the correct status.

  • When a head node is deleted from the Cluster Status panel, the star icon indicating the head node appears both in the original head node and the new head node until the first completes deletion.

(RUN-631)

Docker images

The following fixes were released off-cycle after the July 2020 release.
  • Previously, it was not possible to set nonProxyHosts containing pipe | characters in Docker image properties. With this fix, you can insert a backslash to escape the pipe character. If a backslash is inserted before the pipe character, the pipe character is not used as a delimiter. (RUN-683)

  • Kubernetes liveness, readiness, and startup probes failed in Docker image version 3.1.1. With this fix, Docker image version 3.1.2 is released so that Kubernetes probes no longer fail. (RUN-958)

Java upgrades

Feature:
  • The Atom, Molecule, and Atom Cloud installers and updaters are modified to use Java 1.8.0_251. Boomi Atom Clouds are also modified to use Java 1.8.0_251. (RUN-623, RUN-624)

The following feature was released off-cycle into production after the July 2020 release.
  • The Docker images for Atoms, Molecules, and Atom Clouds are modified to use Java 1.8.0_251. (RUN-795)

Logging

Fix:

  • When there was a head node issue, excess messages were logged. With this fix:

    • The following logs are changed to a FINE level so that these messages are not all shown: Flushed API call count log, Handling Quota log, Requesting Counts log, and Sending API calls log. (APIM-1734)

    • The API Key Call Count Resource log is changed to a FINEST level so that these messages are not all shown. (APIM-1422)

Boomi Integration


API Service component

Feature:

  • You can use the HTTP PATCH method as a REST endpoint in an API Service component. (APIM-410)

    Restriction: Currently, you can manually generate the PATCH HTTP method. However, the importing of PATCH HTTP method endpoints is not supported.
    Note: This feature has companion changes covered in the Connectivity section of these release notes.

    To learn more about this feature, see the topic API Service REST tab.

Dynamic process properties

Fix:
  • The process Extensions dialog erroneously did not display any leading or trailing spaces within a dynamic process property name, though such spaces may have been intentionally included. With this fix, dynamic process property names are displayed with leading and trailing spaces, where applicable. (INT-2147)

Integration packs

Fix:
  • If a parent account made changes to an integration pack while its release was already scheduled, child accounts that applied the release early had to wait until the targeted release date to get these new changes. With this fix, integration pack publishers can push subsequent updates to users that have already installed a previous pending update prior to the target release date. Child accounts that apply the release early automatically receive new updates made in the parent account. (INT-1063)

JSON profiles

Known issue:

  • Incorrect mapping results may occur when using profiles in which instance identifiers are defined. If you encounter this issue, request Atom v20.07.1, which contains a fix for this issue, from Support. (B2B-1094)

    Note: Atom v20.07.1 was applied to Boomi public Atom Clouds as part of the July 2020 release.

Feature:

  • You can define nested instance identifiers for repeating array elements. (B2B-1004)

    To learn more about this feature, see the topic JSON profiles.

Meta information document properties

Feature:

  • New document properties, Listener Batch Index and Listener Batch Payload Sequence, let you retrieve metadata for payloads submitted using listener batching from SDK connectors with listeners. Listener Batch Index corresponds to the index provided when a batch is created, and Listener Batch Payload Sequence represents the order in which a payload is added to the batch. (CON-557)

    To learn more about this feature, see the Meta information document properties and Implementing the Listen operation topics.

Shared Web Server panel

Fix:

  • When an SSL Certificate is updated, the previous version was referenced in the component XML. With this fix, the component XML is updated to the updated SSL Certificate version. (APIM-906)

SSO Options

Features:
  • Single sign-on (SSO) users have the ability to use the new Sign Out Redirect URL field in Setup > SSO Options to specify the page that displays upon signing out of the AtomSphere platform. (ADSEC-622)

    Note: This feature has companion changes to the Account Single Sign-on Configuration object in the AtomSphere API — see the AtomSphere and Partner API section of these release notes.

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

  • SSO users are automatically redirected to the page set as the Sign Out Redirect URL when their user session is terminated due to inactivity. This applies only to users of accounts with the Lock and terminate inactive sessions feature enabled in Setup > Security and for users who set Sign Out Redirect URL in Setup > SSO Options. (ADSEC-801)

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

Tracked documents

Fix:
  • In some cases, tracked document retrieval did not display search results for executions run on Atoms in any time zone ahead of the GMT time zone. With this fix, search results are improved to return the correct documents for all time zones. (PS-1076)

XML profiles

Known issue:

  • Incorrect mapping results may occur when using profiles in which instance identifiers are defined. If you encounter this issue, request Atom v20.07.1, which contains a fix for this issue, from Support. (B2B-1094)

    Note: Atom v20.07.1 was applied to Boomi public Atom Clouds as part of the July 2020 release.

Features:

  • You can define nested instance identifiers for repeating elements. (B2B-1003)

    To learn more about this feature, see the topic XML profile instance identifiers.

  • XML profile imports are improved to better handle large XML schemas that use reference-type definitions. (INT-2304)

AtomSphere API and Partner API

Account Single Sign-on Configuration object

Feature:
  • You can use the Account Single Sign-on Configuration object to programatically GET and UPDATE the signoutRedirectUrl field value. (ADSEC-622)

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

    To learn more about this feature, see the topic Account Single Sign-on Configuration object.

Component Reference object

Feature:
  • The new Component Reference object allows programmatic retrieval of all components which reference a given component ID. GET and QUERY operations are supported. This feature enables identification of component references similar to the Show Where Used utility in Component Explorer. (INT-1682)

    To learn more about this feature, see the topic Component Reference object.

Deprecated objects

Feature:
  • Operations on deprecated objects return a warning header in the response informing users that the object is positioned for retirement on a specified date. Although deprecated objects will remain usable for a period of time, Boomi highly recommends using newer API functionality. (INT-1717)

    To learn more about this feature, see the topic API versioning and deprecation policy.

Environment Extensions object

Feature:
  • When updating an object, a request no longer needs to include the entire set of extension values. “Partial updates” are now supported — only the extension values requiring modification need to be included in the request. Partial updates are considered a Tech Preview feature and are not recommended for use in production. (INT-1505)

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

Folder object

Fix:
  • Using a QUERY request with an empty filter previously returned an error. With this fix, a QUERY request with an empty filter returns all folders found in the given account’s Component Explorer. (INT-2278)

Trading Partner Component object

Fix:

  • An error occurred while processing a request that should have returned a Trading Partner in which the value of the encryptionAlgorithm field for AS2 communication corresponded to an AES encryption type. With this fix, Trading Partners meeting that description are retrievable. (B2B-1016)

Connectivity


Amazon EventBridge (Tech Preview) connector

Features:

  • “Detail” is now an accepted object type in the request profile, letting you easily map to entries without requiring a string value. The connector accepts the value of “Detail” in object or string form and converts the object entry into a string before sending it to Amazon EventBridge—which expects a string value.

  • The response profile now matches the output document, enabling easy usage of the output document for further processing.

HTTP PATCH Client connector

Feature:

  • The connector supports proxy configurations, allowing Atom owners and users to configure connections to proxy servers with authentication on their Atom. As a part of this effort, non-proxy host support is enabled so Atom owners can specify a list of host endpoints that they do not want to go through the proxy server. (CON-639)

Listen connectors

Features:

  • SDK connectors with listeners can be approved by Boomi for public use in Boomi Integration on Atoms and Molecules. However, these listeners will not run on Boomi public Atom Clouds unless approved. This classifies the connector as a multi-tenant connector. Atom Cloud owners have the option to enable non multi-tenant listeners to run on their private Atom Cloud by setting the Listener Startup Mode container property (com.boomi.container.startListeners) to ALL. Additionally, owners of private connectors in a private Atom Cloud can still run the listener on their Atom Cloud. (CON-1385)

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

  • For SDK connectors with listeners, Atom owners can control the number of listener batches that a listener instance is allowed to create. Atom owners can manage these privileges with the new Maximum Number of Active Batches per Listener container property. (CON-556)

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

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

  • SDK connectors with listeners now provide additional metadata for payloads submitted using listener batching. As a result, users can retrieve metadata for the new document properties, Listener Batch Index and Listener Batch Payload Sequence. Listener Batch Index corresponds to the index provided when a batch is created, and Listener Batch Payload Sequence represents the order in which a payload is added to the batch. (CON-557)

    To learn more about this feature, see the Meta information document properties and Implementing the Listen operation topics.

Fix:

  • Listen operations may not successfully execute due to the Atom returning the incorrect Connector implementation instance (ConnectorContext) to the Connector implementation. With this fix, the Atom returns the correct instance and Listen operations succeed as expected. Additionally, developers building a custom connector can utilize the getContext().getConnector() method in their connector's connection or operation. (CON-1251)

Microsoft Azure Cosmos DB (Tech Preview) connector

Feature:

  • The Microsoft Azure Cosmos DB (Tech Preview) connector allows you to transfer data from/to Microsoft Azure Cosmos DB servers using Boomi Integration and REST APIs. These REST APIs provide access to Microsoft Azure Cosmos DB resources to Get, Update, Delete, Create, Upsert and Query documents from Collections and Databases. (CON-1537)

    To learn more about this feature, see the topic Microsoft Azure Cosmos DB (Tech Preview) connector.

Microsoft Dynamics 365 for Customer Engagement connector

Feature:

  • Previously the connector bypassed and did not apply the Proxy Host, Proxy Port, Proxy User ID, Encrypted Proxy Password, and Non Proxy Hosts Atom proxy settings (container properties). Because of this, the connector could not be used in situations requiring a connection to a Dynamics 365 for Customer Engagement service through a proxy. With this feature, the Atom proxy settings are honored and applied using the Honor Atom Proxy Settings option. (BOOMI-42464)

    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 the connector bypassed and did not apply the Proxy Host, Proxy Port, Proxy User ID, Encrypted Proxy Password, and Non Proxy Hosts Atom proxy settings (container properties). Because of this, the connector could not be used in situations requiring a connection to a Dynamics 365 for Finance and Operations service through a proxy. With this feature, the Atom proxy settings are honored and applied using the Honor Atom Proxy Settings option. (BOOMI-42463)

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

MQTT connector

Security enhancement:

  • This release includes a security enhancement for customers using authentication in their MQTT connections. MQTT users will receive a system message in AtomSphere with detailed instructions to help facilitate this change. (CON-1332)

    To learn more about this security enhancement, see the topic MQTT connection.

Fix:

  • Extensions for the MQTT connection do not currently display and cannot be set in the environment Extensions dialog. With this fix and by utilizing the security enhancement (CON-1332), extensions appear as expected and can be set. (CON-1349)

NetSuite connector

Security enhancement:

  • This release includes a security enhancement for customers using NetSuite token-based authentication (TBA). NetSuite TBA users will receive a system message in AtomSphere with detailed instructions to help facilitate this change. (CON-1252)

    To learn more about this security enhancement, see the topic NetSuite connection.

OData Client connector

Feature:

  • Previously the connector bypassed and did not apply the Proxy Host, Proxy Port, Proxy User ID, Encrypted Proxy Password, and Non Proxy Hosts Atom proxy settings (container properties). Because of this, the connector could not be used in situations requiring a connection to an OData service through a proxy. With this feature, the Atom proxy settings are honored and applied using the Honor Atom Proxy Settings option. This applies only to OData V4.0. (BOOMI-9860)

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

Oracle E-Business (EBS) connector

Fix:

  • Previously released Oracle E-Business (EBS) connector fixes (CON-604, CON-716, CON-1074) introduced an Unknown Error during process execution when using PL/SQL stored procedures having OBJECT type input/output parameters with multiple input documents. With this fix, the stored procedures execute as expected and process execution is successful. (CON-1233)

Salesforce connector

Fix:

  • When using the Salesforce connector with Bulk API v2 to upload data, not all records processed by the connector were received by Salesforce, resulting in data inadvertently being lost. With this fix, the connector constructs the batch differently to avoid data loss under certain circumstances. Additionally, to address a Salesforce issue preventing batches larger than 10 MB from being processed, the connector reduces the batch size to 10 MB to ensure all records can safely be processed by Salesforce. (CON-1466)

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

Web Services Server connector

Feature:

  • You can use the HTTP PATCH Method as a REST endpoint in a Web Services Server operation.

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

Connectivity development


Connector SDK

Features:

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

  • The maximum size of a document, inputData, and payload in the SizeLimitedUpdateOperation.java class is now configurable using a new container property, com.boomi.container.updateOperation.maxSize. (CON-652)

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

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

Master Data Hub

Modeling

Fix:

  • An error occurred when attempting to deploy an oversized model. With this fix, a model cannot be published if the aggregate size of its fields exceeds 65,331 bytes, exclusive of collection fields and reference fields. (HUB-708, HUB-899)

    To learn more about the model size limitation, see the topic Model design.

Repository API

Feature:

  • The Update Golden Records operation can be used to change the source entity to which a specified golden record is linked. The entity’s optional grid attribute is used to specify the ID of the golden record. (HUB-870)

    To learn more about this feature, see the topic Update Golden Records.

Stewardship

Fix:

  • When the data grid in the Golden Records page was filtered by a source entity ID containing pipe “|” characters, all matching golden records were not listed in the grid. With this fix, filtering in that manner has the expected effect on the contents of the grid. (HUB-753)

Transactional workflow

Fixes:

  • When an incoming entity specified an UPSERT operation on a collection item, if a collection field was omitted from the collection item, the field’s value in the golden record was nulled. With this fix, in this scenario the value of the omitted collection field in the golden record is retained, as expected. (HUB-754, HUB-861)

  • When an incoming entity specified an UPSERT operation on multiple key field values in a collection item, if one of the key fields was a reference field, only that key field value was respected. With this fix, in this scenario the values of all specified key fields are respected, as expected. (HUB-818)

B2B/EDI Management


Note: See the AtomSphere API and Partner API section of these release notes for information about a B2B/EDI Management-related fix in the July 2020 release.

EDIFACT document handling

Fix:

  • When a document with a loop containing multiple segments was read, the second segment was not split from the first. With this fix, a new option, First Segment of Loop is Required, is available in the EDIFACT profile’s Options tab. Select this option to require that the first segment in a loop be present if that segment is configured as Mandatory in the profile. (B2B-894)

EDI profiles

Known issue:

  • Incorrect mapping results may occur when using profiles in which instance identifiers are defined. If you encounter this issue, request Atom v20.07.1, which contains a fix for this issue, from Support. (B2B-1094)

    Note: Atom v20.07.1 was applied to Boomi public Atom Clouds as part of the July 2020 release.

Feature:

RosettaNet trading partner components

Fix:

  • If, in a RosettaNet trading partner component, one set Global Usage Code to Production and then saved and closed the component, upon reopening the component, the setting was falsely shown as Test. With this fix, upon reopening the component, the setting is accurately shown as Production. (B2B-955)

API Management

Authentication Brokers and API Gateways

Features:

  • The Configure Server > External Authentication page is redesigned into a table structure to provide a better overview of the Authentication Brokers and Authentication Sources. (APIM-1551, APIM-1553)

    To learn more about this feature, see the topic External Authentication.

  • You can set a custom Authentication Broker com.boomi.plugin.authservice.managementPort property to control the JMX management port. If you do not set this property, the default is 18969. (APIM-438)

    To learn more about this feature, see the topic Authentication Broker settings.

Developer Portal

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

Boomi Flow

The following information identifies the new features and fixes in Boomi Flow Core releases 1.154.7, 1.155.0, 1.156.0, 1.157.0, 1.158.0, System Flows 1.53.0, 1.54.0, Tooling 2.22.0, 2.23.0, 2.24.0, 2.25.0, 2.25.1, Twilio service 2.2.0, and User Interface 3.20.0, 3.21.0.

Core

Fixes:

  • An "Object reference is not set to an instance of an object" error was displayed when executing a subflow where public values were not referenced by the subflow. With this fix, the error is no longer displayed, and subflows that do not include public values referenced by the subflow will run as expected. (FLOW-1703)

  • If a user had previously rejected a tenant invitation to an organization, accepting any subsequent invitations would not result in the user successfully joining the organization. With this fix, accepting an invitation allows a user to join the organization, regardless of whether the user had previously rejected a tenant invitation. (FLOW-1490)

  • In certain instances of flow execution, some database connections were not correctly disposed of, potentially resulting in resource issues and error messages such as “Error reading from stream”. With this fix, any affected database connections are now correctly disposed of in alignment with Boomi Flow engine database disposal methods. (FLOW-1969)

  • Message actions were not being executed in the specified sort order, and were instead being executed using the position defined in the metadata. With this fix, message actions are executed in the correct order, as specified in the Order column. (FLOW-1931)

  • The flowOut setting on an outcome was not being cleared correctly upon deletion. With this fix, this setting is cleared from the metadata upon deletion. (FLOW-1796)

  • Using the DELETE /api/admin/1/organization/tenants/{id} endpoint to delete a subtenant from the tenant that a user is currently logged into would result in a successful request, but the subtenant would not be removed from the organization. With this fix, the request will be unsuccessful, and an error message will indicate that subtenants cannot be added or removed to/from organizations. (FLOW-1510)

  • When a user attempts to navigate away from an authorized swimlane for which they do not have access, inconsistent navigation behavior or an error may occur. With this fix, the user is able to correctly navigate to other authorized map elements in the flow. (FLOW-1621)

  • When using historical navigation, multiple navigations between the same map elements would result in the breadcrumb trail collapsing to minimize the items displayed. With this fix, duplicate map element navigation is removed so that all navigation is displayed, even if it has occurred multiple times between the same map elements. (FLOW-2007)

  • When using historical navigation, navigating to a map element using the top-level navigation bar resulted in the addition of the map element page as another item in the breadcrumb trail. With this fix, navigating to a map element using the top-level navigation bar results in the clearing of the trail and an update of the trail so that it starts again, with the selected map element page as the first item. (FLOW-1954)

System Flows

Fixes:
  • All compatible values were not made available for selection when updating or removing from lists in an operator map element. With this fix, all object/list values of the same type as the original list are correctly listed and available for selection. (FLOW-1767)

  • When setting up page conditions on a page map element, the Criteria drop-down menu on the Page Rule panel displayed duplicate criteria options. With this fix, duplicate criteria options are no longer displayed. (FLOW-462)

Tooling

Features:
  • Selecting the Enable historical breadcrumb navigation option in the Flow Properties form enables the new historical navigation feature. (FLOW-1548)

    Historical navigation can be added to a flow to enable users to easily navigate to previously visited pages. If historical navigation is enabled, breadcrumb-style navigation links are included at the top of each flow page, enabling users to quickly navigate back through their page history to previously visited pages.

    A new link is added to the breadcrumb navigation each time a user clicks an outcome to navigate to the next location in the flow path, such as the next map element in the flow, or to another map element in a subflow. In this way, the breadcrumb links trail is built up as the user navigates forward through the flow.

    To learn more about this feature, see the topic Historical navigation.

  • The Platform Instances drop-down menu is updated to allow regional flow Execution restrictions to be applied to the Canada (CA) and/or Singapore (SG) platform instances. This feature enables you to specify whether these new regional platform instances are allowed to execute a flow. (FLOW-1945)

    To learn more about setting up regional restrictions, see the topic Restricting tenant flow access by region.

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, with the user interface updating to reflect the edited page metadata. (FLOW-2098)

  • If a user clicked outside of the Flow Library Overwrite existing elements? window when attempting to import an existing Flow Library template, the window closed. With this fix, clicking outside of the window will not affect it, and it will be necessary to click Cancel or Confirm to continue. (FLOW-712)

  • 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, in this scenario the Create New Page form is not displayed. (FLOW-1742)

  • Searching for values in the value picker previously sent multiple API requests when implementing the 'search as you type' functionality, resulting in decreased search performance and accuracy. With this fix, the search functionality is optimized so that search results are accurately and quickly returned. (FLOW-1330)

  • The positioning of layout areas in the Page Layout Editor would become inconsistent if the browser was resized down below certain dimensions. With this fix, the positioning of affected layout areas has been optimized to prevent layout inconsistencies in this scenario. (FLOW-539)

  • When editing a basic page condition in the Page Layout editor, some value/component selections created in the basic condition were not displayed within the relevant fields on the Rule panel for the condition, resulting in the insertion of an '[undefined]' value into the rule. With this fix, the fields are correctly displayed. (FLOW-1994)

  • When setting up a Navigation Override on an operator map element, the Which item do you want to override? list did not update to include changes made to the selected navigation menu. With this fix, the list correctly updates to include changes made to the navigation menu. (FLOW-908)

Twilio service

Fix:
  • An "Invalid URL" error message was displayed when running a flow using the Twilio service to trigger the sending of SMS messages from a flow, resulting in SMS messages not being sent correctly. With this fix, flows using the Twilio service no longer display the error message, and SMS messages are successfully sent. (FLOW-1744)

User Interface

Feature:
  • Functionality has been added to the user interface to support the upcoming historical breadcrumb navigation feature. See Tooling below for details on this new feature. (FLOW-1544)

Fixes:
  • No error message was displayed to users to inform them that the Boomi Flow Amazon S3 service does not support file listing. With this fix, an error message "Listing all files is not yet supported in the S3 Service" is displayed. (FLOW-1597)

  • Offline flow caching was sometimes not being performed correctly, resulting in missing cached values or caching not being carried out correctly. With this fix, offline flow caching behavior is carried out correctly when a flow is run offline. (FLOW-1618)

  • It was not possible to edit date/time fields in an editable table component. With this fix, clicking or tapping on a date/time field enables editing of the field contents. (FLOW-473)

  • When a user selected a menu item from a navigation drop-down menu, the drop-down menu continued to display. With this fix, the drop-down menu correctly disappears upon selection of one of its items. (FLOW-1733)

  • When using historical navigation, if a user expanded the breadcrumb trail, and then navigated via an outcome to another page/step in the flow, the trail would remain in an expanded state. With this fix, the trail now re-collapses upon movement within the flow. (FLOW-2004)

  • When using historical navigation, multiple navigations between the same map elements would result in the breadcrumb trail collapsing to minimize the items displayed. With this fix, duplicate map element navigation is removed so that all navigation is displayed, even if it has occurred multiple times between the same map elements. (FLOW-2007)

  • When using historical navigation, the historical navigation 3 only listed any previous map elements that had been navigated to. With this fix, the name of the current map element is also displayed at the end of the trail, to inform the user of their current map element location. (FLOW-1953)