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


Data Collection

Feature:

  • Boomi Resolve is not accessible to users that opt out of Data Collection. (PS-804)

Guided tours

Feature:

  • Boomi introduces a series of in-application guides to help new users get started on the AtomSphere platform. With these new guides, users can quickly tour a variety of pages and services within AtomSphere, learn how to use new features that coincide with monthly product releases, and participate in important surveys that could impact future enhancements to the platform. (ADSEC-641)

Home/Welcome page

Feature:

  • The new AtomSphere home page opens when you sign in to the platform, serving as your new welcome experience. The home page contains information from all areas of the platform, as well as links to additional information from other Boomi resources such as help content, the Boomiverse community, and training. (UNI-373, UNI-388)

Key-value pairs

Feature:

  • To enable connector development, infrastructure changes are applied to support key-value pairs in future Connector SDK releases. (CON-434, CON-442, CON-614, CON-769)

Atoms, Molecules, and Atom Clouds


Atom Cloud properties

Feature:

  • The new Force Restart Override for Molecule Scale Down property allows users to configure the number of milliseconds that the AtomSphere platform waits for processes to finish before it forces the Molecule node to stop. (RUN-345)

  • The new Async Message Poller Timeout for Molecule Scaledown property allows users to configure the maximum number of milliseconds that the AtomSphere platform waits before assuming that a step within a node's shutdown process has failed. (RUN-387)

    To learn more about these features, see the topic Properties panel, Advanced tab.

Cluster Status panel

Feature:

  • Ease of use is improved for Molecule and Atom Cloud owners deleting nodes and viewing current node statuses on the Cluster Status panel of Atom Management. The changes are as follows:
    • The star indicating a Molecule or Atom Cloud’s head node now appears in the Node ID column.

    • The Action menu previously used to delete a node is now converted into a Delete button.

    • The Status column displays a more comprehensive, descriptive list of statuses to indicate the health and state of the node.

      (RUN-515, RUN-516, RUN-518)

    To learn more about this feature, see the topic Cluster Status panel.

Known issues:

  • Though a node may be successfully deleted, its status does not consistently show a “Deleted” status on the Cluster Status panel.

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

  • Processes that are executed as forked executions are properly aborted based on configured timeouts, but show as hanging in Process Reporting.

  • 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)

Public Atom Clouds

Boomi is committed to modernizing its integration platform to ensure ongoing reliability, performance, and scalability. As part of this effort, migration events will be scheduled to occur during 2020. You will receive an email notification 60 days in advance of a migration event that will include your account.

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

Security policies for Molecules and Atom Clouds

Fix:

  • When a policy value contained values with trailing backslashes, it caused the policy file to become misinterpreted. With this fix, values with trailing backslashes are accepted and no longer cause errors. (RUN-259)

Boomi Integration


Audit logs

Feature:

  • An audit log entry is now created when the account administrator unlocks an SSO user who is locked out of the AtomSphere platform. (ADSEC-607)

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

Fix:

  • When pausing or resuming listeners, an incorrect audit log action was recorded. With this fix, the correct audit log action is recorded when starting, resuming, and pausing listeners. (RUN-538)

Component Explorer

Feature:

  • Component Explorer’s load performance is improved. (INT-1956, INT-1737)

Component XML

Fix:

  • When viewing a component’s XML from the Revision History panel, the FullFolderPath attribute was erroneously omitted from the XML document. With this fix, the XML document includes the FullFolderPath attribute as expected. (INT-1999)

Document cache

Fix:

  • An error occurred when a multi-threaded process attempted to access the document cache. With this fix, a retry is imposed to prevent the process from failing. (RUN-45)

Email alerts

Fix:

  • Previously, some users experienced a delay in receiving Boomi alert emails, or did not receive them in some cases. With this fix, alert emails are sent as expected. (PS-829)

Environment extensions

Feature:

  • Previously, users were unable to update extensions using an extensions file larger than 32 MB. With this release, the size of accepted extensions files is increased to 64 MB. (INT-1749)

Listeners panel

