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

Removing exclusionary terminology

Words matter. In response to expanded conversations around institutional racism, we are committed to using language that includes everyone. Our teams are making significant shifts away from terms that have been 'common industry' terms, because we now recognize them as offensive, non-inclusive, or with historically racist implications.

Read more about our efforts in our Removing exclusionary terminology from Boomi Community article.

Boomi Community

Fix:

  • An invalid SSO request message resulted when using Boomi AtomSphere credentials to sign into the Boomi Community site from https://community.boomi.com/s/login/. With this fix, SSO sign in works as expected. (ADSEC-986)

Landing page

Feature:

  • In Settings > User Information > Preferences, you can choose your landing page, which is the page that loads when you sign in to the AtomSphere platform. You can choose the Home page or any menu page within Boomi IntegrationMaster Data Hub, or API Management. If you sign in through a bookmarked page, you will continue to land on your bookmarked page. (UNI-574)

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

Atoms, Molecules, and Atom Clouds

Atom Cloud management

Feature:

  • The Enable Download of Execution Artifacts and Atom Worker Logs property for an Atom Cloud attachment is set to true by default. (RUN-1266)

    To learn more about this feature, see the topic Attachment Quotas tab.

Atom management

Feature:

  • The Clean Up Custom Script Engine Data on Completion property, if set to true (the default), causes the immediate cleanup of leftover data after custom script execution. (RUN-1066)

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

Docker installer

Fix:

  • Docker installers failed in Microsoft Azure when mounted to CIFS file systems due to unexpected changes in file permissions. With this fix, file permissions do not change. (RUN-1010)

Boomi Integration

API Service components

Feature:

  • When adding REST endpoints to an API Service component, the Resource Path is no longer required. If you leave the Resource Path empty, the resource path is the default operation from the Base API Path. The Base API Path is set in the Service Configuration section on the General tab of the API Service component. (APIM-2293)

    There is a known issue with this feature: If you do not specify a Resource Path/Object is appended to the Endpoint Path for the REST endpoint within the Configure APIs and Applications > Deployed APIs page in API Management. However, the endpoint does not actually include the appended /Object. This issue will be resolved in our next release.

    Note: This known issue is also covered in the API Management section of these release notes.

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

Audit logs

Fix:

  • An audit log entry is enhanced for clarity. (PS-709)

Build page

Feature:

  • Changes are introduced to the process canvas to better identify connected and disconnected shapes. (DS-3534)

    • A disconnected shape is identified by a navy blue square with a white minus sign inside.

    • A connected shape is identified by a teal circle with a right-facing arrow inside.

Environment extensions

Feature:

  • The environment Extensions dialog’s Connection Settings and Data Maps tabs, and the Test dialog's Connection Settings tab, feature improved design and navigation. (CON-1126)

Fix:

  • The message “There are no extensible connections” erroneously appeared in the Connection Settings tabs in both the environment Extensions dialog and the Test dialog while the tabs loaded, even if extensions were indeed present. With this fix, the message displays only when there are no extensible settings. (INT-2828)

Integration packs

Feature:

  • The workflow for scheduling integration pack releases on the Manage > Integration Packs page is enhanced to provide more granular control when selecting specific versions of packaged components for release. The new workflow also allows rollback of versions of packaged components in an integration pack. (INT-2691)

    To learn more about this feature, see the topics Integration pack development and Releasing an integration pack.

JSON profiles

