Release 10.16

Explore the release highlights, usage notes, known issues, and fixes for IBM webMethods Integration.

What's New

Release 10.16.5

Resuming workflow execution

You can now resume the execution of one or more failed and timed-out workflows. Earlier, resuming timed-out workflows was not supported.

Reorganization of Cloud Messaging

The Events tab has been added within the Projects section to group all types of events supported by IBM webMethods Integration. From this release, you can access the Cloud Messaging functionality through Events.

Built-In-Services are updated for Flow services

Input and Output signatures are updated for the JSON, MIME, and XML services under the Built-in Services section in the following categories:

JSON: jsonStringToDocument, documentToJSONString, documentToJSONStream, documentToJSONBytes, jsonStreamToDocument, jsonBytesToDocument.
MIME: getEnvelopeStream.
XML: documentToXMLStream, documentToXMLBytes, documentToXMLString, xmlStringToXMLNode, xmlNodeToDocument.

Changes in Clock Trigger

In this release, months are removed from the Runs on every drop-down list under Daily, Weekly, and Monthly clock trigger types.

As per the updated Clock trigger (v9), under Daily, Weekly, and Monthly Clock trigger type, the maximum value for Runs on every field is 1 Day.

New and Updated Connectors

Explore new and updated connectors released recently in IBM webMethods Integration.

Fixes included in the 10.16.5 release

See the Fixes section for information on the 10.16.5 fixes.

Release 10.16.4

Enhanced security for password-protected project parameters

From this release, values of password-protected project parameters are masked by default and are not disclosed in API responses. This significantly strengthens the security of password-protected project parameters.

**Support to retain the value of the Invoke Flow service over HTTP option**

When you enable the Invoke Flow service over HTTP option for a Flow service and then proceed to clone, export, or import it, the option remains enabled in the resulting cloned, exported, or imported Flow service. This enhancement ensures that your desired settings are retained.

New and Updated Connectors

Explore new and updated connectors released recently in IBM webMethods Integration.

Fixes included in the 10.16.4 release

See the Fixes section for information on the 10.16.4 fixes.

Release 10.16.3

Insights

The Insights feature adds a new module to the IBM webMethods Integration portfolio. The primary objective of this capability is to provide you with statistics of transactions. This is achieved through the use of graphical depictions highlighting your usage of Flow services and Workflows.

The Insights feature helps you with:

A clear representation of your usage of IBM webMethods Integration services.
A thorough understanding of your billed transaction data.
Optimization possibilities within your IBM webMethods Integration services.

Enhanced queryTransaction operation to support custom attributes

queryTransactions operation on the IBM webMethods B2B connector app supports custom attributes as a filter criteria in the input. Also, in the output, you can view the attributes (up to 5 based on the attribute names specified in the includeAttributes input field), for the transaction in addition to the basic transaction details.

Auto-generate workflow structures based on user prompts

You can now provide input prompts that will automatically generate workflow structures. These workflow structures can be further configured and customized to align with your specific business requirements and use cases.

This NLP-based feature is currently in beta phase. After release, we invite you to give it a try and share your thoughts and feedback with us, so that we can enhance it further.

Restarting workflow execution

You can now restart execution of one or more failed, timed out, and stopped workflows. Earlier, restarting timed-out workflows was not supported.

Increased transaction limit for Free Forever Edition tenants

The transaction limit for all Free Forever Edition plan-enabled tenants is increased to 2000 transactions per month. Earlier, it was 1000 transactions per month.

Support for storing assets at the user level while publishing projects

When you publish a project, only the assets that you have selected now appear as preselected on the Select Assets screen when you attempt to publish the project again. Previously, when publishing the same project, assets selected by other users were also displayed as preselected.
When you try to republish a project previously published before this (10.16.3) release, no assets appear as preselected under the Select Assets screen.

Debug panel enhancements

The Debug Panel now shows the logs in a collapsible format by default. You can expand it to view logs from a specific action.
Previously, if the log size exceeded 250 KB, a message stating Message Size Too Large was displayed. Now, with the improved user interface, you can expand each logger in the Logs and the Actions tab of the debug execution panel to view log data of up to 10 MB.
Note - The input, output and log under the Actions tab and the workflow executions log under the Monitor tab shows the log data of up to 10 MB.

API enhancements

The following enhancements have been made to the APIs listed below:

Reference data API: The base path for all reference data APIs has been changed to "/apis/v1".
Import API: You can now overwrite an existing workflow within a specified project by appending a request body parameter "overwrite=true" in the endpoint URL "/apis/v1/rest/projects/:project/workflow-import".

Terminology change

The term Pending used to indicate the execution status of a workflow that is waiting to be processed has been replaced with Queued. This terminology change will affect all instances where the old term was used to describe this workflow status.

New and updated connectors

Explore new and updated connectors released recently in IBM webMethods Integration.
Read More

Fixes included in the 10.16.3 release

See the Fixes section for information on the 10.16.3 fixes.

Release 10.16.1

SAP® ERP Lookup

SAP® ERP now allows you to perform metadata lookups for function interfaces, business objects, IDocs, and tables in SAP ABAP application servers.

Increased maximum execution runtime limit for sync and async workflows

The maximum execution runtime limit has been increased to 6 minutes for sync workflows and 90 minutes for async workflows.

Earlier, the maximum execution runtime limit for sync and async workflows were 3 minutes and 30 minutes respectively.

You can configure the required execution runtime for your sync and async workflows by going to the particular <workflow> > Workflow settings > Execution settings > Maximum Workflow Runtime (in Minutes).

Introducing suspension and deletion for inactive Free Forever Edition tenants

All inactive Free Forever Edition tenants will be suspended after 45 consecutive days of inactivity and deleted after 75 consecutive days of inactivity.

Read More

Transaction Count for Workflow Executions

You can now select the Transaction Count column in the Executions table for workflows by clicking the Settings button in the workflow execution page. The Transaction Count column displays the number of transactions that have been consumed for each workflow execution. Earlier, this option was available only for Flow services in the Flow service execution page.

Flat File Connector Enhancements

Following enhancements are made to the Flat File Connector wizard for better usability:

Flat File Description Page

Drag and Drop Files option is provided for the flat file creation and the connector icon upload.
Use the Show Preview or Hide Preview option to view or hide the file details respectively.

Flat File Type Page

Custom drop-down input with predefined list of values is provided to select values for Delimiter, Fixed Length, and Variable Length parsers.

Added the Use first row as field labels checkbox. You can select it to convert the values of the first row to column headers. This checkbox remains disabled until the record length is selected.

The default value for Record Identifier Position is changed from Start at character position to Start at field position.

Flat File Summary Page

The connector Summary page is enhanced to display the Description (File name, Description, and Connector icon) and the File Type (Parser type and Parser fields value) details.

Independent options for restart and resume Flow service executions

IBM webMethods Integration now provides independent options to restart and resume Flow service executions. Selecting the Enable Flow service to be restarted option on the Overview page of a particular Flow service displays the Restart button on that Flow service’s Execution Details page, while selecting the Enable Flow service to be resumed option on the same page displays both the Restart and Resume buttons on the Flow service’s Execution Details page.

Alternatively, you can also restart or resume a Flow service on the Monitor page using the corresponding buttons in the Actions column. However, it is important to note that if you choose to resume a Flow service with only the restart option enabled, it will trigger a full restart instead of resuming from the point of failure.

Copying of existing REST APIs across Projects

IBM webMethods Integration now allows you to copy an existing REST API from the REST APIs page to another project. You can locate the Copy icon in the Action(s) column, next to the Edit and Delete icons. Previously, this feature was available for SOAP APIs only.

Enhancement in Search Methods

Flow service step now supports two different search methods:

Alias-based search
Restricted scope search

Alias-based search

The alias-based search method allows you to search for specific keywords, for example, map, iteration/loop.
Read More

Restricted Scope search

The restricted scope search method allows you to search specific keywords followed by the pipe symbol within a specific scope, for example, type fs| to search within Flow services.
Read More

Support for Account Interoperability for Coupa in Flow services

IBM webMethods Integration offers support for account interoperability for Coupa in Flow services, allowing you to easily switch between multiple Coupa accounts that are created using both basic authentication and OAuth 2.0 authentication. This feature provides greater flexibility and efficiency when working with different accounts within the same Flow service.

Release 10.16.0

Error Management for Salesforce Listeners

Listeners functionality is introduced with an error management mechanism. As an integration developer, you can now configure an error call-back service and be notified when an error occurs with the Salesforce listener communication.

You can configure a Flow service to address how a listener must behave in case of errors. A new drop-down menu, Select ErrorCallBackFlowService name, has been added under the Event tab in the Add Listeners wizard. From this drop-down menu, you can either create a new Flow service or choose an existing Flow service that defines the listener behavior when an error occurs.

See this tutorial for more information.

Runtime Status of Connector Listeners

You can now view the runtime status of a connector listener from the Listeners screen. A new column Status is introduced to display the runtime status for each listener.

If the Status is Active, it indicates that the configured cloud connection for a connector is successful and active.
If the Status is Disabled, it indicates that the configured cloud connection for a connector is inactive.
If the Status is Suspended, it indicates that the configured cloud connector listener was successfully enabled, but the subscription is currently inactive. To get a detailed explanation of the error status, you can click on the Suspended status in the Status column.

Note

If the SAP® ERP Connector listener status is Suspended, it indicates that an error occured during enabling or disabling the listener.

Listener Improvements

Improvements were made in listeners to:

Ignore duplicate trigger listener entries in Workflows.
Avoid multiple executions and intermittent lack of response from listeners.

If you are using on-premises Integration Server v10.15 for hybrid connectivity, and if your hybrid connectivity uses two-way SSL, ensure that you have installed IS_10.15_WmCloud_Fix1 or higher in your environment.

In this release, on-premises Integration Server 10.3 or higher versions with the latest on-premises Integration Server and Universal Messaging fixes are supported for hybrid connectivity.

Size Limit for Hybrid Integration Messages

The maximum size limit of an encoded service output to be transported over Hybrid Integration is 50 MB.

The following encoding limits are enforced:

java.lang.String uses a fixed width encoding of 2 bytes per java.lang.Character. In general, all data types excluding java.lang.Integer and java.lang.Byte are converted to java.lang.String before encoding. For example, a java.lang.String must be less than 25 MB, however, a byte[] must be less than 50 MB.
Each field or value within the Service Output is framed with metadata during encoding, and this is added to the encoded data.
The Service Output being transported is encoded into a single cumulative piece, so consideration for the number of fields and their cumulative sizes are needed.

Hybrid Integration Architecture Improvements

Routing mechanism of the hybrid integration solution is enhanced. In the hybrid integration solution, IBM webMethods Integration uses Universal Messaging (UM) to route messages to the on-premises applications and vice-versa. While configuring the connectivity (routing) settings, currently the host name is provided in the format, um.int-aws-de.webmethods.io.

In the new approach, the host name format has been changed to *.um.int-aws-de.webmethods.io, where * indicates the tenant-specific identifier.

Example:

Old UM URL: nhps://um.int-aws-de.webmethods.io:443//stage00-um-1397192613 -1012/
New UM URL: nhps://tenant subdomain-ade43fe.um.int-aws-de.webmethods.io:443//tenant subdomain/, where ade43fe is a unique number generated by the system to identify the Integration Server.

