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


Welcome page

Feature:

  • A new welcome experience is released that contains information from all areas of the AtomSphere platform as well as links to additional information from other Boomi resources such as help content, Boomi Community, and training. (UNI-1, UNI-103, UNI-104, UNI-105)

    Seeing the new welcome page requires you to opt-in to Beta features by going to Setup > Beta Features > New build canvas and component icons and enabling the toggle. Then, click the AtomSphere logo to open the new welcome page. In future months, the new welcome page will become more robust and eventually will open by default.

    Note: The Welcome page is deferred from the March 2020 release and will be included in a future release.

Filtering

Feature:

  • To improve accessibility, filter icons are replaced across the platform with buttons labeled “Filter.” (INT-1420)

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 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 Community. For an updated list of Atom Cloud IP addresses, see the topic Hostnames and IP addresses for the Boomi Atom Clouds.

Connector SDK enablement

Feature:

  • To enable connector development, a change was made so that the Connector SDK can expose custom properties in an OAuth2Token response. With this feature, custom connectors can access these properties and interact with services that may require them. (CON-595)

Installers

Fix:

  • An error occurred while attempting to upgrade an Atom to Java 8 on a Windows system. With this fix, Atom upgrades to Java 8 work as expected for Windows users. (RUN-299)

Java security compatibility

Feature:

  • To maintain compatibility with Java 1.8.0_241 version upgrades, a new security compatibility property, jdk.security.allowNonCaAnchor, is introduced which preserves certificate functionality that may have otherwise been affected. (RUN-407)

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

    Note: Support for Java 1.8.0_241 version upgrades is deferred to the April 2020 release.

Java upgrades

Feature:

  • The Atom, Molecule, and Atom Cloud installers and updaters are modified to use Java 1.8.0_241. Boomi Atom Clouds are also modified to use Java 1.8.0_241.

    Java 1.8.0_241 upgrades limit the number of capture groups defined in Javascript custom scripts to 32767.

    When establishing a TLS connection, Java 1.8.0_241 requires that the TLS server certificate be an exact match of a trusted certificate on the client in order for it to be trusted. (RUN-302, RUN-310)

    Note: Boomi Atom Clouds are also modified to use Java 1.8.0_241.

    To learn more about this feature, see the topic Java upgrade FAQ.

    Note: Support for Java 1.8.0_241 version upgrades is deferred to the April 2020 release.

Startup properties

Feature:

  • To assist users in determining process limits, the following properties are displayed in the Startup Properties panel for Atoms, Molecules, and Atom Clouds running on Linux systems:

    • Max CPU Time

    • Max File Size

    • Max Data Size

    • Max Stack Size

    • Max Processes

    • Max File Locks

  • (RUN-42)

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

Boomi Integration


Packaged Component Deployment

Features:

  • The new Packaged Component Deployment workflow is introduced to Boomi Integration. This workflow leverages the former Package Manager feature in both design and function. Using packaged components, you can apply custom, consistent versioning to deployable components and processes, which provides greater traceability as they are deployed across multiple environments, published to process libraries, or added to integration packs. (INT-816, INT-1436)

    The new Packaged Component Deployment functionality is automatically enabled for newly created accounts as of the March 2020 release. Accounts that previously used the Package Manager deployment feature are automatically updated to use the new Packaged Component Deployment functionality.

  • From the Setup > Account Features page, account administrators can choose to enable the Packaged Component Deployment feature for those accounts that currently use Legacy deployments. Once enabled on the Account Features page, the Packaged Component Deployment feature replaces the Legacy workflow in Boomi Integration. Once enabled, the feature cannot be disabled.

    Upon enabling Packaged Component Deployment in Setup, administrators can choose to automatically update any custom roles defined in the Legacy account that currently use the Packaged Component Deployment privilege (formerly Process Deployment) to also include the Packaged Component Management privilege. (INT-278)
    Note: For accounts using Legacy Deployment that currently share custom roles with child accounts, any shared custom roles with the Packaged Component Deployment privilege are updated automatically to also include the Packaged Component Management privilege as part of this release. This update preserves the level of access for child account users assigned with deployment custom roles. Administrators may refer to audit logs to note any role changes that occur on the account.

    To learn more about enabling Packaged Component Deployment, see the topic Account features management. For more information about packaged components and converting your account, please see the How to Prepare for Integration Packaged Component Deployments Community article and the Preparing for Packaged Component Deployment free training course.