Features:

  • Management of data element qualifiers is simplified:

    • Once a qualifier is added to an element, the qualifier is active until it is removed.

      Note: In previously existing profiles, inactive qualifiers may be present in the profile component XML. If present, they are removed when the element definition is subsequently edited and the profile is saved.
    • Clicking a qualifier value in the Qualifiers table opens the Edit Qualifier dialog, in which you can edit the qualifier value and description.

  • Additionally, the Add Custom Qualifier dialog is retitled “Add Qualifier”, and the dialog entry point in the Qualifiers table’s Actions menu is changed from Add Custom Qualifier to Add. (B2B-1213)

    To learn more about this feature, see the topics Adding qualifiers to a JSON profile data element and JSON profile’s Data Elements tab.

  • The JSON Profile component configuration dialog is enhanced with a new Getting Started screen to help you get started with importing or manually creating a profile. (INT-2812)

  • JSON profiles generated from JSON schema files either via API Service components or when browsing connector operations are automatically configured with the following settings:

    • Min Length and Max Length are automatically populated for Character elements if specified in the JSON schema file. Note that the Field Length Validation field remains false for backward compatibility.

    • A new Required option is automatically selected if an element is designated as required in the JSON schema file. This is also set for array elements with a minOccurs greater than 0. If Required is selected, the element is always output when mapping, even if there is no value or the element is not even mapped.

    • A new Comments field for each element is also automatically populated from the JSON schema Description attribute, if specified. Comments can also be entered manually.

  • (INT-2370)

    To learn more about this feature, see the topic JSON profile’s Data Elements tab.

Fix:

  • It was erroneously possible to add duplicate qualifier values to a data element. With this fix, an error message is displayed in the Add Qualifier dialog or the Edit Qualifier dialog upon entry of a duplicate qualifier value. (B2B-1196)

Process reporting

Fix:

  • In the Process State dialog, the Archive path for a Trading Partner Start shape was erroneously identified as an Acknowledgments path. With this fix, the Archive path is correctly identified. (B2B-1087)

RSS feeds

Fix:

  • Previously, customers reported up to an hour delay in receiving RSS Alerts Only feeds. With this fix, the frequency in which subscribers receive RSS Alerts Only alerts is increased to every 15 minutes. (PS-1287)

    To learn more about this feature, see the topics Email alert management and Test connection licensing.

Shared Web Server panel

Fix:

  • Upon switching API Type from Advanced to Basic and then to Intermediate, the CORS configuration panel incorrectly displayed. With this fix, the CORS configuration panel does not display when API Type is set to Intermediate under any circumstances. (APIM-2137)

Web Services Server listener processes

Fix:

  • When a request sent to a Web Services Server listener process timed out, an error message was displayed, but the Shared Web Server logs showed a successful execution status. With this fix, you can specify a timeout value, in milliseconds, in the X-Max-Wait request header. (APIM-2026)

    • If the process successfully services a request, a successful status (HTTP code 200) is returned to the client, and the X-Execution-Id response header is omitted.

    • If a request times out, an HTTP code 202 is returned, and the X-Execution-Id and X-Execution-Status-Link response headers are included; the X-Execution-Status-Link value is the URL from which the execution status can be retrieved.

  • Note: This fix has companion changes covered in the Connectivity section of these release notes.

XML profiles

Feature:

  • Management of element and attribute qualifiers is simplified:

    • Once a qualifier is added to an element or attribute, the qualifier is active until it is removed.

      Note: In previously existing profiles, inactive qualifiers may be present in the profile component XML. If present, they are removed when the element or attribute definition is subsequently edited and the profile is saved.
    • Clicking a qualifier value in the Qualifiers table opens the Edit Qualifier dialog, in which you can edit the qualifier value and description.

  • Additionally, the Add Custom Qualifier dialog is retitled “Add Qualifier”, and the dialog entry point in the Qualifiers table’s Actions menu is changed from Add Custom Qualifier to Add. (B2B-1213)

    To learn more about this feature, see the topics Adding qualifiers to an XML profile element or attribute and XML profile’s Data Elements tab.

Fix:

  • It was erroneously possible to add duplicate qualifier values to an element or attribute. With this fix, an error message is displayed in the Add Qualifier dialog or the Edit Qualifier dialog upon entry of a duplicate qualifier value. (B2B-1196)

AtomSphere API and Partner API

Clear queue messages operation

Feature:

  • You can programmatically delete all messages in an Atom queue for a given Atom, Molecule, or Atom Cloud by means of a Clear queue messages operation. This action is similar to the Clear Messages action in the Queue Management panel of Atom Management in Boomi Integration. (RUN-766)

    To learn more about this feature, see the topic Clear queue messages operation.

Deployed Package object

Fix:

  • Unhelpful messaging appeared when a timeout error occurred due to excessive concurrent API requests. With this fix, performance is improved to allow for more concurrent requests and to reduce the risk of a timeout error. Messaging is also improved. (INT-2776)