Fix:

  • The Listeners panel in Atom Management failed to load when the Listener Startup Mode property was set to NONE or MULTI_TENANT in a Cloud’s Advanced Properties. With this fix, the Listeners panel loads, as expected, regardless of the value set in the Listener Startup Mode property. (RUN-72)

Process executions

Fix:

  • Previously, Hub Clouds were not configured to accept process attachments and caused Process Reporting to filter out MDM Listener processes. With this fix, MDM Listener executions are displayed as expected in Process Reporting. (ADSEC-596)

Process Reporting

Fix:

  • Previous error messaging was unhelpful to users who attempted to view process documents for a listener process run in low-latency mode or set with the Purge Data Immediately option. With this fix, error messaging is improved to be more descriptive as to why such documents are unavailable. (INT-422)

Profiles

Feature:

  • Messaging is improved for JSON and XML profiles that are truncated upon import. Profiles for deeply nested, recursive schemas are capped at a certain number of attributes to avoid infinite profiles. Messages now include information about the last rejected node, recursion level, or node to help users know where they can begin adding new elements manually. (INT-2055)

SSO users

Features:

  • When an SSO user is locked from the AtomSphere platform due to too many invalid login attempts or API Token entries, account administrators now have the ability to manually unlock SSO users from the User Management page. (ADSEC-567)

    Note: This fix required the re-release of the AtomSphere platform.

    To learn more about this feature, see the topic Unlocking a user with single sign-on access.

  • Error messaging is improved to be more helpful for SSO users who are locked out of the AtomSphere platform. New messaging details next steps, and how the account administrator must perform a manual unlock on behalf of the user. (ADSEC-667)

AtomSphere API and Partner API

Atom Security Policies object

Fix:

  • In Windows environments, Update operations on this object failed to properly update security policy files. With this fix, Update operations properly update security policy files, as expected. (RUN-293)

Audit Log object

Fix:

  • Objects returned by a GET or QUERY operation erroneously showed a “Delete” message rather than “Uninstall” when an Atom was uninstalled. With this fix, the appropriate Uninstall or Delete message is displayed depending on the action taken. Documentation is updated to describe differences between both terms. (RUN-43)

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

Folder object

Feature:

  • The new Folder object enables you to programmatically query for information about folders in a given account. You can use the Component Metadata or Component objects to retrieve the folder ID for a specific folder in Component Explorer, and then use that folder ID in a Get request on the Folder object to retrieve more details about that folder, such as its name, full path, and whether or not it is deleted. (INT-1916)

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

Listener Status object

Feature:

  • Objects returned by a Get or Query operation now include the connectorType attribute, which identifies the type of listener connector — for example: wss and queue. (RUN-615)

    To learn more about this feature, see the topic Listener Status object.

Node Offboard object

Feature:

  • The Node Offboard object enables you to programatically delete Molecule and Atom Cloud nodes, similar to how you delete nodes on the Cluster Status panel in Boomi Integration. The Node Offboard object allows you to delete both active, running nodes and nodes that are already shut down. (RUN-520)

    To learn more about this feature, see the topic Node Offboard object.

Process Schedules object

Feature:

Trading Partner Component object

Feature:

  • The qualifierValidation field (type boolean) is added to the object to coincide with the introduction in this release of the option to validate qualifiers for X12, EDIFACT, and HL7 document types. (B2B-918)

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

Connectivity


Amazon EventBridge (Tech Preview) connector

Feature:

  • This connector was released off cycle into production after the Apr 2020 release. Amazon EventBridge (Tech Preview) allows you to send any number of events to your AWS event buses that can then pass those events to target AWS services. (CON-1077)

    To learn more about this feature, see the topic Amazon EventBridge (Tech Preview) connector.

AS2 Shared Server connector

Feature:

  • This connector is updated to support the new capability to archive “raw” documents that pass through a Trading Partner at the process level. See the B2B/EDI Management section of these release notes for information about this feature.

Box connector

Fix:

  • Sending a JSON input document to the connector containing special characters (for example, an accent) resulted in an error on the server side indicating that the document contained invalid UTF-8 characters and could not be read. This applied to Create, Update, and Upsert operations. With this fix, requests the connector sends to the server are UTF-8 encoded to preserve the special characters and to prevent errors. (CON-913)

    To learn more about this fix, see the topic Box connector.