Account Dashboard

Fix:

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

Environment management

Feature:

  • To improve the method by which users select Environment Management options, the Roles with Access and Attachments field options are now presented as check boxes rather than drop-down lists. (ADSEC-143)

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

Object definition files

Fix:

  • In some cases, importing large connector object definition files negatively impacted platform performance. With this fix, a limit is imposed to prevent the importing of files larger than 20 MB. (INT-1405)

OData API endpoints

Feature:

  • Processes started with a Web Services Server connector in the Start shape now include inheader_ for OData endpoints that are set in the Dynamic Document Properties header settings and are not in a protected header group. These inheader_ prefixes will cause the prefix outheader_ on the result document. (APIM-12)

    Note: This feature has companion changes covered in the Connectivity section of these release notes.
    Note: This feature is deferred to the April 2020 release.

Process configuration for API Service components

Fix:

  • Dynamic Document Property Headers were being returned in the same case as the HTTP header request. This caused false null values being returned due to a case insensitivity when calling the inheader_ value. For example, calling inheader_Test was returning a null value because all headers were being generated as lowercase and sending the value as test rather than Test. With this fix, the Dynamic Document Property Header is matched to the HTTP header regardless of case, removing the false null values being returned. (APIM-873)

    Note: This fix has companion changes covered in the Connectivity section of these release notes.
    Note: This fix is deferred to the April 2020 release.

Process Reporting

Fix:

  • When an error message in Process Reporting contained #, exporting the process report to a CSV file produced output in which that message and all remaining messages were omitted. This defect was reported in Chrome and Firefox browser versions 71 or above. With this fix, the output CSV file contains all messages, as expected. (INT-556)

Shared Web Server configuration

Fix:

  • Within Atom Management’s Shared Web Server panel, selecting an API to which to allow a specific user access through the Use API Filtering option would not clear the filter when switching to a different user. Upon clearing the filter for the new user, the API that was selected for access was removed from the first user. With this fix, changing users does not pre-filter the User API Filtering search results or remove the API selected for the first user. (APIM-942)

Test mode

Fix:

  • Previously, an incorrectly formatted message was presented to users who attempted to run a listener process in Test mode. With this fix, the message is correctly formatted. (INT-1725)

XSLT transformation

Feature:

  • XSLT transformation functionality, formerly a Tech Preview, is Generally Available for production use with this release. (INT-1495)

    To learn more about this feature, see the topic XSLT Stylesheet components.

AtomSphere API and Partner API

AS2 Connector Record object

Fix:

  • Query operations occasionally returned inconsistent results from one request to the next for executions with 100 or more processed documents. With this fix, the returned results from one request to the next are reliably consistent with Boomi Integration Process Reporting. (B2B-733)

    Note: This fix was rolled back subsequent to the March 2020 release. The issue will be addressed in a future release.

Component Metadata object

Feature:

  • With the introduction of the Component Metadata object, you can programmatically query the component metadata in your account, similar to searching for components from the Component Explorer within the Build tab. This provides you with information including name, component type, folder, revision, and more. You can also search across component revision history, to create audit reports of which users changed which components, for example. (INT-1677)

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

Deployed Package object

Feature:

  • The componentVersion field is added to the Deployed Package object. componentVersion represents the component revision number of the primary component (for example, a process component) included in the deployed packaged component. (INT-1703)

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

EDI Connector Record objects

Fix:

  • X12, EDIFACT, HL7, RosettaNet, and Tradacoms connector record query operations occasionally returned inconsistent results from one request to the next for executions with 100 or more processed documents. With this fix, the returned results from one request to the next are reliably consistent with Boomi Integration Process Reporting. (B2B-874)

    Note: This fix was rolled back subsequent to the March 2020 release. The issue will be addressed in a future release.

Packaged Component object

