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


    Release Control

    Feature:

    • The Atom & Connector Versions panel is updated so you can view and selectively apply pending rollback and update versions for your Atoms and connectors. You can even accept early access releases that cross release boundaries and traditional Release Control, allowing you to test and react to changes quickly. If the pending versions are part of the release and you did not update early, you are automatically updated to that version once it is released. (CON-235)

      To learn more about this feature, see the topic Atom & Connector Versions panel.

    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 GBR Hub Cloud occurred January 25, 2020.

    • Migration of the Boomi USA East Hub Cloud (formerly US Hub Cloud) will be rescheduled.

    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.

    Atom Cloud attachments

    Fix:
    • Removing an Atom Cloud with a large number of attachments from an account group caused interruptions in Atom communication. With this fix, users can successfully remove Atom Clouds from account groups as expected. (RUN-278)

    Independent purge schedules

    Feature:
    • A new advanced Atom Cloud property, Purge Schedule for Components, enables you to configure the number of days to wait before purging test execution and browse component data held on your Atom, Molecule, or private Atom Cloud. Shared HTTP Server SSL Certificates and Certificate Authorization components are not purged as a result of enabling this property. (RUN-348)

      To learn more about this feature, see the Account properties panel and Purging of Atom Molecule or Cloud logs and data topics.

    Java upgrades

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

    Java security compatibility

    Feature:
    • To maintain compatibility with Java 1.8.0_231 version upgrades, the following NIST EC Curves were reintroduced to the Default TLS Algorithms in the java.security configuration file: sect283k1, sect283r1, sect409k1, sect409r1, sect571k1, sect571r1, and secp256k1. (RUN-320)

      To learn more about this feature, see topic Controlling Java security compatibility.

    Log messages

    Fix:
    • Previously, log messages did not provide adequate detail about processes discarded due to system loads. With this fix, improved log messaging provides detail about the specific transaction that was discarded, and includes information about what limits may have been exceeded. (RUN-314)

    Purging of Atom, Molecule, or Atom Cloud logs and data

    Fix:
    • The purge manager did not compress all eligible files. With this fix, the compression of eligible files for purging works as expected. (RUN-362)

    Security policies for Atom Clouds and Molecules

    Fix:
    • Users were shown an inaccurate error message when their SFTP connectors failed high permission JVM policies while running on an Atom Cloud. With this fix, accurate messaging for permissions errors is provided . (RUN-254)

    Boomi Integration


    Account Dashboard

    Fix:
    • When filtering the status of an Account Dashboard by Account Groups, the Offline Atoms gadget is slow to load results. With this fix, the performance of the Offline Atoms gadget is improved to produce filtered results more quickly. (INT-837)

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

    API Service component

    Fix:

    • On importing an endpoint for an API Service component from an external file, any supplementary XSD files with relative paths were rejected by the import wizard. With this fix, you can upload supplementary XSD files during an import of an endpoint from an external file to an API Service component. (APIM-615)

    Integration packs

    Fix:
    • When published, integration packs erroneously abided by the timezone of the user’s browser rather than the timezone of the schedule configured in the integration pack. With this fix, integration packs work as expected and abide by the timezone of the schedule. (INT-1206)

    Process reporting

    Fix:
    • The AtomSphere API connector failed when querying for more than 10,000 records. With this fix, the query can return up to 100,000 records. (PS-595)

    Process schedules

    Fix:
    • Non-numeric values entered in the configuration fields of advanced type process schedules were erroneously saved. With this fix, users cannot enter non-numeric values with the exception of special characters. (INT-1432)

    RSS feeds

    Feature:
    • RSS feeds are now off by default for newly created AtomSphere accounts. This change does not affect existing accounts. (INT-1307)

      To learn more about this feature, see the topic Account features management.

    Single sign-on

    Fix:
    • An unrelated, inaccurate error message was displayed to users logging into the AtomSphere platform when all accounts to which they had access were expired. With this fix, the error message accurately states that their account expired and is inaccessible. (INT-1372)

    XML profiles

    Features:
    • When generating XML profiles through an XSD or WSDL import, users are now presented with a warning message if they reach the limit on the number of nodes, recursion levels, or types that can be generated within a profile. (INT-1123)

      For more information about limitations when generating XML profiles, see the topic Importing an XML profile from an XSD file.

    • When users open a newly generated XML profile component that was previously truncated during import from an XSD file, a message is displayed to remind users that the profile is truncated. (INT-1167)

    Fix:
    • An enhancement was introduced in the November 2019 release which truncated imported XML profiles if they contained more than 3,300 complex types (INT-1166). With this fix, API components that use truncated XML profiles are updated to handle such profiles properly. (INT-1368)

    AtomSphere API and Partner API


    EDIFACT Connector Record object

    Feature:
    • The EDIFACT Connector Record object is extended to support outbound validation of EDIFACT documents. (B2B-813)

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

    HL7 Connector Record object

    Feature:
    • The HL7 Connector Record object is extended to support outbound validation of HL7 documents. (B2B-844)

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

      Note: Support in Boomi Integration for outbound validation of HL7 documents (B2B-150) is deferred to the February 2020 release.

    Installer Token object

    Feature:
    • The Installer Token object is extended to support the creation of API Management API Gateways. (APIM-557)

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

    Trading Partner object

    Feature:
    • The Trading Partner object is extended to support outbound validation of EDIFACT documents (B2B-695) and HL7 documents (B2B-697).

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

      Note: Support in Boomi Integration for outbound validation of HL7 documents (B2B-150) is deferred to the February 2020 release.

    Connectivity

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

    AS2 Client connector

    Feature:

    • Basic authentication for AS2 client connections is now supported. The implementation required a companion update to the platform. (B2B-751)

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

    AS2 Shared Server connector

    Fixes:

    • With this release, B2B-619 from the November release is effectively rolled back by virtue of updates to the Atom, EDI trading partners, and the AS2 Shared Server connector. (B2B-850)

    • AS2 listeners reported a connection failure error in the Listeners panel in Atom Management in some cases during the restart of a multi-node Atom Cloud. This error was misleading because the AS2 listener was already successfully connected to a node and operating. With this fix, a connection failure error is not reported when an AS2 listener cannot connect to to an individual node. Instead, a warning is logged. (B2B-827)

    Box connector

    Fix:
    • When using the Create and Upsert operations, a file containing no data (zero KB) was occasionally sent to the service in a process, resulting in the operation failing. With this fix, the correct and expected file size is sent and the operations succeed. (CON-551)

    Disk connector

    Feature:

    • The Disk v2 connector, formerly a Tech Preview, is Generally Available for production use with this release. If you are using the legacy Disk connector, you can continue to do so. However, you are encouraged to take advantage of the new functionality provided by the Disk v2 connector. (CON-602)

    FTP (Tech Preview) connector

    This connector was released off cycle into production before the January 2020 release. (BOOMI-14660). To learn more about this connector, see the topic FTP (Tech Preview) connector.

    LDAP connector

    Features:

    • When using the LDAP Import Wizard for the Get operation, you can use the Custom Attributes field to enter additional attributes you want to add to the selected Object Type. This provides you the flexibility to include additional fields supported by your LDAP entries, but not part of the selected Object Type, in operation profiles and responses. (BOOMI-40122)

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

    • A new LDAP Query operation document property is available, enabling you to dynamically set the search context. The new document property is LDAP - Search Context. (BOOMI-40117)

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

    • A new Execution operation with the Object Type of Rename entry is available, enabling you to rename an entry in the data directory by changing its Distinguished Name (DN). By changing the DN, you can move the entry to a new location. (BOOMI-36341)

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

    NetSuite connector

    Feature:

    • Two sets of Query filter operators are available (Any Of [ID], None Of [ID]) and (Any Of [Value], None Of [Value]) to account for Multi-select search fields where either the name or internal ID of the object is the same as or contains another object's name. With this release, you can refine your queries using these filter operators to return the expected results. (CON-6)

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

    SAP connector

    Feature:

    • The connector's error messaging is improved. (CON-194)

    Fix:
    • When you reopened a connection, Connection Type defaulted to Application Server Host. This occurred even when Connection Type was set to Message Server Host. If you saved the connection without changing Connection Type back to Message Server Host, you could overwrite your settings because the configurable fields changed with the Connection Type. With this fix, Connection Type only defaults to Application Server Host for new connections. (CON-58)

    Shopify connector

    Features:

    • The connector is updated to be compliant with and support the following object changes in Shopify’s REST Admin API:

      • Fulfillment — You can use the Fulfillment object in an operation to create, get, and update an order’s fulfillments. Apps must specify a location_id when creating fulfillments.

      • Refund — You can use the Refund object in an operation to calculate, create, and get a refund. (BOOMI-40266)

    • The connector gracefully recovers from and avoids returning 429 Too Many Requests errors by efficiently managing the number of requests made to the service. (CON-462)

    Web Services Server connector

    Fix:
    • The OData filter did not support null comparisons. With this fix, the OData filter option can compare null values on OData entities. For example, $filter=firstName eq null is a valid filter with this fix. (APIM-412)

    Zuora REST connector

    Feature:

    • The request profile for the CreateAndRetrieveExport object has a new header parameter, X-Zuora-WSDL-Version, that can be used to ensure that the API version you are connecting to and the WSDL version are the same. (BOOMI-40438)

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

    Connectivity development

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

    Connector SDK

    Features:

    Fixes:

    • Custom connector operations displayed “Request Profile Unstructured” when you configured a Get, Listen, or Query operation. With this fix, setting supportsBrowse to true in the descriptor has no effect on the user interface for Get, Listen, and Query operations. (CON-423)

    • When you configured a custom connector Listen operation, you could select the Return Application Error Responses option even though it had no effect. With this fix, the checkbox for that option is removed for custom connector Listen operations. (CON-512)

    Connector packaging

    Feature:

    • When packaging a connector in preparation to version and release it to Boomi for approval, the connector archive file maximum size limit is increased from 10 MB to 20 MB. (CON-646)

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

    Master Data Hub


    Reference data onboarding

    Feature:

    • Mastering reference data — for example, geographical locations — in domains separate from the domains in which you master “nouns” of your business, can help ensure references from master data to reference data remain consistent across master data domains and across the source systems that contribute to individual master data domains.

      To identify a domain as a reference data domain, you can designate a default source for that domain. Then, when an entity is contributed to a referencing master data domain from a source not attached to the reference data domain, an attempt is made to match the entity ID in the referencing field to an entity ID linking a golden record in the reference data domain to the default source. If the attempt is successful, the reference is resolved for the contributing source. (HUB-401)

    Data stewardship

    Features:

    • A new option is available in the Resolve Matching Issues wizard for resolving a quarantine entry for an entity that is a potential duplicate of an existing golden record. If you want to link a matching golden record to the entity rather than to the entity to which it is currently linked, select the ID field from the entity to merge into the golden record. (HUB-417)

      To learn more about resolving quarantine entries related to matching issues, see the topic Quarantines.

    • Quarantine entries now load more quickly in the Quarantine page as a result of

      • technical improvements to the Hub back-end (HUB-584)

      • changes to the purging policy for quarantine entries. Resolved quarantine entries are now purged 14 days after their resolution except where superseded. Superseded quarantine entries are now purged seven days after their resolution. (HUB-605)

    Fixes:

    • An error occurred during the processing of requests to unlink an end-dated golden record from a source. Such requests occurred because the option to make an unlink request was erroneously available in the golden record detail view for end-dated golden records. With this fix, the option to unlink a golden record from a source is available only for active golden records. (HUB-586)

    • When multiple golden records had the same updated date, the same golden record was included twice in a query result set in certain cases. With this fix, no golden record is included more than once in a result set.

      This fix required a re-release of the Repository to Hub clouds. (HUB-633)

    Governance

    Fix:

    • An error occurred during the loading of the Outbound Activity page for an account with more than approximately 100,000 golden records and no previously delivered source record update requests. With this fix, the Outbound Activity page loads properly under the same circumstances. (HUB-601)

    Transactional workflow

    Feature:

    • As a means of improving the consistency of data flowing from Hub to source systems, this release implements a fundamental change in the propagation of source record update requests:

      • Where a source’s channel is configured to propagate entities containing all fields, multiple pending requests for a given entity, regardless of the batch in which they are propagated, are combined into a single request reflecting the current version of the associated golden record.

      • Where a source’s channel is configured to propagate entities containing only updated fields, when there are multiple pending requests for a given entity, differences are merged to reflect the current version of the associated golden record. (HUB-534)

    Fixes:

    • Quarantine entries with either of these causes — Unknown Reference Value or Reference Matching Error — were not automatically resolved when the referenced golden record was created. With this fix, resolution occurs as expected under the same circumstances. The resolution type is Newer Version Incorporated. (HUB-451)

    • An entity in an incoming batch was quarantined with an Other Incorporation Error if the entity contained a reference to a field in an undeployed model. With this fix, such an entity is quarantined with the cause Unknown Reference Value. (HUB-574)

    B2B/EDI Management


    AS2 communication

    Feature:

    EDI document handling in multi-node Atom Clouds

    Fix:

    • With this release, B2B-619 from the November release is effectively rolled back by virtue of updates to the Atom, EDI trading partners, and the AS2 Shared Server connector. (B2B-850)

    EDIFACT document handling

    Feature:

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

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

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

    Fixes:

    • Data was neither processed nor available for viewing and downloading if the source data contained UNA as a substring. With this fix, source data containing UNA as a substring is properly handled. (B2B-620)

    • The Controlling Agency (UNH02:4) erroneously defaulted to UN in output unless it was set as a message-level document property. With this fix, Controlling Agency can be set as a document property in the Set Properties shape. (B2B-725)

    HL7 document handling

    Note: These features are deferred to the February 2020 release:
    • There is a new option to configure a trading partner for outbound validation of documents at the interchange level. 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)

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

    Trading partner settings extensions

    Fixes:

    • It was not possible to select application/octet-stream as a trading partner’s Content Type extension value for AS2 communication. With this fix, application/octet-stream is selectable. (B2B-625)

    • In the environment Extensions dialog’s Partner Settings tab, while Component Type was set to Trading Partner, the Trading Partner components available for selection in the Component Name list were not listed in alphabetical order. With this fix, the component names are listed in alphabetical order. (B2B-636)

    • It was not possible to select ZZ as an EDIFACT trading partner’s Qualifier (UNB02:7/UNB03:7) extension value. With this fix, ZZ is selectable. (B2B-657)

    API Management


    Applications

    Fix:

    • Deleting an Application did not delete the attached subscriptions. With this fix, deleting an application also deletes the attached subscriptions. (APIM-664)

    Authentication Brokers and API Gateways

    Feature:

    • You can toggle between enabled and deleted API Gateways on the Configure Server > Gateways page. (APIM-631)

      To learn more about this feature, see the topic API Gateways.

    Fix:

    • Adding or removing plans on deployed APIs that are not attached to an API Gateway caused an error. With this fix, plans can be added to, modified, and removed from deployed APIs that are not attached to an API Gateway without error. (APIM-956)
      Note: This fix required the re-release of the AtomSphere platform.

    Known issue:

    • A process deployed to an environment that is attached to an API Gateway can run longer than the API Gateway is available. With this release, the API Gateway timeout value is increased from 60 seconds to 120 seconds. To take advantage of this change, you must detach and then reattach the environment to the API Gateway. (APIM-839)

    Developer Portal

    Features:

    • The API Catalog details page displays the information provided on the Documentation tab of an API component on the Overview tab. (APIM-163)

      To learn more about this feature, see the topic API Catalog page.

    • You can enable or disable an application on the Applications page by clicking the value in the status column and selecting Enabled or Disabled or by clicking on the application name in the table and selecting the correct Application status in the settings. (APIM-90, APIM-91)

      To learn more about this feature, see the topics Applications and Developer Portal Applications page.

    Fix:

    • Deployed APIs that are in a status of "Requires Configuration" appeared on the Developer Portal even though users could not actually call the API through an application. With this fix, deployed APIs that require configuration do not appear on the Developer Portal until all errors are corrected and the status reads "Sent to the Gateway." (APIM-377)

    Known issue:

    • Applications on the Developer Portal may disappear after updating to a new version of the API Gateway. If this happens, refresh the page on which your Developer Portal is displayed to clear the cache. (APIM-655)

    Boomi Flow

    The following information identifies the new features and fixes in Boomi Flow Core releases 1.136.0, 1.137.0, 1.137.1, 1.138.0, 1.139.0, 1.140.0, 1.141.0, System Flows 1.46.0, Tooling 2.14.0, and User Interface 3.12.0.

    Core

    Features:

    • “Literal” values can now be added through the API, by applying the "elementType": "LITERAL" JSON attribute during API value creation. This feature is currently only available through the API, but a user interface for literal value creation will follow in a future release. (CORE-5488)

    • Loading performance for map elements in flows at runtime has been greatly improved so that map elements load faster within Boomi Flow. (CORE-4995)

    • New /api/draw/1/dependencies/{id} endpoint has been added to the API. This will list the entire dependency tree for any element in Boomi Flow. (CORE-5397)

    • Runtime user authorization is now performed more frequently within the system; authorization is now checked at 15 minute intervals. (CORE-5546)

    • Syntax and language-level errors generated from macros now provide details of the line and column numbers that are causing the error. (CORE-5485)

    • The Notifications menu now includes details of Boomi Flow Core releases. Click the release notification item in the menu to view details of what is included in the release. Notifications can be marked as read/unread. A GET request to the /api/notifications/1/me?includeRead={true/false} endpoint also allows read/unread notifications to be loaded using the API. (CORE-5332)

    • The State API has been extended with the addition of new properties to reflect subflows functionality in Boomi Flow:
      • mapElementDeveloperName

      • precommitStateEntry

      • runningUserId

      • values

      These properties are located in the "Frames" list in the API. (CORE-5389)

    • Values can now be set to clear after navigation options have been selected in flows. This is achieved through the API, by specifying the navigationItems value(s) to clear in a "valuesToReset": [{"id":"","resetType":"Clear"}] JSON attribute in a POST request to the /api/draw/1/flow/{flow}/{editingToken}/element/navigation endpoint. This feature is currently only available through the API, but a user interface for value clearing will follow in a future release. (CORE-5401)

    Fixes:

    • The Start map element was not being displayed in certain scenarios. (CORE-5508)

      With this fix, a manual intervention is required:
      1. Using the API tool, load your flow using the /api/draw/1/flow endpoint, and make a note of the startMapElementId property in the Response pane.

      2. Load the Start map element using the startMapElementId previously noted in the previous step and the /api/draw/1/flow/(flowId)/(flowId)/element/map/(startMapElementId) endpoint.

      3. Copy the response into the Request pane, and perform a POST request to /api/draw/1/flow/(flowId)/(flowId)/element/map.

      4. Close and reopen your flow, and the Start map element should be displayed normally.

    • API Tool filtering on "Literal" value references was not working correctly, for example performing a GET request on the API endpoint "/api/draw/1/element/value/reference?elementType=LITERAL" was returning all values. With this fix, "Literal" values can be filtered correctly using the API Tool. (CORE-5549)

    • Configuration values were not being passed through to services using the v2 External Service API. With this fix, configuration values are passed through to services correctly. (CORE-5439)

    • Customers using a custom Boomi Flow Service or a Boomi Flow Service in Boomi Integration may have experienced issues of the following nature when using types:
      • Types were not being not found at runtime when referencing a type by name; when running a flow that referenced a type by name rather than by ID, the error “Your Flow does not contain a Type with the name X” would be displayed. This issue is resolved. (CORE-5528)

      • Type properties were not being correctly deleted after a service was updated. This issue is resolved. (CORE-5517, CORE-5530)

    • Flow builders were previously unable to update services that used multiple type bindings, such as the Master Data Hub service. With this fix, services that use multiple type bindings can be updated. (CORE-5338)

    • Identity services were sometimes not being imported when snapshotting. With this fix, identity services are imported correctly. (CORE-5508)

    • Installing a service with a large number of types or particularly complex types — Salesforce, for example — was causing the system to time out when selecting Save Service in the tooling. With this fix, the system no longer times out in this scenario. (CORE-5368)

    • Intermittent error message "The state record contains data inconsistencies" was displayed when a user switched between multiple regions in the same state. With this fix, users can now switch between multiple regions in the same state without error. (CORE-5564)

    • Message actions with a ContentObject or ContentList input were not filtering values correctly. With this fix, the correct input type can now be filtered. (CORE-3336)

    • Navigation elements were previously being removed from flows in certain scenarios. With this fix, navigation elements are no longer being removed. (CORE-5516)

    • Object data that was not correctly parsed would result in an error message "Data at the root level is invalid. Line 1, position 1" that did not help the user. With this fix, the error message is now in the format "The provided object data couldn't be parsed correctly. Please contact your support team if this continues. ID: 67877e3d-b470-49d8-b90b-6944adb66a90 Map Element: Edit employee record" to better inform a user of the error and resolution. (CORE-5174)

    • Offset token pagination is now supported by the External Service API. Previously, pagination was only supported using numeric offset and limit parameters, but with this fix, pagination can use an offset token (a string). (CORE-5480)

    • Outcomes from a Subflow map element using value passing could not be saved. With this fix, outcomes can be saved. (CORE-5524)

    • Performance of the endpoint that lists players was sometimes too slow. With this fix, the response when listing players using either the tooling or the API endpoint is improved. (CORE-5474)

    • Performance of the system was sub-optimal when deleting services with many types in any region other than the master US region. With this fix, performance in this scenario is optimized. (CORE-5478)

    • Properties of values that used a system type were not being displayed in the value reference picker. With this fix, these properties are correctly displayed. (CORE-5501)

    • Swimlane authorization was not being triggered for non-ui map elements, such as the Load, Save, Delete, Decision and Operator map elements. With this fix, swimlane authorization now works correctly for all affected map elements. (CORE-5259)

    • Types with multiple bindings were displaying the incorrect binding selection at build time. With this fix, the correctly selected binding is shown. (CORE-5518)

    • User details for the $User system value were not populating correctly. With this fix, user details are correctly populated in the $User system value. (CORE-5576)

    System Flows

    Feature:

    • The Atom Type drop-down menu displayed when installing a new Boomi Flow Integration Service now includes all the current Boomi Atom Cloud hostnames. (FLOW-609)

    Tooling

    Features:

    • The Select Value form (commonly referred to as the “value picker”) that is used to select and create values across Boomi Flow is greatly enhanced to make working with multiple values much easier for flow builders. These enhancements include the ability to filter the values displayed by type, content type, and access type, and the ability to view the five most recently used values. These enhancements can be seen when selecting values via the rich text editor, selecting values when creating basic scalar page conditions, and when configuring a subflow map element, but will eventually be added to all related areas in the tooling. (FLOW-472, FLOW-486, FLOW-514, FLOW-515)

    • The ability to clone entire page layouts is added to the Page Layout Editor. Flow builders can now clone a page layout by clicking the new Copy button in the right-hand navigation bar; this does not clone the page dependencies (such as values for example), but only the page layout reference. This feature means flow builders can create duplicate page layouts and then modify them as needed. (FLOW-624)

    • The ability to clone page layout containers and their nested elements is added to the Page Layout Editor. Flow builders can now clone containers on a page layout by clicking the new Copy button in the container options shown when editing a container. This will create a duplicate of the container below the original. This feature means that flow builders can reuse containers in a page layout, enabling page layouts to be built more efficiently. (FLOW-533)

    • Values can now be passed between master flows and subflows when using subflows functionality. Note that the subflows feature is not currently in production and is only available as a Tech Preview in the UAT environment. (FLOW-617)

    • When installing a flow from the Flow Library or importing a flow into a tenant, users are now warned if the flow contains any shared elements which will be overwritten. A list of the affected elements is displayed in the warning dialog, informing the user of the relevant element name, type, and ID. (FLOW-603)

    • When importing a flow into a tenant, the name of the imported flow is now displayed in the success notification. (FLOW-646)

    Fixes:

    • Some error messages were being displayed inside quotation marks. With this fix, the quotation marks are removed. (FLOW-418)

    • The Import and Export tools were displaying an error in some versions of Microsoft Internet Explorer. With this fix, the error is no longer displayed in this browser. (FLOW-598)

    • The Insert Image and Insert Value buttons were not available in the content editor when editing a Content kind value property. With this fix, these options are correctly enabled in the content editor. (FLOW-427)

    • Unmasked text was being displayed in the Select Value form when a property of type contentEncrypted was used. With this fix, the text is correctly masked as expected. (FLOW-429)

    User Interface

    Fixes:

    • Editable tables were no longer editable by a user when viewed on a screen width below 768 pixels in size. With this fix, editable tables correctly retain edit functionality even when the screen width is reduced below 768 pixels. (FLOW-395)

    • Error messages were not being displayed when some service calls were not completed. With this fix, an error message is displayed to inform the flow builder if a service failure is encountered. (FLOW-477)

    • Image page component size attributes assigned by a flow builder were not being applied when the flow was displayed within a browser. With this fix, the dimensions assigned to an image page component are applied as expected. (FLOW-438)

    • Input component hint values were causing a rendering error when integers were assigned to the hint value rather than a text string. With this fix, numeric values can be used for hint values as expected. (FLOW-702)

    • Pagination limit attributes were not correctly applied to table page components when retrieving data from lists and services. With this fix, the value entered for a paginationSize attribute is correctly used to define the pagination items limit for the page component. (FLOW-402)

    • Removing rows from a table after a table column was used to sort the table was causing an error to be displayed. With this fix, the table correctly displays the message that is defined for the table page component in the noResults attribute. (FLOW-608)

    • Rendering errors “Target container is not a DOM element.” or “Minified React error #200” were caused by components containers not being correctly rendered in the browser. With this fix, rendering errors are no longer caused when a container is not found while the page is rendering. (FLOW-666)

    • When adding a message action map element to a flow without any services installed, the services drop-down menu on the Message Action for page was not being displayed correctly. With this fix, the drop-down menu displays correctly. (FLOW-426)