Coupa connector

Feature:

  • To align with the most current list of Coupa objects, the connector supports the latest Coupa API version 26. (BOOMI-41803)

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

Fix:

  • When the number of Query results was a multiple of the pageSize (by default, 50 - Coupa's paging limit for each query call), an error occurred and one more page appeared with zero results. With this fix, the connector ignores the last empty page to prevent errors. (CON-1160)

Fiix — Partner connector

Feature:

  • This connector was released off cycle into production after the official May 2020 release. The Fiix — Partner connector allows customers to seamlessly integrate Fiix’s Computerized Maintenance Management System (CMMS) with other systems, so they can access maintenance-specific data (assets, work orders, purchase orders, and more). Customers can then use these integrations with ERP systems like SAP, Microsoft Dynamics, NetSuite, and Sage for parts inventory adjustments and purchasing. (CON-1377)

    To learn more about this feature, see the topic Fiix — Partner connector.

Flow Services Server connector

Fixes:
  • A blank screen was being displayed to users of any flow where a connector operation took longer than 30 seconds to complete, resulting in the service connector failing over from a synchronous call to an asynchronous call. With this fix, a Sync Timeout setting is added to the Options tab in the Flow Service Operation configuration dialog. This setting is the time a request should wait, in seconds, before failing over from a synchronous call to an asynchronous call. (FLOW-1364)
    • The default is 30 seconds. To avoid timeout errors within a flow, do not set a value of 60 or more seconds.

    • This setting is applicable only if Service Type is set to Message Action.

Kafka connector

Feature:

  • When creating a connection and authenticating using Kerberos (GSSAPI), you can specify only the service name and have the connector build the service principal name (SPN) for each broker configured in the connection. In this way, you can configure a list of brokers with each having a different SPN. Currently, all configured brokers must use the same SPN. In support of this feature, the Service Principal field is renamed as Service Name/Principal. (BOOMI-42245)

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

Microsoft Dynamics 365 for Customer Engagement connector

Fixes:

  • The connector includes the following previously-released OData Client connector fixes (BOOMI-41348):

    • Remove an extra leading space in custom expressions. (BOOMI-24630)

    • Select a non-leaf node and receive all of its leaves, or select a leaf node without selecting an intermediate branch. (CON-122)

  • When gathering metadata from the service, the connector made individual requests for each execution of the Get, Query, and Delete operations, resulting in slow operation response times. With this fix, the metadata from the service is saved in the connector cache and is reused for each operation to produce faster response times. If caching the metadata impacts the Atom’s available memory, disable the caching by setting the com.boomi.connector.odata.disableMetadataCaching container property to true. (BOOMI-41425)

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

Microsoft Dynamics 365 for Finance and Operations connector

Fixes:

  • The connector includes the following previously-released OData Client connector fixes (BOOMI-41348):

    • Remove an extra leading space in custom expressions. (BOOMI-24630)

    • Select a non-leaf node and receive all of its leaves, or select a leaf node without selecting an intermediate branch. (CON-122)

  • When gathering metadata from the service, the connector made individual requests for each execution of the Get, Query, and Delete operations, resulting in slow operation response times. With this fix, the metadata from the service is saved in the connector cache and is reused for each operation to produce faster response times. If caching the metadata impacts the Atom’s available memory, disable the caching by setting the com.boomi.connector.odata.disableMetadataCaching container property to true. (BOOMI-41426)

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

NetSuite connector

Feature:

  • The NetSuite connector now supports connecting to NetSuite Version 2019 Release 2 (also known as v2019.2). (CON-955)

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

Fix:

  • When using NetSuite versions 2015.1 and older with Atoms on Java 7, operation browsing (Import Wizard) and process execution were not successful, and a process log error appeared. With this fix, the legacy NetSuite connector versions use TLS v1.2 for secure transmission and to prevent errors. (CON-1119)

OData Client connector

Fix:

  • When gathering metadata from the service, the connector made individual requests for each execution of the Get, Query, and Delete operations, resulting in slow operation response times. With this fix, the metadata from the service is saved in the connector cache and is reused for each operation to produce faster response times. If caching the metadata impacts the Atom’s available memory, disable the caching by setting the com.boomi.connector.odata.disableMetadataCaching container property to true. (CON-724)

    To learn more about this fix, see the topic OData Client operation (V 4.0).

SDK connectors

Feature:

  • You can select the document Tracking Direction for Get and Query operations. The default is Output Documents, but you have the flexibility to change this based on your needs. This setting affects which documents appear in Process Reporting. (CON-334)

SFTP V2 (Tech Preview) connector

Feature:

  • This connector was released off cycle into production after the Apr 2020 release. SFTP V2 (Tech Preview) allows you to transfer data from and to an SFTP server using Java Secure Channel (JSch). It enables uploading to a temporary file name, with a .tmp extension, until the operation is completed, to ensure that the file is not processed prematurely. In addition, when uploading a file to the target directory, if the filename already exists, you can choose to overwrite, append, create a new unique file name, or generate an error. (CON-1081)

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

Web Services SOAP Client connector

Fix:

  • The Encrypt Certificate was pulling the private certificate and the Decrypt Certificate was pulling the public certificate. This was the reverse of correct behavior. With this fix, the behavior is corrected: The Encrypt Certificate pulls the public certificate, and the Decrypt Certificate pulls the private certificate. (DS-2303)

    Note: This is a platform change. There is no connector update.

Workday Prism Analytics V2 (Tech Preview) connector

Feature:

  • This connector was released off cycle into production after the official May 2020 release. The Workday Prism Analytics V2 (Tech Preview) connector allows Workday customers to bring together data from any source to prepare, analyze, and securely share it within your organization - enabling business insights to drive better business decisions and outcomes. With the ability to bring in external data sources and govern them along with existing Workday Prism Analytics data, the business is empowered to generate financial and HR insights that can be shared across the organization. (CON-1345)

    To learn more about this feature, see the topic Workday Prism Analytics V2 (Tech Preview) connector.

Zuora REST connector

Fix:

  • Sending a JSON input document to the connector containing special characters (for example, an accent) resulted in an error on the server side indicating that the document contained invalid UTF-8 characters and could not be read. This applied to Create, Update, and Execute operations. With this fix, requests the connector sends to the server are UTF-8 encoded to preserve the special characters and to prevent errors. (CON-1156)

    To learn more about this fix, see the topic Zuora REST connector.

Connectivity development


Key-value pairs

Feature:

  • To enable connector development, infrastructure changes are applied to support key-value pairs in future Connector SDK releases. (CON-434, CON-442, CON-614, CON-769)

Master Data Hub

Modeling

Feature:

  • You can more easily select fields to include in a model’s record title format, especially in large models, by filtering the field selection list. To apply filtering, type in the search field above the list. (HUB-711)

    To learn more about this feature, see the topic Record Title Format tab.

Fixes:

  • 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)

    Note: Subsequent to the May 2020 release, the Repository was updated on Hub clouds to effectively roll back this fix. The fix will be rescheduled for a future release.
  • As a result of a new feature in the April 2020 release, the XML element names for reference fields and collection fields were no longer visible in field definition dialogs. With this fix, these element names are once again visible in the dialogs — Element Name for a reference field and Collection Tag for a collection field. A Copy button is added adjacent to the element name to make it easier to copy the element name to the system clipboard. (HUB-773)

  • An error occurred when attempting to deploy a model with a non-reference field name longer than 64 characters. With this fix, a model cannot be saved as a draft or published if it has non-reference fields with names longer than 64 characters. (HUB-822)