Ensure that you allow the following domains in your firewall or proxy settings:

Region	Allowed domains
US1 Oregon AWS	*.um.int-aws-us.webmethods.io
EU2 Frankfurt AWS	*.um.int-aws-de.webmethods.io
AU2 Sydney AWS	*.um.int-aws-au.webmethods.io
US2 East Azure	*.um.int-az-us.webmethods.io
EU3 West Azure	*.um.int-az-eu.webmethods.io
AU1 Australia East Azure	*.um.int-az-au.webmethods.io

Note

For the list of allowed IPs, see the IBM webMethods Integration section under IP Addresses.

To migrate to the new hybrid routing mechanism, it is recommended to perform Update Settings and restart the on-premises Integration Server. On-premises Integration Server remains connected to the old Universal Messaging URL unless the settings are updated and the Integration Server is restarted.

With this change, cloud hybrid communication traceability has improved.

Enhanced rate limits for manually run, trigger-enabled, and async webhook-enabled workflows

Under paid plans, you can now send execution requests for up to 15000 workflows within a minute. Earlier this was 1500. The first 15000 requests are processed, while the rest of the requests are Rejected.

Under trial/unpaid plans, you can now send execution requests for up to 300 workflows within a minute. Earlier this was 30. The first 300 requests are processed, while the rest of the requests are Rejected.

Such workflows are indicated with a Failed status against them in the Workflow Execution section of the Monitor page.

Execution Settings Enhancements

The seven day restriction on the Maintain workflow execution logs when executed via webhook or trigger checkbox under Execution settings is removed.
Earlier, when you selected the Maintain workflow execution logs when executed via webhook or trigger checkbox under Execution settings, it was auto-disabled after seven days. From this release, when you select this checkbox, it stays selected until you deselect it manually.

New APIs

New APIs have been introduced in the following domains:

Account APIs: Allows you to retrieve, delete, and switch accounts from the workflow connector and also update the account configuration.
Metrics APIs: Allows you to retrieve the execution summary and logs.
Reference APIs: Allows you to retrieve, add, and update the reference data.

Monitor Page Enhancements

The following enhancements are now available in the Workflow Execution and Flow service Execution features:

You can now directly retrieve a list of all successful, failed, or pending Workflow or Flow service executions from the Execution Status filter. Earlier, you had to choose Project(s) and Workflow(s)/Flow service(s), before selecting execution status(es) to retrieve the execution data.

You can now set the limit of the number of items to be displayed per page by clicking on the Items per page drop-down menu located at the bottom of the Executions table. By default, 50 items are displayed on a single page. The maximum page size is restricted to 150 items.

The execution listing section in the Monitor page is enhanced to provide two new options for Restart and Resume under the newly added Actions column. Using these options, you can restart and resume Workflow and Flow services executions from the main execution listing page.
You can now select one or multiple failed Workflow or failed/successful Flow service executions to restart in a single click. To do this, in the Executions table, select the checkbox beside the name of failed workflows or failed/successful Flow services and click the Restart button. The checkboxes will be enabled only if the restart capability is enabled and also if the Enable Flow service to be restarted option is checked on the Overview page of the Flow service. In earlier releases, you could restart only one Workflow/Flow service execution at a time.

In the Executions table, a new label named Restarted is introduced in the Status column . This label indicates that the corresponding failed workflow execution or failed/successful Flow service execution is restarted successfully.

The chart view that shows the graphical representation of Workflow/Flow service executions located in the Workflow Execution and Flow service Execution page is now named as Overview. For better readability, you can now expand or collapse the Overview section by clicking the down arrow located next to Overview.

Flow service Execution Results for new tenants are now retained for a period of seven days.

Monitoring SAP® ERP Performance

You can now monitor the SAP® ERP performance, the SAP® response time summary, query requests, and query components from the Monitor page.

Monitoring SAP® ERP Connection Pools

You can now monitor the SAP® ERP repository connection pools, the SAP® ERP client connections, and the listener status from the Monitor page.

New SAP® ERP Built-In Service

The new SAP® ERP built-in service createTIDOffline has been introduced in this release.
createTIDOffline allows you to obtain a transaction ID (TID; which is a GUID) that conforms to the format of SAP TIDs even when not connected to a SAP system. The transaction ID is based on a randomly created UUID Version 4.

Flow service Enhancements

Following improvements have been made in Flow services for ease of use:

Flow services are made available by default for all tenants. Earlier, you needed to contact IBM to enable Flow services for your tenants.
The Transform Pipeline panel is enhanced with the Expand All and Collapse All buttons. Using these buttons you can easily expand and collapse all nodes nested within another in a single click instead of navigating to each node.
The Context ID details are displayed in the Flow service Execution page if a Flow service is created with Context ID. Earlier, the Context ID details were not displayed.
The Picklist field in the Define input and output fields page is enhanced for better ease of use. The Add and Delete buttons are provided for each list item for adding or deleting the corresponding item. To modify an item, you can double-click the item and update with a new value.

Additionally, the Allow other values checkbox is provided under the Picklist field. If selected, you can enter new values while providing inputs during runtime. Otherwise, you can select only from the list provided in the Define input and output fields page.

Earlier, an Untitled entry got added by default and to delete it, you had to click Edit, select the item, and delete it. The up and down arrows are no longer available to reposition the items.
Service names are now displayed correctly across the Pipeline panel. Earlier, the name in the step and name in the Input and Output column headers were not the same.
The Set Value dialog is enhanced with the Copy and Paste buttons and a read-only custom text area. By default, the normal text area is displayed for you to provide values. If the number of character limit exceeds, then the read-only text area with Copy and Paste buttons is displayed.
Earlier, when the character limit exceeded, the Set Value dialog box did not respond and the Flow service failed.
Flow services now support the String Table, Date, and Character datatypes in addition to the existing datatypes.
The Cancel button is added in the New Reference Data wizard for canceling the action at any time.
The messages displayed during export are updated to provide additional information related to the components that are not exported or published.
You can now select multiple fields by pressing a Ctrl key in the Define input and output fields page. Additionally, you can perform Cut, Copy, Paste, Duplicate, and Delete operations.
The Clear All option is available for the transform step in the pipeline panel. You can clear the parameter values with a single click instead of clearing each parameter.
Earlier, the Clear All option was not applicable for the transform step.
A new option Add Document Type is provided for the Document reference option in the Define input and output fields page. On selecting the Add Document Type option, you are redirected to the Configurations page where you can add and define new document types in a new window. After saving the document types, the new document type is automatically added in the Define input and output fields page.
Earlier, you had to first add document types in the Configuration page before defining the input or output fields in the Define input and output fields page. With this option, you can now add and define new document types while defining the input or output fields.
A new option emptyString is added in the Case statement to verify if the input string is empty.
A new option Isempty is added in Expression Editor to verify if the input string is empty.

Support for Caching in Flow services

Caching is added for Flow services to store the results of successfully run Flow services for a specified period. When you enable the Caching feature for any Flow service, IBM webMethods Integration stores the results of the invoked Flow service. Next time if the Flow service is run with the same input values, IBM webMethods Integration returns the cached results from the previous invocation and does not run the Flow service again. By using the Caching feature, you can improve the performance of Flow services by improving the response time.

Note

Caching is not available by default for a tenant. To enable this capability, contact IBM Global Support.

The Cache settings dialog box is added to enable and configure caching. You can access the dialog box by using the Settings option from the Flow services page.

Further, you can clear the cache for any Flow service using the Clear cache option.

Support Connectivity with Self-hosted Universal Messaging Servers from JMS connector

You can now publish and subscribe messages to publicly accessible self-hosted Universal Messaging servers. This option allows you to leverage your existing messaging system-based solutions to integrate with IBM webMethods Integration. The JMS connector’s Add account wizard has been updated with new settings to support this connectivity.

Support for Reusing Previous Flow service Configurations and Parameter Values during Redeployment

You can now use the existing accounts configured for a Flow service during redeployment. This eliminates the need to manually reconfigure the Flow service accounts during each redeployment.

Moreover, you can now use the previously configured values for project parameters during redeployment. This eliminates the need to manually provide values for project parameters during each deployment.

These enhancements will reduce the cost of deployments and risk of errors while deploying.

Support for Multiple Port Bindings in SOAP Connectors

The URL field in the Add Account dialog box for SOAP connectors now gets updated with the corresponding link as per the selected Port Binding value when creating new accounts. You can also edit the URL to specify a different web service endpoint.

Support for Partner Certificate in SOAP Connectors

A new option, WS Security Partner Certificate Alias, has been added in the Add Account dialog box of the SOAP connector for providing the partner certificate information. With the partner certificate information, you can now invoke a web service using the SOAP connector, which was earlier not possible.

Custom Action Enhancements

While creating a custom action, you can now view the selected value for the Operation, Business Object, and Interaction fields at the top of the corresponding screens.

Label for deprecated triggers

All deprecated published triggers can now be identified by the Deprecated label displayed below the trigger name. The deprecated label appears under the relevant published trigger name on the trigger selection screen, trigger configuration screen, and on the workflow canvas.

Support for Updating Predefined Connector Account Information

You can now edit the account details of a predefined connector directly from Flow services.
Earlier, you had to go to the Connectors tab to edit the account details.

IBM webMethods B2B Connector Enhancements on IBM webMethods Integration

New operations
- getFAReport: Retrieves a list of transactions with reconciled functional acknowledgments and generates a report.
- resubmit: Resubmits the existing transactions of IBM webMethods B2B as new documents based on the transaction IDs.
- reprocess: Reprocesses the existing transactions of IBM webMethods B2B based on the transaction IDs.
- queryTransactions: Retrieves transactions that match the specified criteria.
Read More
Flat file batching for large documents
A new output parameter hasMore is added in the convertFlatFileToDocument to process large flat file documents in batches.

Read More

Connector Enhancements

The CLI connector runtime Node.js version is updated to v18.12.1
The npm library for the SFTP connector is updated from v5.3.2 to v9.0.4

New and Updated Connectors

Explore new and updated connectors released recently in IBM webMethods Integration.

Tutorials

In this release, new tutorials are added to assist you in understanding the features of IBM webMethods Integration.

Flow Service Export and Publish Update

After release 10.16.4, if you are unable to export or publish a certain Flow service after modifying it, we recommend saving the Flow service again. This will resolve the issue.

SOAP APIs Update

As a part of the fix provided for BIC-21088, review the existing client configurations for SOAP APIs and ensure that it is updated appropriately after redeploying any SOAP API. This is important because this fix modifies the port bindings and removes the source tenant information. As a result, the SOAP API WSDL might become incompatible with existing client setups.

AS2 Connector Update

If you receive the Connection field is not available for field key accountName error while editing the account configurations for AS2 connector, delete the existing account and create a new one.

SSL/TLS Certificate Update

SSL/TLS certificates for IBM webMethods Integration will expire on the date mentioned in the Service Status page. If you are currently using SSL/TLS certificates with IBM webMethods Integration, download the updated certificates from the location mentioned in the Service Status page and replace your existing certificates.
If you do not update the certificates, 2-way SSL transactions will fail and you might experience an SSL handshake error. Root and intermediate certificates remain unchanged.

SFTP Connector Update