Feature:

  • The componentVersion field is added to the Packaged Component object. componentVersion represents the component revision number of the primary component (for example, a process component) included in the packaged component. (INT-1702)

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

Process Schedules object

Fix:

  • Query operations returned an error if a process schedule in the results had an invalid maximum retry count. With this fix, the query returns process schedules, as expected, with a default value for retry schedules. (INT-1478)

Trading Partner object

Feature:

  • The Trading Partner object is extended to support AS2 communication with Basic authentication for inbound EDI. (B2B-791)

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

Connectivity


SDK connectors

Feature:

  • There is a new Tracking Direction read-only setting for all connector operations built using the Connector SDK. For a given operation, this setting shows the tracking direction — Input Documents or Output Documents. (CON-718)

    • The default value for Get and Query operations is Output Documents.

    • The default value for Create, Update, Upsert, Delete, and Execute operations is Input Documents.

    • Start Shape operations have no input, so the value is always Output Documents.

  • This setting is determined by a configuration change, affecting which document appears in Process Reporting.

Fix:

  • The SDK listener batch manager did not close if an exception was thrown while attempting to stop the Listen operation. This left open resources if the connector did not submit all of its open or pending batches. With this fix, if an exception occurs while attempting to stop the Listen operation, the batch manager stops, too. (CON-775)

AS2 Shared Server connector

Feature:

  • Basic authentication for AS2 listener operations is now supported. (B2B-750)

    To learn more about this feature, see the topic AS2 Shared Server operation.

Database connector

Fix:

  • If a document with user-defined dynamic document properties passed into a Database connector shape with configured parameters, the dynamic document property values did not persist through the connector shape upon process execution. With this fix, the values persist through the connector shape upon process execution. (CON-338)

FTP (Tech Preview) connector

Features:

  • A new Get operation is available, enabling you to retrieve a single file from an FTP server by its unique ID. As an added convenience, you can choose to delete the file from the server after being retrieved to prevent the same file from being processed twice. (BOOMI-16159)

    To learn more about this feature, see the topic FTP (Tech Preview) operation.

  • A new List operation is available, enabling you to retrieve a list of file metadata entries from an FTP server. This is a convenient way to retrieve a set of documents, with each document having the metadata for a file stored in the corresponding FTP server. By doing so, you can avoid the actual cost of transferring the files. (BOOMI-16156)

    To learn more about this feature, see the topic FTP (Tech Preview) operation.

Google Pub/Sub connector

Fix:

  • The connector was not displaying tracked fields in Process Reporting for Pull operations. Properties such as Resource Id, Message Id, Acknowledge Id, and Publish Time were missing values even if the Google API provided them. Additionally, if a message was retrieved, the document payload was always displayed as 0.0 KB. With this fix, the connector reports results and associated metadata for Pull operations as expected, and the correct document payload size is displayed. (CON-258)

Kafka connector

Feature:

  • To expand the authentication capabilities of the connector and increase the security in a Kafka cluster, you can authenticate using Kerberos (GSSAPI). (BOOMI-40329)

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

Fix:

  • The connector's Commit Offset operation was not failing during process execution when the JSON input profile omitted the partition or offset ID. As a result, the operation used 0 (zero) as the default value which was not always the correct value. With this fix, the operation correctly fails when either the partion or offset ID is omitted from the input profile. (BOOMI-41472)

Microsoft Azure Service Bus connector

Feature:

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

Fix:

  • The connector was not displaying tracked fields in Process Reporting for Receive operations. Properties such as Message Id and Sequence Number were missing values even if the Microsoft Azure API provided them. Additionally, if a message was retrieved, the document payload was always displayed as 0.0 KB. With this fix, the connector reports results and associated metadata for Receive operations as expected, and the correct document payload size is displayed. (CON-259)

Oracle E-Business (EBS) connector

Fix:

  • Previously, when executing stored procedure calls and queries, the connector provided all parameters to the procedure call even when the parameters were missing in the incoming XML document. The connector set the missing parameter values to NULL, resulting in DEFAULT values set for optional parameters not being used. With this fix, you can use the Exclude missing parameters from the procedure check box to determine if parameters missing from the input document should be excluded from the procedure call, or include them with a value of NULL. (CON-604)

    Note: This fix is deferred from the release.