Reporting

Feature:

  • On the Historical Reporting page, a new option, Outbound Data > Delivered Update Requests, enables you to obtain historical counts of delivered source record update requests. (HUB-713)

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

Repository API

Fix:

  • Collection fields were erroneously omitted from Query End-dated Golden Record results. With this fix, query results are accurate. (HUB-768)

B2B/EDI Management


Note: All Trading Partner connectors and the AS2 Shared Server connector are updated in this release to add support for custom archiving logic — see “Document archiving” below. For processes using Trading Partner connectors that you have deployed to your multi-node Atom Clouds or Molecules, take these precautions:
  • While the release is in progress, do not execute processes using Trading Partner connectors that are deployed to your Atom Cloud or Molecule.

    You can monitor the progress of the release by visiting status.boomi.com.

  • Once the release is complete, stop and restart the Atom Cloud or Molecule.

  • Monitor process executions for any errors that occur during the rolling restart for the release, and retry any executions if necessary.

Document archiving

Feature:

  • You can now implement custom archiving logic for the “raw” documents that pass through a Trading Partner. This feature enables you to maintain archives anywhere.

    • If archiving is enabled in a Trading Partner Start shape, inbound documents are archived after any data processing occurs but before EDI processing occurs.

    • If archiving is enabled in a Trading Partner shape, outbound documents are archived after EDI processing occurs but before any data processing occurs.

  • Archiving occurs by means of processing defined in a shape’s Archive path. (B2B-906)

    Note: All Trading Partner connectors, the AS2 Shared Server connector, and the Atom software are updated to support this feature.

    To learn more about this feature, see the topic Trading Partners.