For SFTP connector, when you receive sftp.list is not a function or sftp.put is not a function or No SFTP connection available error, replace the existing SFTP connector with a new one and reconfigure the action and connection.

Hybrid Connectivity Update

If you are using on-premises Integration Server v10.15 for hybrid connectivity, and if your hybrid connectivity uses two-way SSL, ensure that you have installed IS_10.15_WmCloud_Fix1 or higher in your environment.
Read more

Hybrid Integration Update

The host name format for Hybrid Integration has been changed to *.um.int-aws-de.webmethods.io, where * indicates the tenant-specific identifier.

Ensure that you allow the following domains in your firewall or proxy settings:

Region	Allowed domains
US1 Oregon AWS	*.um.int-aws-us.webmethods.io
EU2 Frankfurt AWS	*.um.int-aws-de.webmethods.io
AU2 Sydney AWS	*.um.int-aws-au.webmethods.io
US2 East Azure	*.um.int-az-us.webmethods.io
EU3 West Azure	*.um.int-az-eu.webmethods.io
AU1 Australia East Azure	*.um.int-az-au.webmethods.io

Regular Expression Update

The replace and tokenize built-in String services accept a regular expression as an input. If execution of one of these services results in the java.util.regex.PatternSyntaxException, change the syntax of the supplied pattern. For example, if your regular expression has a value of , change it to . This change is required because characters like { or } need to be escaped with \ in the expression.
Read more

Usage Notes

This section provides any additional information that you need to work with IBM webMethods Integration.

IBM webMethods Integration is supported on the latest version of Google Chrome web browser (v110 or later).
Every time you upgrade IBM webMethods Integration, ensure that you clear the cache manually before logging in to IBM webMethods Integration. This is because the older browser’s cache and cookies are not cleared automatically and the page content may not display correctly.
IBM webMethods Integration is best experienced when the scale and layout settings are as follows:
IBM webMethods Integration supports Transport Layer Security (TLS) version 1.1 and version 1.2 for connectivity.
Any time stamp displayed in IBM webMethods Integration is based on the user’s registered time zone specified in IBM webMethods iPaaS. Not all the time zones in IBM webMethods iPaaS are supported in IBM webMethods Integration. If a time zone in IBM webMethods iPaaS is not supported, then the time stamp in IBM webMethods Integration defaults to the Pacific Standard Time (PST) time zone. To change the time zone for a user profile, using the App Switcher, go to IBM webMethods iPaaS and in IBM webMethods iPaaS, click Administration. On the Administration > Users page, edit the user profile. Under Locale information, select the required Time zone. Save the changes, log out, and then again log in to see the changes.
IBM webMethods iPaaS products are available in several geographical regions, operated by different infrastructure providers. Go to the IP Addresses and Regions website for information.
See the Tenant URL and IBM webMethods iPaaS Region section to identify the IBM webMethods iPaaS region based on your tenant URL.
For information on major releases, hotfixes, and patch releases including the latest statistics on the availability of cloud environments, incident history, and planned maintenance events, see the Service Status page.
IBM webMethods Integration v10.16 uses the regular expression pattern as described in the java.util.regex.Pattern class. Earlier, IBM webMethods Integration used Perl 5 compiler and pattern matching while evaluating regular expressions. Some Perl 5 constructs are not supported by java.util.regex.Pattern which can result in unexpected behavior, such as a java.util.regex.PatternSyntaxException during expression evaluation. If your Flow services use regular expressions based on Perl 5 constructs, it is recommended to review the regular expressions to ensure compatibility with the behavior described in the java.util.regex.Pattern class API documentation available here:
https://docs.oracle.com/javase/8/docs/api/java/util/regex/Pattern.html
Review the contents of the Comparison to Perl 5 section, which identifies Perl constructs that are not supported by java.util.regex.Pattern. Regular expressions that rely on these Perl 5 constructs must be modified to work correctly with java.util.regex.Pattern.
Note: The replace and tokenize built-in String services accept a regular expression as an input. If execution of one of these services results in the java.util.regex.PatternSyntaxException, change the syntax of the supplied pattern. For example, if your regular expression has a value of , change it to . This change is required because characters like { or } need to be escaped with \ in the expression.
You can simultaneously open five Flow services in different tabs in a browser.
For SOAP and REST connectors, if you have created an account while creating a Flow service, then that account:
- cannot be edited or deleted from the Connectors page.
- cannot be used in Workflows. The pre-existing accounts are not available in the Connectto drop-down list while creating a Workflow.
- cannot be used in migrated REST applications.
  You have to create a new account in all the above mentioned scenarios.
You can import Flow services using an on-premise connector to different environments. However, you cannot use the Flow service until you configure the on-premise connector in the destination environment.
Ensure to configure the On-Premise connector in the destination environment before publishing a project that has a Flow service using On-premise connector. This is so because, the On-premise connector is not published to the destination environment along with the Flow service.
After changing a REST-based connector’s document type, ensure that you update the operation using that doctype. This updates the operation signature, and the doctype changes reflect correctly in the connector.
After creating a SOAP connector, if you immediately try to update it’s description, the updation process takes longer than usual. Update the SOAP connector by going to the Connectors page.
Some pre-defined operations in the Salesforce® CRM REST connector may not work if you are using an account configured with the JWT flow authentication type.
Click here to see some of the most common scenarios you may come across while configuring an Account, as well as troubleshooting tips on Account configurations. Information on the connector Account configuration fields can be found here. For information on custom actions, custom fields, field lookups, business objects, business parameters, and interactions, click here. Browse through the IBM Tech Community tutorials related to connectors here.
The FTP connector used in a Flow service is different from the FTP connector used in a workflow. So if you create an FTP account in a Flow service, the FTP account will not be available inside a workflow. Similarly, if you create an FTP account in a workflow, the same FTP account will not be available inside a Flow service.
As Reference Data generally varies across different environments, you need to reconfigure the Reference Data as per the respective environment. Therefore if you are publishing a project that has a Flow service with Reference Data, the Reference Data will not be published along with the Flow service. You are required to create the Reference data in the destination environment. Further, if a Flow service you are exporting has Reference Data, the Reference Data will not be exported along with the Flow service. You are required to create the reference data in the destination environment.
Additional headers are observed when running a REST application.
When a REST application Flow service is run with changed header attributes, sw6 headers may be observed in the pipeline output result. Note that sw6 is a valid request header used by End-to-End Monitoring for monitoring IBM product runtimes. This has no impact on feature functionalities.
IBM webMethods Integration does not honor the following headers and their values will be ignored:
- X-Forwarded-Host
- X-Forwarded-For
- X-Forwarded-Proto
- X-Forwarded-By

Although the Workflow to Flow service or on-premises application mapping of the following data types is allowed in IBM webMethods Integration, such Workflows, Flow services, or on-premises applications may not run as expected:
- String type in workflows to Num (Double/Float/Int/Short/Long) type in on-premises applications
- String type in workflows to Byte type in on-premises applications
- Boolean type in workflows to Byte type in on-premises applications
- Object type in workflows to Byte type in on-premises applications
- Number type in workflows to Byte type in on-premises applications
- Array type in workflows to Num type in on-premises applications
- Number type in workflows to Boolean type in on-premises applications
- Boolean type in workflows to Num type in on-premises applications
- Object type in workflows to Num type in on-premises applications
- String of String Array type in workflows to Boolean type in on-premises applications
- Float type in workflows to Num type in on-premises applications
If the data type of a Flow service is set to Object in the I/O signature, then it is considered as a String type in the associated workflow. Such workflows may not run as expected.

Configuring the same client application details across multiple custom OAuth-based accounts may lead to issues related to access token invalidation. To avoid the issues, configure a unique set of client application details for a custom OAuth-based account.

Listeners configured with the Select replay option as New and enabled with a specific replay id might miss some of the replay events. This is in accordance with the current feature design.

As of v10.16, messaging destinations are project-specific, that is, you cannot share Queues and Topics across other projects.

Known Issues

This section lists the issues for this release that were known when this release readme was published.

WFL-2759
When you create a custom Node.js connector with label (name) as test and test it, the output shows error.
Workarounds:

Avoid using test label for custom Node.js connectors.
Do not test a custom Node.js connector labelled as test. You can instead directly execute it.

JDB-3597
When a Database service is edited, a side panel appears by default, which hides the delete or edit button.
Workaround: Minimize the overlay or side panel.

JDB-3602
When the Firefox web browser is used to add or edit the Database Account, port number validation fails.

WSP-1999
SAP® ERP metadata lookup for a business object intermittently returns empty data.

WSP-1758
Contact Support error observed while deploying a project having an SAP® ERP listener. This issue occurs while deploying a project having SAP® ERP listener notifications.
When you deploy a project containing SAP® ERP listener notifications, the deploy wizard provides you with an option to either create a new listener or select an existing listener. This listener is associated with the listener notification being deployed.
When you select a listener from the dropdown list, which is in disabled mode or enable pending mode, the listener notification deployment fails with an error related to enabling the listener. If you continue with the deployment even after the error, An error occurred while processing your request. Contact support. error message appears.
Workaround: Always select an enabled listener while deploying a project having SAP® ERP listener notifications.

WSP-1573
Unable to edit imported action with created account.
An account name is associated with each SAP® ERP action. If the account with associated account name is not enabled in the project, the SAP® ERP action cannot be edited.
When an export/import function is used, the SAP® ERP action in the target project contains the associated account name.
However, the SAP® ERP account is not created in the target project.
Workaround: To edit the SAP® ERP action in the target project, do the following:
- If an SAP® ERP account with an associated account name exists in the target project, enable the SAP® ERP account in the target project and disable it in all other projects.
- If an SAP® ERP account with an associated account name does not exist in the target project, create and enable the SAP® ERP account in the target project.

FLOW-2575
In a transform pipeline, when both direct mappings and prediction mappings are present and you try to scroll the pipelineInput or pipelineOutput panel, the mapping lines are broken.
Workaround: Collapse and expand the direct mappings. The mapping lines will be repainted properly. This issue exists only when the scroll bar exists and you scroll either horizontally or vertically.

FLOW-2215
The icon position for adding a new Flow service step is not proper when the Expand All and the Collapse All buttons are used.
Workaround: Toggle the expanded state of the step on which the icon appears. This corrects the icon position when adding a new step.

BIC-8481
Users are unable to update the custom time field under the Monitor tab with a simple click in Firefox browser.
Workaround: In Firefox, users can clear the time field value they want to update and re-enter the required value. Alternatively they can use any other browser to update the custom time field value with a simple click.

JDB-2977
In the Database application, updating an Update operation leads to incorrect output.
Workaround: Once you add or delete the table columns or data fields, verify the input/output names and update the proper input/output names if they are not correct.

BIC-5324
After logging out from IBM webMethods iPaaS, when a user logs in again using a different username and then navigates to IBM webMethods Integration using the App Switcher, the user sees that the earlier user’s session has still not been logged out.
Workaround: Log out from IBM webMethods Integration, instead of from IBM webMethods iPaaS.

JDB-3112
Editing an imported workflow or Flow service having database application operations displays an error.
When a workflow or a Flow service is exported using the IBM webMethods Integration export functionality, the connection name is not saved in the exported workflow or Flow service. On editing the database operation in the imported workflow or Flow service, the connection associated with the action is not found.
Workaround: The imported workflow or Flow service having database operations can be executed with a valid connection.