Get queues list operation

Feature:

  • You can programmatically retrieve a list of message queues for a given Atom, Molecule, or Atom Cloud by means of a Get queue list operation. (RUN-763)

    To learn more about this feature, see the topic Get queues list operation.

Trading Partner Component object

Feature:

  • You can programmatically configure a trading partner so that Base64 encoding is applied to message headers and service content in outbound RosettaNet messages by setting the corresponding object’s contentTransferEncoding field in RosettaNetMessageOptions to base64 . (B2B-1189)

    Note: This feature has companion changes covered in the B2B/EDI Management section of these release notes.

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

Upgrade Java operation

Fix:

  • Previously, omitting the JavaUpgradeOptions and migrateCertificate fields from the request body resulted in an error. With this fix, JavaUpgradeOptions is optional, and in an XML and SOAP request body migrateCertificate is a child element of JavaUpgradeOptions, rather than an attribute as was previously the case. (RUN-1216)

Connectivity

AtomSphere API and AtomSphere Partner API connectors

Features:

  • The following objects and operations are added to those available for selection when browsing (Import Wizard):
    • Atom Disk Space object (RUN-981)

    • Atom Purge object (RUN-982)

    • Node Offboard object (RUN-983)

    • Download execution artifacts operation (RUN-1267)

    • Download Atom worker log operation (RUN-1268)

Google Sheets connector

Feature:

  • After using the Query operation's Import Wizard for the RecordData object and specifying the Spreadsheet ID and Sheet Title, the values were set and could not be changed without performing another import. With this feature, two new operation fields are available, Spreadsheet ID and Sheet Title, enabling you to override the values. Dynamic operation properties are also available as overrides. (CON-1997)

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

Fix:

  • Deleting a spreadsheet, even when providing the correct Spreadsheet ID, returned an error. This was due to the deprecation of certain endpoints by the service. With this fix, the Delete operation works as expected. (CON-1895)

Mail (IMAP) connector

Feature:

Microsoft Azure Cosmos DB connector

Feature:

  • The Query operation retrieves all available records in the database table, not just the first 100 records. (DBOETKZW-2168)

Fix:

  • When using the Import Wizard to browse, the Atom drop-down list does not appear. With this fix, the Atom list appears, as expected. (DBOETKZW-2168)

Microsoft Dynamics 365 for Customer Engagement connector