SAP Cloud for Customer connector

SAP is ending their support cycle for their SOAP APIs and deprecating their SOAP API for the Cloud for Customer service. As a result, their service and the SAP Cloud for Customer connector are no longer available for customers who have not previously used them. If you are using this connector in production processes, you can continue to do so. (CON-877)

SAP connector

Fix:

  • There was a known issue where SAP Java Connector 3.0.x versions greater than 3.0.19 were not working with the SAP connector. With this fix, SAP Java Connector 3.0.x versions greater than 3.0.19 work as expected. (CON-609)

SFTP connector

Fix:

  • If a document with user-defined dynamic document properties passed into an SFTP connector shape with configured parameters, the dynamic document property values did not persist through the connector shape upon process execution. With this fix, the values persist through the connector shape upon process execution. (CON-339)

Web Services Server connector

Feature:

  • Processes started with this connector in the Start shape now include inheader_ for OData endpoints that are set in the Dynamic Document Properties header settings and are not in a protected header group. These inheader_ prefixes will cause the prefix outheader_ on the result document. (APIM-12)

    Note: This feature has companion changes covered in the Boomi Integration section of these release notes.
    Note: This connector update is deferred to the April 2020 release.

Fix:

  • Dynamic Document Property Headers were being returned in the same case as the HTTP header request. This caused false null values being returned due to a case insensitivity when calling the inheader_ value. For example, calling inheader_Test was returning a null value because all headers were being generated as lowercase and sending the value as test rather than Test. With this fix, the Dynamic Document Property Header is matched to the HTTP header regardless of case, removing the false null values being returned. (APIM-873)

    Note: This fix has companion changes covered in the Boomi Integration section of these release notes.
    Note: This connector update is deferred to the April 2020 release.

Connectivity development


Connector SDK

Features:

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

  • The SDK is updated to expose custom properties in an OAuth2Token response so that custom connectors can access them. To access these additional custom properties, add a generic getProperty(key) method to Oauth2Token, allowing custom connectors to interact with services that require them. (CON-595)

  • Atom Proxy configuration values are accessible using the following method: getContext().getConfig().getProxyConfig();. (CON-485)

Master Data Hub

Deployment

Fix:

  • Upon deployment of a new version of a model, the tagging of the domain’s golden records was not re-evaluated. With this fix, tagging is re-evaluated, as expected. (HUB-735)

Modeling

Feature:

  • The model page is redesigned. The new design is consistent with configuration pages in other platform applications. (HUB-643)

    These are the notable changes:

    • Tabs are vertically aligned.

    • Action buttons are horizontally aligned.

    • Select the new Name and Root Element tab to name the model and copy the root element name to the system clipboard. This tab is automatically selected when you create a model.

    • Select the new Record Title Format tab to specify the golden record title format. You no longer need to first designate “title fields” in the Fields tab.

  • To learn more about this feature, see these topics:

Platform API

Fix:

  • The Deploy Universe response erroneously included milliseconds in the <mdm:deployDate> timestamp. With this fix, milliseconds are omitted, which means the timestamp format is consistent with the timestamp format in the Get Universe Deployment Status response. (HUB-686)

Repository API

Fix:

  • The Query Golden Records endpoint returned inaccurate results in certain cases. With this fix, all queries should return accurate results. (HUB-690)

Stewardship

Fixes:

  • In the quarantine entry detail view, a reference field value for a resolved reference to a golden record in a reference data domain was incorrectly shown. The value shown was the source entity ID linking the referenced golden record to the default source. With this fix, if the reference data source field is a title format field, the reference field value shown in the quarantine entry detail view is the actual value from the default source, as expected. (HUB-697)

  • In the Quarantine page, it was not possible to change the repository and domain selection while the quarantine entries list loaded. With this fix, changing the repository and domain selection is possible while the quarantine entries list loads. (HUB-704)

B2B/EDI Management


AS2 communication