JDB-3106
The SQL query in CustomSQL is parsed by the system using a third-party SQL query parser (FoundationDB SQL Parser) to populate the input and output. When the SQL query parser is unable to parse, the error Failed to fetch Database Metadata appears.
Workaround: If the input and output for CustomSQL operation is not populated, ignore the error and configure the input and output explicitly.

Flow-4355
Ensure that you provide correct values for the input fields in the Set Value or Run dialog boxes when running a Flow service. This is because the input values are not validated according to their data types by the system and you may encounter errors.

Fixes

This section provides information on the fixes for IBM webMethods Integration v10.16.

Release 10.16.5

Issue ID	Release Date	Region	Description
WFL-4338	December 12, 2023 December 12, 2023 December 12, 2023	EU3 West Azure US2 East Azure AU1 Australia East Azure	When users try to bulk restart workflows, sometimes they receive Missing subdomain in context parameters error. Code changes have been made to ensure that bulk restart operations work smoothly.
WF-31390	December 12, 2023 December 12, 2023 December 12, 2023	EU3 West Azure US2 East Azure AU1 Australia East Azure	Free Forever Edition tenants created after December 12, 2023, will no longer have access to the Notification - Send an Email connector. Such tenants must be upgraded to one of the paid plans to access this connector.
WFL-3764	October 5, 2023 October 7, 2023 October 14, 2023 October 28, 2023 November 04, 2023 November 05, 2023	AU2 Sydney AWS EU2 Frankfurt AWS US1 Oregon AWS US2 East Azure AU1 Australia East Azure EU3 West Azure	A user is unable to select the services that are available in Cloud Container, in the IBM webMethods Cloud Container connector.
WFL-3858	October 5, 2023 October 7, 2023 October 14, 2023 October 28, 2023 November 04, 2023 November 05, 2023	AU2 Sydney AWS EU2 Frankfurt AWS US1 Oregon AWS US2 East Azure AU1 Australia East Azure EU3 West Azure	When a user sends some data with a request and the execution fails, and later tries to do a bulk restart of the failed executions, the request data is not picked up during execution.
WFL-3900	October 5, 2023 October 7, 2023 October 14, 2023 October 28, 2023 November 04, 2023 November 05, 2023	AU2 Sydney AWS EU2 Frankfurt AWS US1 Oregon AWS US2 East Azure AU1 Australia East Azure EU3 West Azure	The custom icon for a defined REST connector is not displaying correctly.
WFL-3796	October 5, 2023 October 7, 2023 October 14, 2023 October 28, 2023 November 04, 2023 November 05, 2023	AU2 Sydney AWS EU2 Frankfurt AWS US1 Oregon AWS US2 East Azure AU1 Australia East Azure EU3 West Azure	When users invoke a webhook or REST API with a large compressed payload (~7MB), the following error appears: request entity too large .
FLOW-5117	October 5, 2023 October 7, 2023 October 14, 2023 October 28, 2023 November 04, 2023 November 05, 2023	AU2 Sydney AWS EU2 Frankfurt AWS US1 Oregon AWS US2 East Azure AU1 Australia East Azure EU3 West Azure	The issue revolves around the visibility of spaces when they are used in mapset. With this fix, the visibility of spaces in mapset will ideally remain consistent for more clarity.
FLOW-5002	October 5, 2023 October 7, 2023 October 14, 2023 October 28, 2023 November 04, 2023 November 05, 2023	AU2 Sydney AWS EU2 Frankfurt AWS US1 Oregon AWS US2 East Azure AU1 Australia East Azure EU3 West Azure	Input and output validations are not functioning correctly when validating the content value of a field. This has now been addressed, ensuring that the validation constraints are consistently applied.
FLOW-4963	October 5, 2023 October 7, 2023 October 14, 2023 October 28, 2023 November 04, 2023 November 05, 2023	AU2 Sydney AWS EU2 Frankfurt AWS US1 Oregon AWS US2 East Azure AU1 Australia East Azure EU3 West Azure	The problem was related to the Flow service scheduler for recurrent runs. With this fix, you can now provide a future time for recurrent run execution.
FLOW-5050	October 5, 2023 October 7, 2023 October 14, 2023 October 28, 2023 November 04, 2023 November 05, 2023	AU2 Sydney AWS EU2 Frankfurt AWS US1 Oregon AWS US2 East Azure AU1 Australia East Azure EU3 West Azure	The parent-level mapset in the document reference field disappears when a Flow service is deployed, imported, or cloned subsequently. With this fix, you can now deploy, import, or clone Flow services without experiencing the disappearance of the parent-level mapset on document reference fields.
FLOW-5081	October 5, 2023 October 7, 2023 October 14, 2023 October 28, 2023 November 04, 2023 November 05, 2023	AU2 Sydney AWS EU2 Frankfurt AWS US1 Oregon AWS US2 East Azure AU1 Australia East Azure EU3 West Azure	IBM webMethods Integration tenant performance is slow while deploying assets with Flow services containing internal or child Flow services, as they get deployed twice. The logic is now optimized to deploy the internal or child Flow services only once, which improves the publish/deploy performance.
FLOW-5048	October 5, 2023 October 7, 2023 October 14, 2023 October 28, 2023 November 04, 2023 November 05, 2023	AU2 Sydney AWS EU2 Frankfurt AWS US1 Oregon AWS US2 East Azure AU1 Australia East Azure EU3 West Azure	With this fix, you can now delete any referenced/dependent doctype. This fix provides greater flexibility when dealing with evolving XSDs. This enhancement simplifies the management of documents generated from the same XSD source.
BIC-21088	October 5, 2023 October 7, 2023 October 14, 2023 October 28, 2023 November 04, 2023 November 05, 2023	AU2 Sydney AWS EU2 Frankfurt AWS US1 Oregon AWS US2 East Azure AU1 Australia East Azure EU3 West Azure	In a few cases, during the process of publishing, deploying, or exporting/importing SOAP APIs from a source tenant to a target tenant, the port type and namespace details are changed to the target tenant's information. To address this problem, the port bindings are preserved, ensuring that they remain consistent with those of the source tenant, and the target namespace is updated to match the target URL. ✅ Customer Action Required
BIC-22075	October 5, 2023 October 7, 2023 October 14, 2023 October 28, 2023 November 04, 2023 November 05, 2023	AU2 Sydney AWS EU2 Frankfurt AWS US1 Oregon AWS US2 East Azure AU1 Australia East Azure EU3 West Azure	The OData v4.0 connector unexpectedly stops working with the following error message: Details: Auth scheme may not be null.

Release 10.16.4

To address this problem the port bindings are preserved, ensuring they remain consistent with those of the source tenant and the target namespace is updated to match the target URL.

Issue ID	Release Date	Region	Description
WFL-3940	October 09, 2023	US1 Oregon AWS	Wrike bot accounts expire within a few hours after creation. Code changes have been made to ensure the accounts do not expire prematurely.
FLOW-5128 FLOW-5135	September 16, 2023 September 16, 2023 September 23, 2023	AU2 Sydney AWS US1 Oregon AWS EU2 Frankfurt AWS	Post release 10.16.4, users are unable to export or publish some Flow services after modifying them. Code changes have been made to resolve this issue. ✅ Customer Action Required
FLOW-5101	September 15, 2023 September 15, 2023	US1 Oregon AWS EU2 Frankfurt AWS	Slowness observed in /service/importFromZip/reuseAccount API during the deployment of Flow services. Code has been updated to resolve this issue.
BIC-21088	August 26, 2023 September 03, 2023 September 03, 2023	AU2 Sydney AWS EU2 Frankfurt AWS US1 Oregon AWS	In few cases, during the process of publishing, deploying, or exporting/importing SOAP APIs from a source tenant to a target tenant, the port type and namespace details are changed to the target tenant's information. ✅ Customer Action Required
BIC-21026	August 26, 2023 September 03, 2023 September 03, 2023	AU2 Sydney AWS EU2 Frankfurt AWS US1 Oregon AWS	In an instance, issue is seen when the cache Flow service is being invoked inside a Flow service and the main payload values are getting overwritten with some previous value. This is now resolved, and only fields that are mentioned in the output signature of the flow are cached for the provided input.
FLOW-4946 FLOW-4963	August 26, 2023 September 03, 2023 September 03, 2023	AU2 Sydney AWS EU2 Frankfurt AWS US1 Oregon AWS	The update to the Flow service scheduler introduces an important enhancement that addresses the issue related to recurrent runs scheduled with previous times. By allowing only future times for scheduling, the scheduler promotes a seamless workflow experience.

Release 10.16.3