Fixes:

  • The Query operation was not successful because it could not appropriately process the JSON response from the service with text containing an unmatched combination of braces — an opening brace { without a closing brace } or a closing brace } without an opening brace {. With this fix, the response is processed and the operation is successful. (CON-2189)

  • When the Query operation was not successful because it could not appropriately process the response from the service, a misleading error message displayed, indicating that the link for the next page could not be retrieved. With this fix, an improved error message is displayed to aid in troubleshooting the operation. (CON-2192)

Microsoft Dynamics 365 for Finance and Operations connector

Fixes:

  • The Query operation was not successful because it could not appropriately process the JSON response from the service with text containing an unmatched combination of braces — an opening brace { without a closing brace } or a closing brace } without an opening brace {. With this fix, the response is processed and the operation is successful. (CON-2190)

  • When the Query operation was not successful because it could not appropriately process the response from the service, a misleading error message displayed, indicating that the link for the next page could not be retrieved. With this fix, an improved error message is displayed to aid in troubleshooting the operation. (CON-2193)

OData Client connector

Fixes:

  • The Query operation (V 4.0) was not successful because it could not appropriately process the JSON response from the service with text containing an unmatched combination of braces — an opening brace { without a closing brace } or a closing brace } without an opening brace {. With this fix, the response is processed and the operation is successful. (CON-2110)

  • When the Query operation (V 4.0) was not successful because it could not appropriately process the response from the service, a misleading error message displayed, indicating that the link for the next page could not be retrieved. With this fix, an improved error message is displayed to aid in troubleshooting the operation. (CON-2076)

Salesforce Platform Events connector

Feature:

  • Listen operations are updated to support receiving near-real-time change events to a Salesforce record type or object by subscribing to Change Data Capture channels. (CON-2159)

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

SAP JCo V2 connector

Features:

  • Support is added for multiple levels of TID management, including None (disable TID management), Minimum (current option), and Full (includes logging of IDocs sent from SAP).

  • If the Atom uses SAP JCo V3.1, support is added for the Listen operation deployed to the SAP Message Server. This allows the listener to connect to multiple SAP application servers concurrently for load balancing and availability.

  • Selected IDoc header fields are exposed as tracked fields for Process Reporting.

  • Newly imported IDoc profiles match the SAP IDoc sequence.

  • SAP SNC support is added for Listen operations receiving IDocs from SAP.

  • JCo trace-level settings are added to the connection, allowing dynamic changes using environment extensions.

    (CON-2133)

    To learn more about these features, see the topic SAP JCo V2 connector.

Snowflake connector

Feature:

  • The Snowflake connector enables high-performance bulk load and extract operations into and from a Snowflake instance utilizing the Get, Create, Update, Query, Delete, Execute, SnowSQL, and Bulk Load/Unload operations. Issue SnowSQL commands to accomplish Merge and Upsert operations, and process unstructured data using VARIANT column support offered by Snowflake. (CON-2133)

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

Web Services Server connector

Fix:

  • When a request sent to a Web Services Server listener process timed out, an error message was displayed, but the Shared Web Server logs showed a successful execution status. With this fix, you can specify a timeout value, in milliseconds, in the X-Max-Wait request header. (APIM-2026)

    • If the process successfully services a request, a successful status (HTTP code 200) is returned to the client, and the X-Execution-Id response header is omitted.

    • If a request times out, an HTTP code 202 is returned, and the X-Execution-Id and X-Execution-Status-Link response headers are included; the X-Execution-Status-Link value is the URL from which the execution status can be retrieved.

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

Connectivity development

Connector SDK

Feature:

  • With this release, the Connector SDK is updated to version 2.8.2. For information about the updates in this release, see the SDK changelog. (CON-2236)

Custom connector development

Fixes:

  • Listen operations defined in the connector descriptor file with or without overrideable fields resulted in the Dynamic Operation Properties tab on the Connector shape not displaying for all other operations having overrideable fields. With this fix, the Dynamic Operation Properties tab displays as expected for all operations having overrideable fields. (CON-2121)

  • When adding dynamic operation properties to the Connector shape, the Parameter Value dialog displayed the field in the Input drop-down list only if the field label (@label) was defined in the connector descriptor file. If not defined, null appeared rather than the field ID (@id) from the descriptor. With this fix, the field ID appears, as expected. (CON-2127)

  • After changing the Action for a connector in the Start shape, the Dynamic Operation Properties tab still appeared even when the Operation cleared. With this fix, the Dynamic Operation Properties tab disappears, as expected. (CON-2131)

Master Data Hub

Quarantine entry resolution

Fixes:

  • If the id field in an entity quarantined as a potential duplicate was merged by request into a matching golden record, the Sources tab in the golden record detail view continued to show the time at which the original link to the source was established. With this fix, the time at which the new link was established is shown. (HUB-1076)

  • If the id field in an entity quarantined as a potential duplicate was merged by request into a matching golden record, the Reject Contributed Entity request propagated to the contributing source on its channel erroneously specified the ID of the newly linked source entity. With this fix, the Reject Contributed Entity request specifies the ID of the previously linked entity. (HUB-1077)

  • If fields in an entity quarantined as a potential duplicate were merged by request into a matching golden record, a source record update request was not propagated to the contributing source on its channel. With this fix, an update request is propagated to the contributing source. If the id field in the entity is one of the merged fields, the update request specifies the ID of the newly linked entity. If the id field in the entity is not one of the merged fields, the update request specifies the ID of the existing linked entity. (HUB-1097)

Source attachment and configuration

Fix:

  • An error occurred in some cases when attempting to remove a source from a domain with a relatively large number of references. With this fix, source removal should complete without error. (HUB-750)

B2B/EDI Management

EDI profiles

Features:

  • Management of data element qualifiers is simplified:

    • Qualifiers can be imported from an EDI standard to an element, provided qualifier values are defined for the element in the standard. Importable qualifiers were previously known as Standard qualifiers. To import qualifier values to an element, in the Qualifiers table's Actions menu, select Import from Standard.

    • What were previously known as Custom qualifiers can be added to an element as before. The Add Custom Qualifier dialog is retitled “Add Qualifier”, and the dialog entry point in the Qualifiers table’s Actions menu is changed from Add Custom Qualifier to Add.

    • Once a qualifier is imported or added to an element, the qualifier is active until it is removed.

      Note: In previously existing profiles, inactive qualifiers may be present in the profile component XML. If present, they are removed when the element definition is subsequently edited and the profile is saved.
    • Clicking a qualifier value in the Qualifiers table opens the Edit Qualifier dialog, in which you can edit the qualifier value and description. (B2B-1213)

  • To learn more about this feature, see the topics Adding qualifiers to an EDI profile data element and EDI profile’s Data Elements tab, element details.

  • While support for standard data element qualifier values continues to be limited to the X12 standard, with this release, all X12 versions are supported. (B2B-1055)

Fix:

  • It was erroneously possible to add duplicate qualifier values to a data element. With this fix, an error message is displayed in the Add Qualifier dialog or the Edit Qualifier dialog upon entry of a duplicate qualifier value. (B2B-1196)

RosettaNet document handling

Feature:

  • Support is added for configuring a RosettaNet trading partner so that Base64 encoding is applied to message headers and service content in outbound messages. To enable Base64 encoding, set Content Transfer Encoding to Base64 in the Message Options section of the ROSETTANET Standard tab. The default setting, Binary, corresponds to the legacy behavior. (B2B-1188)

    Note: The RosettaNet EDI connector is updated to support this feature. (B2B-1200)
    Note: This feature has companion changes covered in the AtomSphere API and Partner API section of these release notes.

    To learn more about this feature, see the topic Trading Partner ROSETTANET Standard tab.

API Management

Authentication Brokers and API Gateways

Feature:

  • On any API Gateway that uses a JWT authentication source, you can specify one or more Scopes parameters to define the actions that we can complete and resources that we can access through third parties on your behalf through an authorization server on your Developer Portal. By default, we add the scopes openid, email, and profile.

    You specify Scopes parameters on the Developer Portal Settings panel within an API Gateway on the Configure Server > Gateways page. (APIM-2063)

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

Fixes:

  • After the November release, APIs that were modified or deployed to an API Gateway on an Atom Cloud returned a 501 error message. With this fix, APIs that are deployed to an API Gateway on an Atom Cloud will not return an error message. (APIM-2580)

    If you modified or deployed an API to an API Gateway on an Atom Cloud after the November release, change the API configuration and revert the change to force the updated API to be sent to the API Gateway. For instance, change the URL to a custom one, save it, and then back to the original and save it. If you have a large number of APIs impacted, we recommend detaching the environment from the API Gateway and then reattaching it.

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

  • When a process being called through an API Gateway took longer than two minutes to complete, an automatic retry of the execution ran. Previously, this two minute value was configurable through a system property that was inadvertently removed as a part of November's release. To identify whether an automatic execution retry was run on your process, view the Process Reporting page within Boomi Integration and see if a new execution started exactly two minutes after the first. With this fix, the automatic retry is not started until ten minutes after the initial execution. (APIM-2585)

    Tip:We recommend designing your APIs in a way that downstream processing is not impacted with a retry, or duplicate transaction.

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

    Subsequently to the fix for APIM-2585, a second re-release of the AtomSphere platform modifies the original fix to remove the timeout value before a retry. (APIM-2602)

Deployed APIs

Fix:

  • The APIs by Gateway tab on the Configure APIs and Applications > Deployed APIs page erroneously displayed each Gateway name twice. With this fix, each Gateway name is displayed once, as expected. (APIM-1959)

Known issue:

  • If you do not specify a Resource Path for the REST endpoint in an API Service component within Boomi Integration/Object is appended to the Endpoint Path for the REST endpoint within the Configure APIs and Applications > Deployed APIs page. However, the endpoint does not actually include the appended /Object. This issue will be resolved in our next release.

    Note: This known issue is also covered in the Boomi Integration section of these release notes.

Developer Portal

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

Boomi Flow

The following information identifies the new features and fixes in Boomi Flow releases Core 2020-10-13.0930, 2020-10-15.1456, 2020-10-28.1109, 2020-11-03.1725, 2020-11-03.1534, 2020-11-04.1437, 2020-11-12.1028, System Flows 1.59.0, 1.60.0, Tooling 2.35.0, 2.35.1, 2.36.0, 2.37.0, 2.38.0, 2.39.0, Twilio Service 2.3.0, and User Interface 3.29.0, 3.30.0, 3.31.0, 3.32.0.

Note: The version reference format for Boomi Flow Core releases has changed — for example, from “1.173.0” to “2020-10-13.0930”.

Core

Features:
  • Flow states can be set to ‘expire’ after a set amount of inactivity, allowing greater control over inactive flow states. For example, you may wish a flow state to expire after x days of state inactivity. This is specified in a new Number of seconds of inactivity before the in-flight States should be deleted setting on the Flow Properties form. Once a state ‘expires’ due to this setting, any user who tries to join or progress through the flow will not be able to interact with the flow and will receive a message to inform them that the “The state with ID 12345 has now expired”. (FLOW-2163)

    To learn more about this feature, see the topic Flow states.

  • Internet Protocol version 6 (IPv6) addresses are supported when restricting tenant flow access by IP address on the Tenant Settings page. Previously, only IPv4 addresses were supported. (FLOW-1943)

  • Modifications support future Multi-cloud Runtime functionality. (FLOW-2388, FLOW-1286, FLOW-2588, FLOW-2589)

  • Modifications support future Organizations functionality. (FLOW-1534)

    Note: Due to these modifications, all new top-level tenant names will no longer end with the suffix ‘.manywho.com’. For example, if a new tenant is named ‘TenantA’, the tenant name will be ‘@TenantA’, when previously it would have been ‘@TenantA.manywho.com'.
  • Modifications support future tenant SAML SSO functionality. (FLOW-2430)

Fixes:

  • If a combobox page component was configured to save to a Boolean value as one of multiple data presentation columns on the page, the combobox would be pre-populated with the last value in the list that had the Boolean value set to ‘False’, even if the display column had been configured not to display. With this fix, the combobox is not pre-populated and selected if no default data has been defined for the value to which the combobox is saved. (FLOW-2347)

  • In some circumstances if a subtenant was renamed, the subtenant was no longer displayed on the Tenant Settings page for the parent tenant. With this fix, all subtenants belonging to a tenant are correctly displayed on the Tenant Settings page, regardless of whether a subtenant has been renamed. (FLOW-2137)

  • Subflow executions were not progressing correctly when using the timer service. With this fix, subflow executions progress as expected. (FLOW-2643)

  • Subtenants did not inherit the expiration date of a parent tenant using the expiresAt setting. With this fix, if a parent tenant has an expiration date set, all subtenants apply that expiration date. (FLOW-1521)

  • Users were prevented from progressing into a subflow that had been configured within a swimlane, with an error informing the user that the maximum number of uninterrupted executions has been reached. With this fix, no error message is displayed and users are able to progress into the subflow as expected. (FLOW-1938)

System Flows

Feature:
  • Information about the new default script behavior is provided when editing presentation components and step map elements. (FLOW-2651)

  • The New Flow page used when creating a flow is updated to align with new functionality, such as adding Historical Navigation or setting state inactivity expiration for a flow. (FLOW-2213)

Tooling

Features:
  • Flow states can be set to ‘expire’ after a set amount of inactivity, allowing greater control over inactive flow states. For example, you may wish a flow state to expire after x days of state inactivity. This is specified in a new Number of seconds of inactivity before the in-flight States should be deleted setting on the Flow Properties form. Once a state ‘expires’ due to this setting, any user who tries to join or progress through the flow will not be able to interact with the flow and will receive a message to inform them that the “The state with ID 12345 has now expired”. (FLOW-2163)

    To learn more about this feature, see the topic Flow states.

  • Modifications support future Multi-cloud Runtime functionality, such as the ability to deploy flows to a local runtime. (FLOW-2523, FLOW-2460, FLOW-2428, FLOW-2558, FLOW-2589, FLOW-1340)

  • Modifications support future Organizations functionality. (FLOW-2652, FLOW-2658)

  • Modifications support future tenant SAML SSO functionality. (FLOW-2430)

  • The Default Value field in the Create new Value form is enhanced to allow multi-line input when entering a default value for String and Encrypted values. (FLOW-1803)

  • The last selected user state for sidebar menus is stored so that users can choose to consistently keep sidebar menus expanded or collapsed. (FLOW-2187)

  • To improve form usability, the Comments about this value field moves to below the Default Value and Presentation sections of the Create new Value form. (FLOW-1802)

Fixes:
  • Blank page names could be used when creating new page layouts, by entering only multiple space characters into the Name field. With this fix, a new page cannot be saved with an invalid name. Page names cannot be blank, or contain leading, trailing, or multiple space characters. Names containing a single space character between words in the name are valid, such as 'Page Name' for example. (FLOW-1983)

  • Double-clicking a map element inside a swimlane opened the swimlane configuration panel. With this fix, double-clicking a map element inside a swimlane opens the configuration panel for the selected map element. (FLOW-2451)

  • Literal string ContentValues could be assigned to a complex ContentObject or ContentList type value using the /api/translate/1 translation endpoints, resulting in corruption of the value and related elements. With this fix, values assigned in this way using the translation endpoints are validated, and an error message is displayed to inform a user if the value cannot be assigned. (FLOW-2279)

  • Service invoker failures were not logged correctly. With this fix, service invoker failures are logged correctly. (FLOW-2395)

  • Tenants were not correctly listed when creating a new local runtime connection. With this fix, tenants are listed correctly when creating a new local runtime connection. (FLOW-2556)

  • Users were unable to reopen a tenant, and an error message was displayed if the api/translate/1/culture endpoint had been used to set a brand and variant variable for the default US-EN culture in the tenant. With this fix, tenants reopen as expected, even if these variables are defined. (FLOW-2380)

Twilio Service

Fix:
  • The Twilio service did not pass back responses into flows, resulting in flows not progressing correctly to any relevant outcomes. With this fix, responses are passed correctly by the service so that flows progress to any relevant outcome once the service response is received. (FLOW-2126)

User Interface

Feature:
  • A new disableScripting player option allows you to define input sanitization behaviour for any flows run using a player. Components such as the presentation component can allow flow users to enter HTML or JavaScript scripting into a flow; it is important to define whether your Organization wishes to allow unsanitized input within your flows, or whether any user input in a flow should be sanitized to comply with your internal security requirements. (FLOW-2018)

    For example, you may prefer to allow users to enter unsanitized input into a flow, in order to render HTML/JavaScript for improving the UX dynamics of any flows that you build.

    • The default player has the disableScripting option included, set to 'true' by default. This applies input sanitization and provides immediate security protection against scripting in any flow that uses the default player.

    • If the disableScripting option is not included in a player, the scripting behaviour will default to 'false', to allow scripting in custom players by default; input sanitization is not applied.

    • If you are using a custom player and wish to apply sanitization to user input in your flows, you will need to add the disableScripting option into your custom player and set this to 'true'. Any input in a flow run using the player will then be sanitized.

    To learn more about this feature, see the topic Applying input sanitization in a player.

  • The default flow loading spinner is updated in the default player. (FLOW-2562)

Fixes:
  • Ordering was reversed in a combobox page component after a user selected a value and reopened the list. With this fix, ordering is applied correctly, even after a value is selected. (FLOW-2267)

  • The Upload button in a file upload component was not displayed when used with a social feed in a flow, preventing flow users from uploading files to the social feed. With this fix, the file upload component functions correctly, allowing files to be uploaded to a social feed. (FLOW-2389)

  • When running subflows in Debug Step-Through mode, attempting to return to the parent flow instead looped back to the beginning of the subflow. With this fix, subflows run in Debug Step-Through mode correctly return to the parent flow. (FLOW-2548)