Feature:

  • Basic authentication for AS2 communication is now supported for inbound EDI. Implementation of this feature required an update to the AS2 Shared Server connector as well as the platform. (B2B-750)

    Note: This feature has a companion update to the Trading Partner object in the AtomSphere API.
    To learn more about this feature, see these topics:

Fix:

  • When the AS2 communication method used in a process was configured with Data Processing options, it was not possible to view or download documents associated with an execution of that process from Process Reporting, even though purging of execution data should not yet have occurred. With this fix, in the same scenario the documents are viewable and downloadable. (B2B-311)

    Note: This fix required updates to the Atom and all EDI connectors.

RosettaNet document handling

Features:

X12 document handling

Features:

  • You can now set ISA Version using a document property. (B2B-942)

  • When a functional acknowledgment is generated in the Start shape, the ISA and GS versions in the acknowledgment are now set to match the values from the original inbound document. (B2B-943)

API Management

Application and Subscription status

Features:

  • On the Configure APIs and Applications > Applications page, clicking Enabled or Disabled in the Status table to open the Application Status window now shows three status options: Enabled, Disabled by Publisher, and Disabled by Consumer.

    Your Developer Portal users can disable the application, which would show as "Disabled by Consumer" in the Application Status window. You, as the application publisher, can enable applications that either you or the consumer disabled. (APIM-762)

    To learn more about this feature, see the topic Applications.

  • When you open the Subscription Status window for a subscription by clicking a value in the Subscription column on the Configure APIs and Applications > Applications page and then clicking Enabled or Disabled in the Status table, the window now shows three status options: Enabled, Disabled by Publisher, and Disabled by Consumer.

    Your Developer Portal users can disable the subscription, which would show as "Disabled by Consumer" in the Application Status window. You, as the application publisher, can enable subscriptions that either you or the consumer disabled. (APIM-761)

    To learn more about this feature, see the topic Applications.

  • Disabling an application does not modify the statuses of the subscriptions for that application. However, the subscriptions cannot be modified until the application is enabled. (APIM-933, APIM-938)

    To learn more about this feature, see the topic Applications and the Developer Portal's Applications page.

Authentication Brokers and API Gateways

Fix:

  • Some custom Java command line parameters were not respected on the Gateway Service. With this fix, custom Java command line parameters are respected. (APIM-1120)

Deployed APIs

Fix:

  • The SOAP 1.2 details tab was not appearing in all cases on the Configure APIs and Application > Deployed APIs page when the API details were viewed. With this fix, the SOAP 1.2 details tab appears when there are SOAP 1.2 endpoints. (APIM-969)

Developer Portal

Features:

  • Disabling an application does not modify the statuses of the subscriptions for that application. However, the subscriptions cannot be modified until the application is enabled. (APIM-935, APIM-938)

  • On the Subscriptions page, the API Key displays for disabled subscriptions. However, the API Key cannot be used to call the API until the subscription is enabled. (APIM-936)

    To learn more about this feature, see the topic Developer Portal's Subscriptions page.

  • Only enabled applications appear in the drop-down menu of applications on the API Catalog page's Subscribe window. (APIM-937)

    To learn more about this feature, see the topic Requesting access to an API.

External Authentication

Fix:

  • Attempting to delete Authentication Sources caused an error. With this fix, you can delete Authentication Sources that have not had subscriptions to attached APIs on the Developer Portal. (APIM-1065)

Boomi Flow

The following information identifies the new features and fixes in Boomi Flow Core releases 1.143.0, 1.144.0, 1.144.1, 1.145.0, 1.146.0, 1.147.0, Hub service 1.0.0, System Flows 1.47.0, 1.47.1, 1.48.0, 1.149.0, Tooling 2.15.0, 2.16.0, 2.17.0, 2.18.0, and User Interface 3.14.0.

Core