Issue ID	Release Date	Region	Description
PIEAR-2338	September 17, 2023	US2 East Azure	When a SAP® ERP listener is enabled or disabled, then the updated status of the listener in all IBM webMethods Integration instances is not in sync as the GIT push of the updated node is skipped.
BIC-20572	September 17, 2023	US2 East Azure	The Messaging Subscriber persistently subscribes to messages despite being disabled.
BIC-21084	September 17, 2023	US2 East Azure	On the Monitor page, some Flow services still show as running even after the execution is completed. This issue, caused by large audit data, has been resolved.
WFL-3726	September 01, 2023	EU3 West Azure	Key values stored through Flow Store are overwritten due to flow_id overlap after publishing and deploying the workflow. This issue is resolved by isolating keys used in different tenants.
WFL-3121	July 22, 2023 July 29, 2023 August 05, 2023 August 06, 2023 August 19, 2023 August 20, 2023	AU2 Sydney AWS US1 Oregon AWS EU2 Frankfurt AWS US2 East Azure AU1 Australia East Azure EU3 West Azure	When multiple loop actions are used in workflows, sometimes duplicate connection IDs are generated, resulting in unstable workflows.
WFL-3227	July 22, 2023 July 29, 2023 August 05, 2023 August 06, 2023 August 19, 2023 August 26, 2023	AU2 Sydney AWS US1 Oregon AWS EU2 Frankfurt AWS US2 East Azure AU1 Australia East Azure EU3 West Azure	When users click anywhere on screen after session time out, they receive random errors.
PIE-80824	July 22, 2023 July 29, 2023 August 05, 2023 August 06, 2023 August 19, 2023 August 26, 2023	AU2 Sydney AWS US1 Oregon AWS EU2 Frankfurt AWS US2 East Azure AU1 Australia East Azure EU3 West Azure	Beginning with version 10.15, Integration Server performs regular expression pattern matching as described in the java.util.regex.Pattern class. Previously, Integration Server used the Perl 5 compiler and pattern matching when evaluating regular expressions. Using the newly introduced "watt.server.usejavaregex" parameter, the patterm matching can be switched between Java Regex and Perl5. To use Java Regex, set "watt.server.usejavaregex" to true. Default value of this watt property is false, i.e. Perl5 pattern matching is used by default.
CCH-5793	July 22, 2023 July 29, 2023 August 05, 2023 August 06, 2023 August 19, 2023 August 26, 2023	AU2 Sydney AWS US1 Oregon AWS EU2 Frankfurt AWS US2 East Azure AU1 Australia East Azure EU3 West Azure	The OData v4.0 connector unexpectedly stops working with the following error message: Connection xxx is disabled, even though the connection was enabled.
PIE-82407	July 22, 2023 July 29, 2023 August 05, 2023 August 06, 2023 August 19, 2023 August 26, 2023	AU2 Sydney AWS US1 Oregon AWS EU2 Frankfurt AWS US2 East Azure AU1 Australia East Azure EU3 West Azure	The pub.security:decrypt public service throws "The service could not retrieve the secret key. The secretKey parameter is invalid". The pub.security:decrypt service fails to decrypt data if the data is encrypted using external tools like PGP or Fusion keys.
BIC-21378	July 22, 2023 July 29, 2023 August 05, 2023 August 06, 2023 August 19, 2023 August 26, 2023	AU2 Sydney AWS US1 Oregon AWS EU2 Frankfurt AWS US2 East Azure AU1 Australia East Azure EU3 West Azure	In some cases, the IO Scheduler service executes twice at the same time per scheduled occurrence.
BIC-19202	July 22, 2023 July 29, 2023 August 05, 2023 August 06, 2023 August 19, 2023 August 26, 2023	AU2 Sydney AWS US1 Oregon AWS EU2 Frankfurt AWS US2 East Azure AU1 Australia East Azure EU3 West Azure	In some cases, users receive an error message indicating a technical user that is not defined in the tenant.
BIC-21310	July 22, 2023 July 29, 2023 August 05, 2023 August 06, 2023 August 19, 2023 August 26, 2023	AU2 Sydney AWS US1 Oregon AWS EU2 Frankfurt AWS US2 East Azure AU1 Australia East Azure EU3 West Azure	In some cases, an active Flow service scheduler does not trigger at scheduled intervals.
CCH-5520	July 22, 2023 July 29, 2023 August 05, 2023 August 06, 2023 August 19, 2023 August 26, 2023	AU2 Sydney AWS US1 Oregon AWS EU2 Frankfurt AWS US2 East Azure AU1 Australia East Azure EU3 West Azure	In some cases, where a custom connector is connected to Salesforce and the "Retry" option is not enabled, any field validation error results in a specific error message. However, if the "Retry" option is enabled for the same workflow, a different error message is seen.
FLOW-4746 FLOW-4906	July 22, 2023 July 29, 2023 August 05, 2023 August 06, 2023 August 19, 2023 August 26, 2023	AU2 Sydney AWS US1 Oregon AWS EU2 Frankfurt AWS US2 East Azure AU1 Australia East Azure EU3 West Azure	New line characters get trimmed on reopening the pipeline, resulting in the absence of separators between items when using the "makeString" built-in service to create a string separated by new lines.
FLOW-4788	July 22, 2023 July 29, 2023 August 05, 2023 August 06, 2023 August 19, 2023 August 26, 2023	AU2 Sydney AWS US1 Oregon AWS EU2 Frankfurt AWS US2 East Azure AU1 Australia East Azure EU3 West Azure	Users are unable to loop through a document array within another document reference. This issue specifically occurs when the document array is immediately placed as a child of the document reference.
FLOW-4802	July 22, 2023 July 29, 2023 August 05, 2023 August 06, 2023 August 19, 2023 August 26, 2023	AU2 Sydney AWS US1 Oregon AWS EU2 Frankfurt AWS US2 East Azure AU1 Australia East Azure EU3 West Azure	When users perform index mapping along with simple mapping within a document reference, they receive an error.
WFL-3020	July 22, 2023 July 29, 2023 August 05, 2023 August 06, 2023 August 19, 2023 August 26, 2023	AU2 Sydney AWS US1 Oregon AWS EU2 Frankfurt AWS US2 East Azure AU1 Australia East Azure EU3 West Azure	Some triggers execute on old values even after values are updated.
WSP-1528	July 22, 2023 July 29, 2023 August 05, 2023 August 06, 2023 August 19, 2023 August 26, 2023	AU2 Sydney AWS US1 Oregon AWS EU2 Frankfurt AWS US2 East Azure AU1 Australia East Azure EU3 West Azure	Users are unable to use tab-based navigation in the "Add Listener" screen.
WSP-1783	July 22, 2023 July 29, 2023 August 05, 2023 August 06, 2023 August 19, 2023 August 26, 2023	AU2 Sydney AWS US1 Oregon AWS EU2 Frankfurt AWS US2 East Azure AU1 Australia East Azure EU3 West Azure	Some UI components on SAP Create Listener screen are misaligned.
WFL-3066 WFL-3399	July 22, 2023 July 29, 2023 August 05, 2023 August 06, 2023 August 19, 2023 August 26, 2023	AU2 Sydney AWS US1 Oregon AWS EU2 Frankfurt AWS US2 East Azure AU1 Australia East Azure EU3 West Azure	Workflows containing the messaging service trigger do not get invoked on any subsequent update of the associated subscriber.
FLOW-4818	July 22, 2023 July 29, 2023 August 05, 2023 August 06, 2023 August 19, 2023 August 26, 2023	AU2 Sydney AWS US1 Oregon AWS EU2 Frankfurt AWS US2 East Azure AU1 Australia East Azure EU3 West Azure	In some Flow services, the logs of the input variables for 1 MB or 10 MB data do not render correctly in the UI of the execution history. The content appears in a single scrollable line, causing performance issues.
WST-7228	July 22, 2023 July 29, 2023 August 05, 2023 August 06, 2023 August 19, 2023 August 26, 2023	AU2 Sydney AWS US1 Oregon AWS EU2 Frankfurt AWS US2 East Azure AU1 Australia East Azure EU3 West Azure	During a failover scenario, duplicate processing is observed due to multiple package reloads. The inflight transactions are now tracked to filter out duplicates during the reload process to prevent duplicate processing.
WST-7233	July 22, 2023 July 29, 2023 August 05, 2023 August 06, 2023 August 19, 2023 August 26, 2023	AU2 Sydney AWS US1 Oregon AWS EU2 Frankfurt AWS US2 East Azure AU1 Australia East Azure EU3 West Azure	During webMethods Integration Server startup, a few listener event-based flow executions fail with the "No deployed Axis service for this name" error.
FLOW-4364	July 22, 2023 July 29, 2023 August 05, 2023 August 06, 2023 August 19, 2023 August 26, 2023	AU2 Sydney AWS US1 Oregon AWS EU2 Frankfurt AWS US2 East Azure AU1 Australia East Azure EU3 West Azure	With this fix, the platform now intelligently renders only the mappings that are immediately visible to the user, excluding those that are hidden or not in the user's current view.
FLOW-4746	July 22, 2023 July 29, 2023 August 05, 2023 August 06, 2023 August 19, 2023 August 26, 2023	AU2 Sydney AWS US1 Oregon AWS EU2 Frankfurt AWS US2 East Azure AU1 Australia East Azure EU3 West Azure	New line characters were getting trimmed on reopening the pipeline, resulting in the absence of separators between items when using the makeString built-in service to create a string separated by new lines. This issue has now been addressed.
FLOW-4788	July 22, 2023 July 29, 2023 August 05, 2023 August 06, 2023 August 19, 2023 August 26, 2023	AU2 Sydney AWS US1 Oregon AWS EU2 Frankfurt AWS US2 East Azure AU1 Australia East Azure EU3 West Azure	User was unable to loop through a document array within another document reference. This issue specifically occurred when the document array was immediately placed as a child of the document reference. This issue has now been addressed. Users can successfully loop through a document array within another document reference in the aforementioned scenario.
FLOW-4826	July 22, 2023 July 29, 2023 August 05, 2023 August 06, 2023 August 19, 2023 August 26, 2023	AU2 Sydney AWS US1 Oregon AWS EU2 Frankfurt AWS US2 East Azure AU1 Australia East Azure EU3 West Azure	Empty values set in the fields under document are now retained correctly during processing.
FLOW-4906	July 22, 2023 July 29, 2023 August 05, 2023 August 06, 2023 August 19, 2023 August 26, 2023	AU2 Sydney AWS US1 Oregon AWS EU2 Frankfurt AWS US2 East Azure AU1 Australia East Azure EU3 West Azure	New line characters were getting trimmed on reopening the pipeline, resulting in the absence of separators between items when using the "makeString" built-in service to create a string separated by new lines.
FLOW-4917	July 22, 2023 July 29, 2023 August 05, 2023 August 06, 2023 August 19, 2023 August 26, 2023	AU2 Sydney AWS US1 Oregon AWS EU2 Frankfurt AWS US2 East Azure AU1 Australia East Azure EU3 West Azure	With this fix, the platform now actively checks for dependencies and displays a pop-up notification for any dependent assets when working with Flow services.
FLOW-4929	July 22, 2023 July 29, 2023 August 05, 2023 August 06, 2023 August 19, 2023 August 26, 2023	AU2 Sydney AWS US1 Oregon AWS EU2 Frankfurt AWS US2 East Azure AU1 Australia East Azure EU3 West Azure	With this fix, all assets, including the last leaf node, will now be correctly shown in the dependency tree.
FLOW-4934	July 22, 2023 July 29, 2023 August 05, 2023 August 06, 2023 August 19, 2023 August 26, 2023	AU2 Sydney AWS US1 Oregon AWS EU2 Frankfurt AWS US2 East Azure AU1 Australia East Azure EU3 West Azure	The issue is addressed by removing the consistency check for reference data during the export process. This change streamlines the export process, enabling users to reconfigure the reference data as needed in the target environment.
FLOW-4969	July 22, 2023 July 29, 2023 August 05, 2023 August 06, 2023 August 19, 2023 August 26, 2023	AU2 Sydney AWS US1 Oregon AWS EU2 Frankfurt AWS US2 East Azure AU1 Australia East Azure EU3 West Azure	The issue is addressed by showing a loader until the variable name appears.
FLOW-4979	July 22, 2023 July 29, 2023 August 05, 2023 August 06, 2023 August 19, 2023 August 26, 2023	AU2 Sydney AWS US1 Oregon AWS EU2 Frankfurt AWS US2 East Azure AU1 Australia East Azure EU3 West Azure	Improved retention of global variables state.
FLOW-4980	July 22, 2023 July 29, 2023 August 05, 2023 August 06, 2023 August 19, 2023 August 26, 2023	AU2 Sydney AWS US1 Oregon AWS EU2 Frankfurt AWS US2 East Azure AU1 Australia East Azure EU3 West Azure	With this fix, the platform now differentiates between variables by internally utilizing the project ID prefix for expressions.
FLOW-4982	July 22, 2023 July 29, 2023 August 05, 2023 August 06, 2023 August 19, 2023 August 26, 2023	AU2 Sydney AWS US1 Oregon AWS EU2 Frankfurt AWS US2 East Azure AU1 Australia East Azure EU3 West Azure	By using the change detector, the platform now effectively detects the changes.
FLOW-4983	July 22, 2023 July 29, 2023 August 05, 2023 August 06, 2023 August 19, 2023 August 26, 2023	AU2 Sydney AWS US1 Oregon AWS EU2 Frankfurt AWS US2 East Azure AU1 Australia East Azure EU3 West Azure	Improved the logic for handling project variables in IBM webMethods Integration.
FLOW-4984	July 22, 2023 July 29, 2023 August 05, 2023 August 06, 2023 August 19, 2023 August 26, 2023	AU2 Sydney AWS US1 Oregon AWS EU2 Frankfurt AWS US2 East Azure AU1 Australia East Azure EU3 West Azure	Improved styling for normal and nested variables.
FLOW-4987	July 22, 2023 July 29, 2023 August 05, 2023 August 06, 2023 August 19, 2023 August 26, 2023	AU2 Sydney AWS US1 Oregon AWS EU2 Frankfurt AWS US2 East Azure AU1 Australia East Azure EU3 West Azure	With this fix, the platform now handles the null exception appropriately, preventing it from causing any disruptions during the export process.
FLOW-4911	July 22, 2023 July 29, 2023 August 05, 2023 August 06, 2023 August 19, 2023 August 26, 2023	AU2 Sydney AWS US1 Oregon AWS EU2 Frankfurt AWS US2 East Azure AU1 Australia East Azure EU3 West Azure	With this fix, the platform now correctly saves and retains the configured lookup transformers, preserving the desired functionality.
FLOW-4912	July 22, 2023 July 29, 2023 August 05, 2023 August 06, 2023 August 19, 2023 August 26, 2023	AU2 Sydney AWS US1 Oregon AWS EU2 Frankfurt AWS US2 East Azure AU1 Australia East Azure EU3 West Azure	With this fix, the mapsets associated with Project Services are correctly displayed, enabling easy configuration and utilization of the mapsets within the flow.
FLOW-4935	July 22, 2023 July 29, 2023 August 05, 2023 August 06, 2023 August 19, 2023 August 26, 2023	AU2 Sydney AWS US1 Oregon AWS EU2 Frankfurt AWS US2 East Azure AU1 Australia East Azure EU3 West Azure	With this fix, the platform now accurately presents all the relevant business data associated with executed processes.
FLOW-4964	July 22, 2023 July 29, 2023 August 05, 2023 August 06, 2023 August 19, 2023 August 26, 2023	AU2 Sydney AWS US1 Oregon AWS EU2 Frankfurt AWS US2 East Azure AU1 Australia East Azure EU3 West Azure	XML tags used as mapset values are now retained, safeguarding the structure and integrity of the data.
FLOW-4992	July 22, 2023 July 29, 2023 August 05, 2023 August 06, 2023 August 19, 2023 August 26, 2023	AU2 Sydney AWS US1 Oregon AWS EU2 Frankfurt AWS US2 East Azure AU1 Australia East Azure EU3 West Azure	With this fix, the pipeline variables associated with the mapset created in the transform step are no longer disappearing upon reopening the pipeline flow.
FLOW-4962 FLOW-4860	July 22, 2023 July 29, 2023 August 05, 2023 August 06, 2023 August 19, 2023 August 26, 2023	AU2 Sydney AWS US1 Oregon AWS EU2 Frankfurt AWS US2 East Azure AU1 Australia East Azure EU3 West Azure	When using Firefox, you may encounter a limitation where copying text in a Flow service is not possible. Workaround: 1. Open a new Firefox browser window. 2. Type about:config in the address bar and press "Enter". 3. In the search bar at the top, enter dom.events.testing.asyncClipboard to locate the specific configuration setting. 4. Double-click on the dom.events.testing.asyncClipboard entry to modify its value. 5. Set the value to true. 6. Close the about:config tab and return to the Flow service interface. You should now be able to successfully copy text in the Flow service.
FLOW-5016	July 22, 2023 July 29, 2023 August 05, 2023 August 06, 2023 August 19, 2023 August 26, 2023	AU2 Sydney AWS US1 Oregon AWS EU2 Frankfurt AWS US2 East Azure AU1 Australia East Azure EU3 West Azure	With this fix, the issue of unexpected value resets has been completely resolved within the context of saving data in documents and document arrays.