Document handling

Fixes:

  • The Security Info ID for an X12 interchange was not listed for selection in the Set Properties shape’s Choose Property dialog for setting as a document property. With this fix, the Security Info ID can be set as a document property. (B2B-858)

  • For a Tradacoms interchange using the AS2 communication method, specifying the AS2 filename using a dynamic document property had no effect. With this fix to the Tradacoms EDI connector, the dynamic document property value overrides the AS2 filename, as expected. (B2B-872)

Document validation and acknowledgment

Feature:

  • Previously, there was no way to disable validation of qualifers for X12, EDIFACT, and HL7 document types. With this release, there is a new option, Validate Qualifiers, for registered document types in the Document Types tab in X12, EDIFACT, and HL7 trading partners. Validate Qualifiers is selected by default for a document type. To disable qualifier validation for the document type, clear Validate Qualifiers. (B2B-913)

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

Fixes:

  • In some cases, when Filter Functional Acknowledgments was selected for a receiving EDIFACT trading partner, CONTRL functional acknowledgment documents were errouneously routed to the Start shape’s Documents path. With this fix to the EDIFACT trading partner connector, CONTRL functional acknowledgment documents are routed to the Start shape’s Acknowledgments path, as expected. (B2B-742)

  • When an X12 document with a missing mandatory segment in the first of two loops was validated, the document was acknowledged. With this Atom fix, such a document is rejected with an error, as expected. (B2B-995)

API Management

Environment to API Gateway migration

Feature:

  • Attaching an environment to an API Gateway happens through a step-by-step process on the Environment Migration tab of the Configure Server > Gateways page. This process guides you through setting up the environment and API Gateway configurations. (APIM-190)

    This new guided process replaces the previous way to attach an environment to an API Gateway using the Environment section on the Gateway Settings panel of the API Gateway.

    To learn more about the environment to API Gateway migration, see the topics Migrating an environment to or from an API Gateway and API Gateways .

Authentication Brokers and API Gateways

Fixes:

  • API components deployed to an API Gateway with Dynamic Document Properties were not including the Dynamic Document Properties headers in the CORS “access-control-allowed-headers” header causing API requests to fail if CORS standards were required. With this fix, the Dynamic Document Properties headers are included in new API components deployed to an API Gateway. Existing deployed API components must be redeployed to the API Gateways to correct this issue. (APIM-1223)

  • Rolling restarts on the API Gateway caused requests sent to the API Gateway to fail for a period of time. With this fix, rolling restarts of the API Gateway do not cause significant request failures. (APIM-1406)

Developer Portal

Feature:

  • If a Developer Portal subscription is set with a future enabled date, the Pending Status indicates this on the Developer Portal's Subscriptions page. It is no longer necessary to drill into the specific subscription's details. (APIM-1256)

Boomi Flow