Features:

  • API improvements have been made by adding more consistent aliases for the following endpoints into the Run API:
    • GET /api/run/1/state/{stateId}/log: Load the execution log for a state.

    • POST /api/run/1/service/data: Load data from a service at runtime.

    • POST /api/run/1/service/file: List files from a service at runtime.

    • POST /api/run/1/service/file/content: Upload a file to a service at runtime.

    • POST /api/run/1/service/file/delete: Delete a file from a service at runtime.

  • Tenants can be renamed using the /api/admin/1/tenant endpoint. Renaming a top-level/parent tenant will automatically rename the base name of all subtenants to match. (FLOW-1314)

  • The “Public” access type has been added to value elements, as this type of access is required as part of the new subflows functionality. Any values that have been defined as being of ‘Public’ access type when the value was created are automatically passed between a master flow and its subflow. (CORE-5581)

Fixes:

  • Map elements were intermittently being imported into parent flows from child subflows, due to a problem with map element dependencies. With this fix, subflow map elements are not duplicated into parent flows when using the subflows functionality. (FLOW-1383)

  • Message actions were not correctly handling value elements of a list type. With this fix, a flow builder can only select or create lists of a type that matches the selected input list type as the list type is automatically populated with the correct types. (CORE-5586)

  • Multiple groups of asynchronous message actions running in parallel were not 'waiting' if the service sent back a WAIT response. With this fix, these message actions wait as expected. (FLOW-1341)

  • Object type values were not being translated correctly when translating a flow. With this fix, object type values are translated correctly. (CORE-5602)

  • When multiple flows were paginated on the Flows page, the last flow listed on the previous page was also the first flow listed on the next page. With this fix, pagination works correctly. (CORE-5595)

  • SAML authentication was not performed correctly when used with the OKTA identity provider. With this fix, SAML authentication is implemented correctly with an OKTA identity provider. (CORE-5569)

  • The SAML authentication RelayState and TargetResource parameters have been reduced in size to meet IdP standards that specify these values should not be bigger than 80 bytes in size. With this fix, IdP standards of this type are now met for these parameters. (CORE-5594)

  • Using values in a subflow map element without importing them resulted in an error. With this fix, any value elements used within a Subflow map element are automatically imported into the current flow, removing the need for a manual import of the selected values. (CORE-5589)

  • Validation was disrupting authorization when re-initializing a flow with an existing state ID, if the flow ID parameter was not present. With this fix, re-initializing a flow with a state ID does not require the flow ID to correctly pass validation. (FLOW-1331)

  • Value elements used within the step map element content field were not being located correctly, resulting in an error: “Could not find a value in the flow with the ID {ID}.” With this fix, value elements used within a step map element content field are automatically imported into a flow. (CORE-5565)

Hub Service

Features:

  • The Hub service allows you to load any deployed universes in your account into Boomi Flow. (FLOW-1264)

    During the Hub service installation, three bindings are created for each deployed Universe in the account, supporting the following features:
    • Golden Record: Supports the ability to load, create, update and delete golden records from different sources and the use of filters.

    • Quarantine: Supports load entities in quarantine from different sources and the use of filters.

    • Match rules: Supports the sending of a batch from a specified source into a flow, allowing you to test the application of match rules against these batch entities for a specified universe.

    To learn more about this feature, see the topic Hub service.

System Flows

Features:

  • As part of the MDH service 1.0.0 release, the Hub service entry in the Which Service would you like to install? drop-down menu has been amended to remove the ‘Tech Preview‘ status. (FLOW-1391)

  • The value Access selection field is moved from the lower Advanced section to a more prominent position at the top of the Value page. This is due to value access type being closely linked to the new subflows feature. (FLOW-947)

  • The “Public” access type has been added to the value Access selection field as this type of access is required as part of the new subflows functionality. Any values that have been defined as being of "Public" access type when the value was created are automatically passed between a master flow and its subflow. (FLOW-949, FLOW-950)

  • The Install Service drop-down menu on the Install Service page has been updated to allow the following services to be selected when installing a service:
    • Amazon Polly (Tech Preview)
    • Amazon Rekognition (Tech Preview)
    • Amazon S3
    • Box
    • Hub (Tech Preview)
    • Onelogin (Tech Preview)
    • PDF
    • Runtime
    • SAML