Release 10.16.1

Issue ID	Release Date	Region	Description
WFL-3288	July 6, 2023	EU2 Frankfurt AWS	While redeploying a project, 502 Bad Gateway error is occasionally observed.
WFL-3333	July 6, 2023	EU2 Frankfurt AWS	In some workflows, the data mapping line between workflow connectors is not visible.
WFL-3020	July 3, 2023 July 3, 2023 July 3, 2023 June 20, 2023 June 22, 2023 June 23, 2023	AU2 Sydney AWS US2 East Azure AU1 Australia East Azure EU2 Frankfurt AWS US1 Oregon AWS EU3 West Azure	When you update a trigger and execute the workflow, the old trigger inputs are considered instead of the updated ones.
WFL-3210	July 3, 2023 July 3, 2023 July 3, 2023 June 20, 2023 June 22, 2023 June 23, 2023	AU2 Sydney AWS US2 East Azure AU1 Australia East Azure EU2 Frankfurt AWS US1 Oregon AWS EU3 West Azure	When users try to redeploy a project containing a Flow service that uses OAuth accounts to another environment, the deployment gets stuck.
CCH-5334	July 3, 2023 July 3, 2023 July 3, 2023 June 20, 2023 June 22, 2023 June 23, 2023	AU2 Sydney AWS US2 East Azure AU1 Australia East Azure EU2 Frankfurt AWS US1 Oregon AWS EU3 West Azure	When the AMQP listener queue is deleted, the trigger disconnects from the workflow, and some trigger events are missed.
BIC-20570 BIC-20790	May 17, 2023 May 27, 2023 May 28, 2023 June 03, 2023 June 04, 2023 June 10, 2023	AU2 Sydney AWS US1 Oregon AWS US2 East Azure EU3 West Azure AU1 Australia East Azure EU2 Frankfurt AWS	Few of the scheduled jobs are taking more time to finish due to which other jobs are getting blocked. This led to skipped execution and scheduler not picking them. This issue is resolved to parallelly execute all the scheduled tasks.
CCH-5510	May 17, 2023 May 27, 2023 May 28, 2023 June 03, 2023 June 04, 2023 June 10, 2023	AU2 Sydney AWS US1 Oregon AWS US2 East Azure EU3 West Azure AU1 Australia East Azure EU2 Frankfurt AWS	Workflows are not triggered as per the scheduled time in Clock trigger.
FLOW-4816	May 17, 2023 May 27, 2023 May 28, 2023 June 03, 2023 June 04, 2023 June 10, 2023	AU2 Sydney AWS US1 Oregon AWS US2 East Azure EU3 West Azure AU1 Australia East Azure EU2 Frankfurt AWS	Set values for picklist fields inside a document array are not retained after reopening the pipeline view.
FLOW-4817	May 17, 2023 May 27, 2023 May 28, 2023 June 03, 2023 June 04, 2023 June 10, 2023	AU2 Sydney AWS US1 Oregon AWS US2 East Azure EU3 West Azure AU1 Australia East Azure EU2 Frankfurt AWS	Dropdown field options are not visible under Flow services.
FLOW-4849	May 17, 2023 May 27, 2023 May 28, 2023 June 03, 2023 June 04, 2023 June 10, 2023	AU2 Sydney AWS US1 Oregon AWS US2 East Azure EU3 West Azure AU1 Australia East Azure EU2 Frankfurt AWS	In Flow services, values set for document list fields inside document reference are getting removed automatically. Workaround: You can add a separate step with pipeline document array field then map that to the respective document array.
WFL-2637	May 17, 2023 May 27, 2023 May 28, 2023 June 03, 2023 June 04, 2023 June 10, 2023	AU2 Sydney AWS US1 Oregon AWS US2 East Azure EU3 West Azure AU1 Australia East Azure EU2 Frankfurt AWS	When users click on a dashboard link on the Monitor page and remove one of the projects from filters, the result still fetches records for the removed project.
WFL-2837	May 17, 2023 May 27, 2023 May 28, 2023 June 03, 2023 June 04, 2023 June 10, 2023	AU2 Sydney AWS US1 Oregon AWS US2 East Azure EU3 West Azure AU1 Australia East Azure EU2 Frankfurt AWS	Some scheduled workflow executions are not processed as per the scheduled time.
WFL-2864	May 17, 2023 May 27, 2023 May 28, 2023 June 03, 2023 June 04, 2023 June 10, 2023	AU2 Sydney AWS US1 Oregon AWS US2 East Azure EU3 West Azure AU1 Australia East Azure EU2 Frankfurt AWS	Updates made to a workflow are reflected after some delay.
WST-7080	May 17, 2023 May 27, 2023 May 28, 2023 June 03, 2023 June 04, 2023 June 10, 2023	AU2 Sydney AWS US1 Oregon AWS US2 East Azure EU3 West Azure AU1 Australia East Azure EU2 Frankfurt AWS	Rest connector accounts are not getting listed in the projects and the respective Flow services are displaying a red dot indicating a missing account.
WFL-2766	May 17, 2023 May 27, 2023 May 28, 2023 June 03, 2023 June 04, 2023 June 10, 2023	AU2 Sydney AWS US1 Oregon AWS US2 East Azure EU3 West Azure AU1 Australia East Azure EU2 Frankfurt AWS	Few workflows were stuck in the running state.
CCH-5383	May 17, 2023 May 27, 2023 May 28, 2023 June 03, 2023 June 04, 2023 June 10, 2023	AU2 Sydney AWS US1 Oregon AWS US2 East Azure EU3 West Azure AU1 Australia East Azure EU2 Frankfurt AWS	Extra executions are observed even if one execution is scheduled per day for some workflows. This is because the trigger poller was picking up the same clock trigger for execution, causing multiple executions.
CCH-5223	May 17, 2023 May 27, 2023 May 28, 2023 June 03, 2023 June 04, 2023 June 10, 2023	AU2 Sydney AWS US1 Oregon AWS US2 East Azure EU3 West Azure AU1 Australia East Azure EU2 Frankfurt AWS	input.connection.query is not a function error observed while connecting to a database due to which requests were failing. This was because there were too many connections open with the MYSQL server.
BIC-20497	May 17, 2023 May 27, 2023 May 28, 2023 June 03, 2023 June 04, 2023 June 10, 2023	AU2 Sydney AWS US1 Oregon AWS US2 East Azure EU3 West Azure AU1 Australia East Azure EU2 Frankfurt AWS	Few seconds latency observed between IBM webMethods API Gateway and IBM webMethods Integration.
WFL-2607	May 17, 2023 May 27, 2023 May 28, 2023 June 03, 2023 June 04, 2023 June 10, 2023	AU2 Sydney AWS US1 Oregon AWS US2 East Azure EU3 West Azure AU1 Australia East Azure EU2 Frankfurt AWS	Some workflows time out intermittently due to cache service disconnection.
WFL-2551 WFL-2176	May 17, 2023 May 27, 2023 May 28, 2023 June 03, 2023 June 04, 2023 June 10, 2023	AU2 Sydney AWS US1 Oregon AWS US2 East Azure EU3 West Azure AU1 Australia East Azure EU2 Frankfurt AWS	Some workflows stay in Running status. Click the Stop button on the workflow canvas to manually terminate the workflow execution.
WFL-2475	May 17, 2023 May 27, 2023 May 28, 2023 June 03, 2023 June 04, 2023 June 10, 2023	AU2 Sydney AWS US1 Oregon AWS US2 East Azure EU3 West Azure AU1 Australia East Azure EU2 Frankfurt AWS	When users try to manually stop workflow execution, the workflow fails.
WFL-2464 WFL-2462 WFL-2758 WFL-2821 WFL-2860 WFL-2944 WFL-2986	May 17, 2023 May 27, 2023 May 28, 2023 June 03, 2023 June 04, 2023 June 10, 2023	AU2 Sydney AWS US1 Oregon AWS US2 East Azure EU3 West Azure AU1 Australia East Azure EU2 Frankfurt AWS	When users try to test actions having large data, the test operation fails as the response format is String instead of JSON. The response format is now changed to JSON.
WFL-2461	May 17, 2023 May 27, 2023 May 28, 2023 June 03, 2023 June 04, 2023 June 10, 2023	AU2 Sydney AWS US1 Oregon AWS US2 East Azure EU3 West Azure AU1 Australia East Azure EU2 Frankfurt AWS	Some users with custom role are unable to delete workflows from projects to which they have access.
FLOW-4740	May 17, 2023 May 27, 2023 May 28, 2023 June 03, 2023 June 04, 2023 June 10, 2023	AU2 Sydney AWS US1 Oregon AWS US2 East Azure EU3 West Azure AU1 Australia East Azure EU2 Frankfurt AWS	Loss of B2B EDI Document Types observed during cloning to a new project. Previously, when cloning to a new project, some B2B EDI Document Types that were present at the tenant level were lost. To address this issue, changes are done to the cloning process to ensure that B2B EDI Document Types are not lost during the cloning process. You can now clone projects without the risk of losing important B2B EDI Document Types.
FLOW-4728	May 17, 2023 May 27, 2023 May 28, 2023 June 03, 2023 June 04, 2023 June 10, 2023	AU2 Sydney AWS US1 Oregon AWS US2 East Azure EU3 West Azure AU1 Australia East Azure EU2 Frankfurt AWS	When saving a Document Type, validation occurs through the REST API endpoint /rest/documenttype/xsd/validate?projectName=. As part of this process, IBM webMethods Integration expects the username and password to be included in the auth attribute. The issue is now resolved. You will no longer experience authentication errors when validating Document Types.
FLOW-4671	May 17, 2023 May 27, 2023 May 28, 2023 June 03, 2023 June 04, 2023 June 10, 2023	AU2 Sydney AWS US1 Oregon AWS US2 East Azure EU3 West Azure AU1 Australia East Azure EU2 Frankfurt AWS	When users go to Configurations > Flow services > Reference data and try to fetch the reference data, the results take longer than usual to appear.
FLOW-4633	May 17, 2023 May 27, 2023 May 28, 2023 June 03, 2023 June 04, 2023 June 10, 2023	AU2 Sydney AWS US1 Oregon AWS US2 East Azure EU3 West Azure AU1 Australia East Azure EU2 Frankfurt AWS	The Include empty values for string types option is used to include or exclude empty string values when providing input values. This option is available in the Debug and Run pages but not when scheduling integrations using the Schedule page. This option is now added to the Schedule page as well, allowing you to include empty string values when scheduling integrations.