The following information identifies the new features and fixes in Boomi Flow Core releases 1.149.0, 1.150.0, 1.151.0, 1.152.0, 1.153.0, 1.154.0, 1.154.1, 1.154.2, 1.154.3, Email Service 1.1.3, 1.1.4, Hub Service 1.1.0, SQL Service 2.3.0, 2.3.1, 2.3.2, System Flows 1.50.0, 1.51.0, 1.52.0, Tooling 2.19.0, 2.20.0, and User Interface 3.14.2, 3.14.3, 3.15.0, 3.16.0, 3.17.0.

Core

Features:

  • Performance improvements have been made in order to reduce response times from the Boomi Flow engine, improve the general performance of running flows, and improve performance of flows that contain large and/or complex values. (FLOW-1412, FLOW-1485)

  • Support is added for the new client certificate authentication for services functionality. (FLOW-957)

  • The ability to navigate to a map element within the current flow from a subflow is added to core engine functionality. (FLOW-1531)

Fixes:

  • An intermittent error was causing an issue when using Data Action Filters with a Database Load map element, where the filter was not being attached correctly to the map element. With this fix, Data Action Filters operate correctly with Database Load map elements. (FLOW-1537)

  • An "Object reference not set to an instance of an object" error is displayed when a subflow is launched, where the parent flow contains one or more public values not present in the subflow. With this fix, the error is no longer displayed and subflows are launched correctly, even if the parent flow contains one or more public values not present in the subflow. (FLOW-1528, FLOW-1703)

  • Flows containing one or more ContentObject values with no default object data and with the nullPasswords option enabled were not being exported correctly. With this fix, flows of this type can be exported. (FLOW-1558)

  • List value pointers were sometimes not being reset correctly between elements. With this fix, list value pointers operate correctly. (FLOW-1570)

  • Outcomes are not re-positioned correctly on the flow canvas when a user moves the outcome line, resulting in unusual and unwanted outcome positions and configurations on the canvas. With this fix, a user can now right-click on an outcome on the flow canvas and select Reset Position to convert the outcome back to it’s original position. (FLOW-1496)

  • Users requesting a password reset or attempting to create a trial account in Boomi Flow are experiencing issues where the password reset emails provide a link to a page that displays a loading spinner and a "Please check your inbox. You must verify the password reset request before we can continue with this request" message. With this fix, the password can be correctly reset. (FLOW-1722)

Email Service

Features:
  • The mailing library used by the Email Service has been updated, and additional internal logging functionality added. (FLOW-1573)

Fixes:
  • An error was displayed when running a flow that uses the Send Email with Decision Request message action. With this fix, flows that use this type of message action with the Boomi Flow email service operate as expected. (FLOW-1557)

Hub Service

Fixes:
  • A "null pointer was encountered" error message was displayed when saving a golden record to Master Data Hub using the Hub service. This is due to a source ID not being correctly assigned to the golden record during the save process. With this fix, golden records are correctly saved to Master Data Hub by the Hub service. (FLOW-1579)

  • Previously, it was possible to install and configure the Hub service without defining the Hub Username and/or Hub Token configuration values. With this fix, an error message is displayed to inform the user that all required configuration values must be defined in order for the Hub service to operate correctly. (FLOW-1384)

SQL Service

Features:
  • Security improvements have been made to parameter binding in the SQL service. (FLOW-1505)

Fixes:
  • A "Text 'False' could not be parsed at index 0" error message was displayed in table components that used a Where filter with the Is Empty criteria. With this fix, table components that use this filter and criteria combination are displayed correctly and without an error message. (FLOW-1617)

  • Loading data for PostgreSQL filtering that used conditions with integers and dates was not being fetched correctly, resulting in an "operator does not exist: integer = character varying Hint: No operator matches the given name and argument types." error message being displayed to a flow user. With this fix, PostgreSQL filtering operates as expected. (FLOW-1577, FLOW-1586)

  • Values set to use a 'null' value caused filtering issues for Boomi Flow components that use Starts WithEnds With and Contains SQL syntax. For example, setting a default value to 'null' returned no results when searching on a table component. With this fix, values that use 'null' return all results for a component, as the 'null' is treated as an empty string value (""). (FLOW-1577)

System Flows