Fixes:

  • Editing an outcome directly would not display the Edit Business Rules button on message, decision, page, database load, or database save map elements. With this fix, the button is again visible on these map elements. (FLOW-1279)

  • Page component bindings were not being saved correctly. With this fix, page component bindings can be saved. (FLOW-645)

  • The maximum character length for an encrypted value has been increased from 1,000 to 1,000,000 characters. With this fix, encrypted certificates can be saved as values. (FLOW-772)

  • When changing a page component from using a Service source to a List source, the objectDataRequest metadata value was not cleared. With this fix, this metadata value is cleared, as expected, when the data source for a Page component is changed. (FLOW-404)

Tooling

Features:

  • Subflows functionality is now available. Flows can be called by other flows as “subflows,” allowing you to reuse flows across multiple workflows. To learn more about this new feature, see subflows.

  • Improvements have been made to the user interface for creating and editing values in the value editor, currently implemented when inserting values into presentation components and creating basic page conditions. These improvements will help flow builders when creating and editing complex values. (FLOW-654)

  • Tenants can be renamed using the new Name field on the Tenant Settings page. Renaming a top-level/parent tenant will automatically rename the base name of all subtenants to match. (FLOW-1314)

  • The value Access selection field is moved from the lower Advanced section to a more prominent position at the top of the Value page. This is due to value access type being closely linked to the new subflows feature. (FLOW-922)

  • When a flow builder attempts to create a value with a duplicate name, a warning message is displayed to inform them that a value already exists with the selected name. (FLOW-459)

Fixes:

  • Copying and pasting a selection of map elements between flows could sometimes result in all map elements being pasted into a flow, instead of just the selected map elements. In addition, the pasted map element also still retained the same map element id, meaning that any changes made to the original map element were also made to the duplicate pasted map element. With this fix, copying and pasting map elements between flows now works correctly. (FLOW-1172)

  • Exporting a package using the /api/package/1/flow/(id) endpoint in the API tool would display the content in the Response pane in an altered format. With this fix, the content in the Response pane is now displayed in its original, obfuscated form. (FLOW-865)

  • Subflow configuration panel subheadings were being displayed in a different font and style to other configuration panels on the flow canvas. With this fix, the styling of the configuration panel is now consistent with the rest of the flow canvas configuration panels. (FLOW-1197)

  • Subflow map elements were not being correctly positioned and contained within a swimlane on the flow canvas. With this fix, dragging a subflow map element into a swimlane correctly positions the subflow map element inside the swimlane and assigns it to the swimlane. (FLOW-1262)

  • System value elements (such as $False) were not available for selection when configuring a service. With this fix, these system value elements are available for selection. (FLOW-1248)

  • The Clear selection cross icon on the Select a flow to run as a subflow drop-down menu on the Subflow configuration pane was not correctly clearing the user selection when clicked. With this fix, clicking this icon clears the user selection, as expected. (FLOW-1234)

  • The Reporting endpoint URL field on the Tenant Settings page was not cleared when a new subtenant was created. With this fix, the field is cleared of any previous values, as expected, when a new subtenant is created. (FLOW-459)

  • The Select a flow to run as a subflow drop-down selection menu on the subflow map element was also displaying the search term underneath the selected flow. With this fix, once you have selected a flow from the menu, the search term is no longer displayed. (FLOW-1235)

User Interface

Fixes:

  • Client-side validation on input fields was being erroneously performed when using a navigation element to navigate between pages in a flow. With this fix, client-side validation is performed as expected when a user clicks on an outcome, but users can still navigate between pages and input forms without validation interrupting the user. (FLOW-501)

  • Client-side validation was not being correctly performed on hidden fields within a flow. For example, if page conditions were being used to hide required fields, the default player (which has client-side validation disabled by default) would not perform any validation on these fields and a user could advance through a flow even if the fields were required. With this fix, client-side validation will not be performed on a component if the component is hidden or disabled. (FLOW-846)

  • Date/time input fields modified using the date/time selector were unable to be cleared by a user when running a flow as the value would be re-inserted when the user clicked outside of the input field. With this fix, date/time input fields can be cleared by a user as expected. (FLOW-845)

  • Flows that were run in an Internet Explorer 11 browser were encountering several issues. The build configuration has now been updated so that the flow experience in Internet Explorer 11 is improved. (FLOW-737)