Release 10.16.0

Issue ID	Release Date	Region	Description
FLOW-4744	April 24, 2023	US2 East Azure	Set values for picklist fields inside a document array were not retained after reopening the pipeline view. This issue is resolved.
BOC-18139	April 15, 2023 April 30, 2023	EU2 Frankfurt AWS US1 Oregon AWS	An error Connection field is not available for field key accountName occurs when editing account configuration in AS2 Connector. This issue is resolved. ✅ Customer Action Required
FLOW-4725 FLOW-4652 FLOW-4666 FLOW-4700	April 15, 2023 April 30, 2023	EU2 Frankfurt AWS US1 Oregon AWS	When you disable and enable a transform pipeline step with mapsets and debug it, the response shows XML nodes. This issue is resolved.
FLOW-4727	April 15, 2023 April 30, 2023	EU2 Frankfurt AWS US1 Oregon AWS	The parseContent service under B2B connector when invoked through a Flow service, does not work as expected.
FLOW-4645	April 15, 2023 April 30, 2023	EU2 Frankfurt AWS US1 Oregon AWS	When users enter hardcoded values for mapping in a Flow service, save it, and go back to the Flow service UI, the hardcoded values disappear.
CCH-5019 CCH-4856	April 15, 2023 April 18, 2023	EU2 Frankfurt AWS US1 Oregon AWS	For workflows containing SFTP connectors, some users receive No SFTP connection available and sftp.put is not a function errors intermittently. ✅ Customer Action Required
FLOW-4725	April 15, 2023 April 30, 2023	EU2 Frankfurt AWS US1 Oregon AWS	When you disable and enable a transform pipeline step with mapsets and debug it, the response shows XML nodes.
FLOW-4727	April 15, 2023 April 30, 2023	EU2 Frankfurt AWS US1 Oregon AWS	The parseContent service under B2B connector when invoked through a Flow service, does not work as expected.
FLOW-4652 FLOW-4666 FLOW-4700	April 15, 2023 April 30, 2023	EU2 Frankfurt AWS US1 Oregon AWS	When you disable and enable a transform pipeline step with mapsets and debug it, the response shows XML nodes.
CCH-5233	April 15, 2023 April 30, 2023	EU2 Frankfurt AWS US1 Oregon AWS	Some SFTP servers were not capable of handling chunking and concurrent options. The download action of SFTP connectors is now updated to the V6 version to resolve this issue. With this change, different types of methods provided by the SFTP library are available.
FLOW-4626	April 15, 2023 April 30, 2023	EU2 Frankfurt AWS US1 Oregon AWS	In some Flow services, hardcoded values were not getting assigned to the variables in the output. To resolve this issue, add a blank step at the end of the Flow service without modifying any business logic and then save the Flow service. This will ensure that the Flow service works as expected.
WFL-1699	April 15, 2023 April 30, 2023	EU2 Frankfurt AWS US1 Oregon AWS	Transactions were stuck in the Running state. This issue is resolved for all use cases except outage scenarios like crash and connection lost to reduce the occurrence of running workflows.
BIC-18913	April 15, 2023 April 30, 2023	EU2 Frankfurt AWS US1 Oregon AWS	SFTP connector shows incorrect error message (Account does not exist - SFTP user alias DBSchenkerConnection does not exist- Error) when a connection times out or a different host key is present. Now when a connection times out or a different host key is present, relevant error message appears.
BIC-19201	April 15, 2023 April 30, 2023	EU2 Frankfurt AWS US1 Oregon AWS	When a workflow fails, the $stage key—which is internal to the system—is displayed in the error response. The $stage key is now removed from the error response.
BIC-19263	April 15, 2023 April 30, 2023	EU2 Frankfurt AWS US1 Oregon AWS	Errors observed while sending a 2-way handshake HTTP request even after passing signed certificates in the trust store and key store.
FLOW-4185	April 15, 2023 April 30, 2023	EU2 Frankfurt AWS US1 Oregon AWS	While initializing variables with special characters (for example, () or []) within a document array, additional double quotes (") are appended at the start and end of the JSON variable name.
FLOW-4390	April 15, 2023 April 30, 2023	EU2 Frankfurt AWS US1 Oregon AWS	When If-Else condition is applied on the output of Reference Data action in a Flow service with null check, and it returns an empty document array (shown as null in the UI), the null check fails. UI changes are now made to display the document array as empty array ([]) instead of null.
FLOW-4585	April 15, 2023 April 30, 2023	EU2 Frankfurt AWS US1 Oregon AWS	An empty string does not work for $null or $default. A new option emptyString is added in the Case statement and a new option Isempty is added in Expression Editor to verify if the input string is empty.
WFL-1564	April 15, 2023 April 30, 2023	EU2 Frankfurt AWS US1 Oregon AWS	For some users, the default branch in a Switch statement does not show correct configurations.
WFL-1604	April 15, 2023 April 30, 2023	EU2 Frankfurt AWS US1 Oregon AWS	Some workflow executions are not initiated due to internal system errors.
WFL-1742 WFL-2123	April 15, 2023 April 30, 2023	EU2 Frankfurt AWS US1 Oregon AWS	Some workflow executions time out due to internal system errors.
WFL-1756	April 15, 2023 April 30, 2023	EU2 Frankfurt AWS US1 Oregon AWS	For some tenants, users with owner permissions are unable to delete other users through the User Management screen.
WFL-1757 WFL-2177	April 15, 2023 April 30, 2023	EU2 Frankfurt AWS US1 Oregon AWS	In some cases, execution logs are not displayed for the failed or timed out workflows even if users have selected the option to view logs.
WFL-1840	April 15, 2023 April 30, 2023	EU2 Frankfurt AWS US1 Oregon AWS	The values stored in Flow Store are shared across all environments without a tenant-level differentiation. A new key tenant_uid is also passed to fetch correct data during deployment.
WFL-2088	April 15, 2023 April 30, 2023	EU2 Frankfurt AWS US1 Oregon AWS	Some scheduled workflows go into pending state and are delayed for execution.
WFL-2165 WFL-2178	April 15, 2023 April 30, 2023	EU2 Frankfurt AWS US1 Oregon AWS	Some workflows time out intermittently.
WST-6937	April 15, 2023 April 30, 2023	EU2 Frankfurt AWS US1 Oregon AWS	Some Salesforce listener linked workflows are executed twice for a single Salesforce platform event.
CCH-4856 CCH-5094	April 15, 2023 April 30, 2023	EU2 Frankfurt AWS US1 Oregon AWS	For workflows containing SFTP connectors, some users receive sftp.list is not a function and sftp.put is not a function errors intermittently.
FLOW-4437	April 15, 2023 April 30, 2023	EU2 Frankfurt AWS US1 Oregon AWS	In Flow services, Document Reference Array list gets converted to a string variable after initializing it with the transform action and then reopening the Flow service.
WFL-1418	April 15, 2023 April 30, 2023	EU2 Frankfurt AWS US1 Oregon AWS	Executions for large workflows containing loops sometimes fail.
WST-6720	April 15, 2023 April 30, 2023	EU2 Frankfurt AWS US1 Oregon AWS	Salesforce connector update failed with the error message: ERROR_INVOKING_CLOUD_SERVICE: Unable to process CloudStreams response message, details: No response code and method mapping found for connector.
WFL-2123	April 15, 2023 April 30, 2023	EU2 Frankfurt AWS US1 Oregon AWS	For some tenants, updates to the Salesforce connector fails.
PIE-78669 PIE-80526	April 15, 2023 April 30, 2023	EU2 Frankfurt AWS US1 Oregon AWS	For some connectors, authentication fails because the password retrieval incorrectly uses global password managers instead of package-level password managers.
WFL-1730	April 15, 2023 April 30, 2023	EU2 Frankfurt AWS US1 Oregon AWS	When a workflow contains a messaging trigger and you deploy it from one tenant to another, sometimes the connector account configurations disappear from the destination tenant deployment.
WFL-2593	April 11, 2023	EU3 West Azure	Stopped, Failed, and Timeout Workflow execution logs displayed incorrect end time, duration, and elapsed time. Workflow execution logs no longer display the end time, duration, and elapsed time in the Workflow execution details. Now, hyphen appears in those columns to indicate blank. However, the duration is displayed in the Executions table.
WF-28476	April 11, 2023	EU3 West Azure	The maximum execution runtime limit has been increased to 6 minutes for sync workflows and 90 minutes for async workflows. Earlier, the maximum execution runtime limit for sync and async workflows was 3 minutes and 30 minutes respectively.
BOC-18139	March 30, 2023 March 30, 2023 March 28, 2023	EU3 West Azure US2 East Azure AU2 Sydney AWS	An error Connection field is not available for field key accountName occurs when editing account configuration in AS2 Connector. ✅ Customer Action Required
FLOW-4725 FLOW-4652 FLOW-4666 FLOW-4700	March 24, 2023 March 29, 2023	AU1 Australia East Azure US2 East Azure	When you disable and enable a transform pipeline step with mapsets and debug it, the response shows XML nodes.
FLOW-4727	March 24, 2023 March 29, 2023	AU1 Australia East Azure US2 East Azure	The parseContent service under B2B connector when invoked through a Flow service, does not work as expected.
FLOW-4645	March 24, 2023 March 29, 2023	AU1 Australia East Azure US2 East Azure	When users enter hardcoded values for mapping in a Flow service, save it, and go back to the Flow service UI, the hardcoded values disappear.
CCH-5019 CCH-4856	March 24, 2023 March 29, 2023	AU1 Australia East Azure US2 East Azure	For workflows containing SFTP connectors, some users receive No SFTP connection available and sftp.put is not a function errors intermittently. ✅ Customer Action Required
FLOW-4725	March 23, 2023	EU3 West Azure	When you disable and enable a transform pipeline step with mapsets and debug it, the response shows XML nodes.
FLOW-4727	March 23, 2023	EU3 West Azure	The parseContent service under B2B connector when invoked through a Flow service, does not work as expected.
FLOW-4652 FLOW-4666 FLOW-4700	March 15, 2023	EU3 West Azure	When you disable and enable a transform pipeline step with mapsets and debug it, the response shows XML nodes.
FLOW-4645	March 15, 2023	EU3 West Azure	When users enter hardcoded values for mapping in a Flow service, save it, and go back to the Flow service UI, the hardcoded values disappear.
CCH-5019 CCH-4856	March 13, 2023	EU3 West Azure	For workflows containing SFTP connectors, some users receive No SFTP connection available and sftp.put is not a function errors intermittently. ✅ Customer Action Required
CCH-5233	February 17, 2023 February 17, 2023 February 17, 2023	AU1 Australia East Azure EU3 West Azure US2 East Azure	Some SFTP servers were not capable of handling chunking and concurrent options. The download action of SFTP connectors is now updated to the V6 version to resolve this issue. With this change, different types of methods provided by the SFTP library are available.
FLOW-4626	February 17, 2023 February 17, 2023 February 17, 2023	AU1 Australia East Azure EU3 West Azure US2 East Azure	In some Flow services, hardcoded values were not getting assigned to the variables in the output. To resolve this issue, add a blank step at the end of the Flow service without modifying any business logic and then save the Flow service. This will ensure that the Flow service works as expected.
WFL-1699	February 17, 2023 February 17, 2023 February 17, 2023	AU1 Australia East Azure EU3 West Azure US2 East Azure	Transactions were stuck in the Running state. This issue is resolved for all use cases except outage scenarios like crash and connection lost to reduce the occurrence of running workflows.
BIC-18913	February 12, 2023 February 12, 2023 February 11, 2023	AU1 Australia East Azure EU3 West Azure US2 East Azure	SFTP connector shows incorrect error message ( Account does not exist - SFTP user alias DBSchenkerConnection does not exist- Error) when a connection times out or a different host key is present. Now when a connection times out or a different host key is present, relevant error message appears.
BIC-19201	February 12, 2023 February 12, 2023 February 11, 2023	AU1 Australia East Azure EU3 West Azure US2 East Azure	When a workflow fails, the $stage key—which is internal to the system—is displayed in the error response. The $stage key is now removed from the error response.
BIC-19263	February 12, 2023 February 12, 2023 February 11, 2023	AU1 Australia East Azure EU3 West Azure US2 East Azure	Errors observed while sending a 2-way handshake HTTP request even after passing signed certificates in the trust store and key store.
FLOW-4185	February 12, 2023 February 12, 2023 February 11, 2023	AU1 Australia East Azure EU3 West Azure US2 East Azure	While initializing variables with special characters (for example, () or []) within a document array, additional double quotes (") are appended at the start and end of the JSON variable name.
FLOW-4390	February 12, 2023 February 12, 2023 February 11, 2023	AU1 Australia East Azure EU3 West Azure US2 East Azure	When If-Else condition is applied on the output of Reference Data action in a Flow service with null check, and it returns an empty document array (shown as null in the UI), the null check fails. UI changes are now made to display the document array as empty array ([]) instead of null.
FLOW-4585	February 12, 2023 February 12, 2023 February 11, 2023	AU1 Australia East Azure EU3 West Azure US2 East Azure	An empty string does not work for $null or $default. A new option emptyString is added in the Case statement and a new option Isempty is added in Expression Editor to verify if the input string is empty.
WFL-1564	February 12, 2023 February 12, 2023 February 11, 2023	AU1 Australia East Azure EU3 West Azure US2 East Azure	For some users, the default branch in a Switch statement does not show correct configurations.
WFL-1604	February 12, 2023 February 12, 2023 February 11, 2023	AU1 Australia East Azure EU3 West Azure US2 East Azure	Some workflow executions are not initiated due to internal system errors.
WFL-1742 WFL-2123	February 12, 2023 February 12, 2023 February 11, 2023	AU1 Australia East Azure EU3 West Azure US2 East Azure	Some workflow executions time out due to internal system errors.
WFL-1756	February 12, 2023 February 12, 2023 February 11, 2023	AU1 Australia East Azure EU3 West Azure US2 East Azure	For some tenants, users with owner permissions are unable to delete other users through the User Management screen.
WFL-1757 WFL-2177	February 12, 2023 February 12, 2023 February 11, 2023	AU1 Australia East Azure EU3 West Azure US2 East Azure	In some cases, execution logs are not displayed for the failed or timed out workflows even if users have selected the option to view logs.
WFL-1840	February 12, 2023 February 12, 2023 February 11, 2023	AU1 Australia East Azure EU3 West Azure US2 East Azure	The values stored in Flow Store are shared across all environments without a tenant-level differentiation. A new key tenant_uid is also passed to fetch correct data during deployment.
WFL-2088	February 12, 2023 February 12, 2023 February 11, 2023	AU1 Australia East Azure EU3 West Azure US2 East Azure	Some scheduled workflows go into pending state and are delayed for execution.
WFL-2165 WFL-2178	February 12, 2023 February 12, 2023 February 11, 2023	AU1 Australia East Azure EU3 West Azure US2 East Azure	Some workflows time out intermittently.
WST-6937	February 12, 2023 February 12, 2023 February 11, 2023	AU1 Australia East Azure EU3 West Azure US2 East Azure	Some Salesforce listener linked workflows are executed twice for a single Salesforce platform event.
CCH-4856 CCH-5094	February 12, 2023 February 12, 2023 February 11, 2023	AU1 Australia East Azure EU3 West Azure US2 East Azure	For workflows containing SFTP connectors, some users receive sftp.list is not a function and sftp.put is not a function errors intermittently.
FLOW-4437	February 12, 2023 February 12, 2023 February 11, 2023	AU1 Australia East Azure EU3 West Azure US2 East Azure	In Flow services, Document Reference Array list gets converted to a string variable after initializing it with the transform action and then reopening the Flow service.
WFL-1418	February 12, 2023 February 12, 2023 February 11, 2023	AU1 Australia East Azure EU3 West Azure US2 East Azure	Executions for large workflows containing loops sometimes fail.
WST-6720	February 12, 2023 February 12, 2023 February 11, 2023	AU1 Australia East Azure EU3 West Azure US2 East Azure	Salesforce connector update failed with the error message: ERROR_INVOKING_CLOUD_SERVICE: Unable to process CloudStreams response message, details: No response code and method mapping found for connector.
WFL-2123	February 12, 2023 February 12, 2023 February 11, 2023	AU1 Australia East Azure EU3 West Azure US2 East Azure	For some tenants, updates to the Salesforce connector fails.
PIE-78669 PIE-80526	February 12, 2023 February 12, 2023 February 11, 2023	AU1 Australia East Azure EU3 West Azure US2 East Azure	For some connectors, authentication fails because the password retrieval incorrectly uses global password managers instead of package-level password managers.
WFL-1730	February 12, 2023 February 12, 2023 February 11, 2023	AU1 Australia East Azure EU3 West Azure US2 East Azure	When a workflow contains a messaging trigger and you deploy it from one tenant to another, sometimes the connector account configurations disappear from the destination tenant deployment.

What's New

Release 10.16.5

Resuming workflow execution

Reorganization of Cloud Messaging

Built-In-Services are updated for Flow services

Changes in Clock Trigger

New and Updated Connectors

Fixes included in the 10.16.5 release

Release 10.16.4

Enhanced security for password-protected project parameters

Support to retain the value of the Invoke Flow service over HTTP option

New and Updated Connectors

Fixes included in the 10.16.4 release

Release 10.16.3

Insights

Enhanced queryTransaction operation to support custom attributes

Auto-generate workflow structures based on user prompts

Restarting workflow execution

Increased transaction limit for Free Forever Edition tenants

Support for storing assets at the user level while publishing projects

Debug panel enhancements

API enhancements

Terminology change

New and updated connectors

Fixes included in the 10.16.3 release

Release 10.16.1

SAP® ERP Lookup

Increased maximum execution runtime limit for sync and async workflows

Introducing suspension and deletion for inactive Free Forever Edition tenants

Transaction Count for Workflow Executions

Flat File Connector Enhancements

Independent options for restart and resume Flow service executions

Copying of existing REST APIs across Projects

Enhancement in Search Methods

Support for Account Interoperability for Coupa in Flow services

Release 10.16.0

Error Management for Salesforce Listeners

Runtime Status of Connector Listeners

Listener Improvements

Information related to Hybrid Connectivity

Size Limit for Hybrid Integration Messages

Hybrid Integration Architecture Improvements

Enhanced rate limits for manually run, trigger-enabled, and async webhook-enabled workflows

Execution Settings Enhancements

New APIs

Monitor Page Enhancements

Monitoring SAP® ERP Performance

Monitoring SAP® ERP Connection Pools

New SAP® ERP Built-In Service

Flow service Enhancements

Support for Caching in Flow services

Support Connectivity with Self-hosted Universal Messaging Servers from JMS connector

Support for Reusing Previous Flow service Configurations and Parameter Values during Redeployment

Support for Multiple Port Bindings in SOAP Connectors

Support for Partner Certificate in SOAP Connectors

Custom Action Enhancements

Label for deprecated triggers

Support for Updating Predefined Connector Account Information

IBM webMethods B2B Connector Enhancements on IBM webMethods Integration

Connector Enhancements

New and Updated Connectors

Tutorials

Customer Actions

Flow Service Export and Publish Update

SOAP APIs Update

AS2 Connector Update

SSL/TLS Certificate Update

SFTP Connector Update

Hybrid Connectivity Update

Hybrid Integration Update

Regular Expression Update

Usage Notes

Known Issues

Fixes

Release 10.16.5

Release 10.16.4

Release 10.16.3

Release 10.16.1

Release 10.16.0

**Support to retain the value of the Invoke Flow service over HTTP option**