Features

  • Client certificate authentication can now be added when installing or editing a ‘Boomi Integration Flow Service’ service in your tenant. This enables Boomi Flow builders to easily add and manage X.509 client certificate authentication for any flow connecting to the Boomi Integration service. (FLOW-960)

  • Support is added for the new page layout naming functionality in the tooling. (FLOW-623)

  • When configuring an Add Value Of operation on an operator map element, the list of values available to reference in the Which Value do you want to reference? field includes properties from the selected object, rather than only valid number values. With this fix, only valid number values are displayed in the value picker for this field. (FLOW-1407)

  • When editing message actions in a message map element, the Service and Action information is not displayed in the Message Action configuration panel. With this fix, the Service and Action information is displayed at the top of the Message Action configuration panel. (FLOW-1386)

Tooling

Features:

  • Support is added for the new client certificate authentication for services functionality. (FLOW-957)

  • When creating a new page layout, the user is now prompted to enter a name for the page layout. When a user clicks New Page Layout to create a new page layout, the Create New Page form is displayed, allowing the user to enter a name for the new page layout. Once the user has named the page and clicked Save, the new page is displayed in the Page Layout Editor. The page layout tab will change to reflect the name for the new page layout once the user clicks the Save icon in the right-hand menu. (FLOW-623)

Fixes:
  • An additional empty page layout tab is created if a user creates a new page layout but does not enter any values into the page configuration panel, before returning to the flow canvas and clicking New Page Layout again, with the existing new page layout still open. With this fix, the original new page layout tab is selected if a user attempts to create a second new page layout before configuring the first new page layout. (FLOW-1542)

  • Input fields on the Integration Flow Service configuration screens have been set to a more uniform width. (FLOW-1376)

  • Outcomes are not re-positioned correctly on the flow canvas when a user moves the outcome line, resulting in unusual and unwanted outcome positions and configurations on the canvas. With this fix, a user can now right-click on an outcome on the flow canvas and select Reset Position to convert the outcome back to it’s original position. (FLOW-1496)

User Interface

Features:
  • The behaviour of the Sync Flow button can be defined for an offline flow, by adding the instantReplay setting into an offline player. (FLOW-1453)

    • False: Clicking the Sync Flow button displays the Go Online form, allowing all offline requests to be viewed and replayed individually by a user as required. This is the default setting.

    • True: Clicking the Sync Flow button displays the Go Online form, but automatically replays all offline requests immediately before closing the form and returning the user to the flow.

  • The user interface has been updated to use aliased Run API endpoints. (FLOW-1329)

  • While using an offline flow, you are notified when network connectivity is lost and restored. (FLOW-1454)

    • When a flow enters an offline state, a notification is displayed to inform you that you are working offline and should synchronize your offline work when reconnected.

    • When an offline flow enters an online state, a notification is displayed to inform you that you are now working online and can synchronize your offline requests when required.

Fixes:
  • Attempting to close a browser tab running Boomi Flow, but canceling the closure by clicking Cancel on the Leave Site? dialog, resulted in looping synchronization requests within the Boomi Flow engine. With this fix, cancelling a browser closure no longer causes a synchronization loop. (FLOW-1326)

  • Enabling client-side validation in a custom player resulted in client-side validation being incorrectly performed on a Date/Time input component as soon as the component was loaded on the page. With this fix, client-side validation is performed correctly. (FLOW-1444)

  • File upload components would not successfully upload a file when an offline flow was replayed online. With this fix, file upload components will successfully upload files in an offline flow, once the flow is online and the file upload is replayed. (FLOW-1431)

  • Github ui-core/ documentation was returning a '404' error page. With this fix, the ui-core/ documentation on Github is available. (FLOW-1406)

  • Performing a search on an empty table populated with data not retrieved from a service resulted in an error message being displayed. With this fix, table searches are correctly performed. (FLOW-1422)

  • Sorting a table column containing one or more null values resulted in an error message being displayed. With this fix, table columns can be sorted, even if the column contains null values. (FLOW-1555)

  • Table components using the formatting.isEnabled player setting set to 'true' displayed an error message if a service request returned a null value. With this fix, table components configured to use this player setting display correctly, even if the service request returns a null value. (FLOW-1554)