Release 10.15
Explore the release highlights, usage notes, known issues, and fixes for IBM webMethods Integration.
Explore the release highlights, usage notes, known issues, and fixes for IBM webMethods Integration.
New features and enhancements | Description |
---|---|
Release 10.15.3 | IBM webMethods B2B Connector Enhancements on IBM webMethods Integration |
Addition of four new operations |
|
Flat file batching for large documents | A new output variable hasMore is added in the convertFlatFileToDocument predefined flat file operation to process large flat file documents in batches. |
Release 10.15.2 | |
Fixes included in the 10.15.2 release | See the Fixes section for information on the 10.15.2 fixes. |
Release 10.15.1 | |
Restart and resume Workflows and Flow services | 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 now restart and resume Workflow and Flow services executions from the main execution listing page. |
Search tenant users on User Management page | You can now search tenant users listed on the User Management page through the newly added search box. You can use the name or email address associated with the user as a keyword. |
setCustomContextID input parameter length | A maximum of 72 characters are now supported for the ID parameter in the setCustomContextID service. In the event that an ID exceeds 72 characters, only the first 72 characters are stored. With this support for lengthy IDs, users can easily correlate the onprem and cloud executions especially for hybrid integrations. Previously, the ID length was limited to 36 characters. |
Fixes included in the 10.15.1 release | See the Fixes section for information on the 10.15.1 fixes. |
Release 10.15.0 | |
OAuth 2.0 authentication for Coupa | Coupa has strengthened its security for all API integrations and require the use of only OAuth 2.0 authentication, for all integrations. You can select this authentication type while adding a custom action in Coupa. The OAuth 2.0 authentication for Coupa requires Scope - assignment which is like a set of permissions set on the API key. You can find the list of scopes and their underlying Coupa permissions by going to the Coupa API Scope management page at /oauth2/scopes. Scopes are available for review on https://{your_instance_address}/oauth2/scopes. For detailed steps on OAuth Client creation and scope assignment in Coupa, see the OAuth 2.0 Transition Guide at the Coupa Success Portal. Click here for information on how to set up a Coupa OAuth 2.0 client and configure a connection. |
OAuth 2.0 authentication for SAP SuccessFactors | OAuth 2.0 authentication is enabled for the SAP SuccessFactors connector to authenticate users in a more secure way. Mandatory fields required to generate the access token to authorize the API requests under the OAuth 2.0 authentication for SAP SuccessFactors are as follows:
|
Custom connector enhancements | In earlier releases, you could import, export, share, clone, and deploy a workflow having a custom connector to another tenant, only if it was first made global. In this release, this restriction is removed. You can now import, export, share, clone, and deploy a workflow having a custom connector to another tenant, without making it global. |
Multiple WSDL files while creating a SOAP API | You can now select one or multiple dependent WSDLs, XSDs, and/or XMLs to the primary WSDL at the same time by clicking Browse file(s) or using the drag and drop functionality. Earlier, you could select only one dependent WSDL, XSD, and/or XML to the primary WSDL at a time. |
Enhancements in Edit Account screen | The following changes are now implemented in the Edit Account screen: In this release, the existing values of the mandatory fields (for example, Client Key) are masked. |
Publish projects across regions | In earlier releases, you could publish projects to different environments, only if they existed in the same region. In this release, this restriction is removed. You can now publish projects to environments existing across different regions. Note: The destination environment must be on the same or higher version than the source environment. If the destination environment is on a lower version than the source environment, an error appears. |
Free Forever subscription | If you now sign up for a IBM webMethods Integration trial tenant, the Free Forever Edition plan is assigned by default, which does not have an expiry. You can optionally upgrade to the Basic, Advanced, or Enterprise paid plan based on your requirements, by contacting IBM Sales. |
New service | The createMessageDigest service has been added in this release in the Utils category, which allows you to generate a message digest for a given message. |
Stability and performance improvements | Event data is now directly stored into the database. |
Support for concurrent message processing | The Messaging feature has been enhanced to process messages received from the Messaging Provider in parallel. That is, a subscriber processes multiple messages at the same time resulting in faster performance than processing in a serial manner. A new tab, Message Processing, has been added in the Subscriber settings screen to configure the subscriber processing mode. Additionally, a new property, Acknowledgement mode, has been added in the General tab of the Subscriber settings screen, which allows users to specify how the subscriber must acknowledge messages received from the Messaging Provider. |
Support for Particular Replay ID in Salesforce Listener | The Salesforce Listener has been enhanced to receive events from Salesforce by providing a specific replay ID. A new screen, Configure listener, has been added allowing users to specify the replay ID while enabling listeners. Users also have an option to replay new or all events by specifying the values -1 and -2 respectively. Earlier, users were able to configure the replay ID only when creating a listener and not when enabling the listener. |
New APIs | New APIs have been introduced in the following domains: |
Tutorials | In this release, new tutorials are added to assist you in understanding the features of IBM webMethods Integration. |
End-to-End Monitoring documentation | End-to-End Monitoring documentation is now independent of IBM webMethods Integration documentation for better visibility and ease of access. |
New and updated Connectors | Explore new and updated connectors released recently in IBM webMethods Integration. |
Creating new document types | Create new SAP® ERP document types from an SAP RFC structure, or a SAP IDoc that matches the structure of the document and content of the SAP RFC structure, or SAP IDoc respectively. |
Asset support matrix | View the list of functions supported for various assets in the current version of IBM webMethods Integration. |
Support for pre-bundled driver groups | Three new pre-bundled driver groups are now supported in IBM webMethods Integration:
|
Support to deploy connector builder connectors to data centers | You can now deploy custom connector builder connectors to different tenants within the same data centers or across data centers. |
This section provides information on the fixes for IBM webMethods Integration.
Version | Issue ID | Release Date | Region | Description |
---|---|---|---|---|
10.15.2 | KUB-18604 |
January 12, 2023 January 12, 2023 January 12, 2023 January 13, 2023 January 13, 2023 January 13, 2023 |
AU1 Australia East Azure EU3 West Azure US2 East Azure AU2 Sydney AWS EU2 Frankfurt AWS US1 Oregon AWS |
REST API returns 401 unauthorized error while supplying the X-Forwarded-Host header. Note that IBM webMethods Integration does not honor the X-Forwarded-Host header and its value will be ignored. |
10.15.1 | WFL-1391 WFL-1671 WFL-1673 |
December 21, 2022 |
AU1 Australia East Azure |
Some workflows time out before execution initiation without any execution logs. Changes are made to resolve this issue. |
10.15.1 | WFL-100 WFL-992 |
December 14, 2022 | AU1 Australia East Azure EU3 West Azure US2 East Azure AU2 Sydney AWS EU2 Frankfurt AWS US1 Oregon AWS |
While passing the token value through webhook payload and mapping it to the dynamic account token value to allow the REST connector use the token, the value shown is, $request.headers.token. |
10.15.1 | WFL-1225 | December 14, 2022 | AU1 Australia East Azure EU3 West Azure US2 East Azure AU2 Sydney AWS EU2 Frankfurt AWS US1 Oregon AWS |
FTP, SFTP, and MySQL connectors were failing on BIGINT enabled tenants. Changes are made to resolve this issue. |
10.15.1 | BIC-17993 FLOW-4304 |
December 3, 2022 December 4, 2022 December 4, 2022 December 11, 2022 December 10, 2022 December 11, 2022 |
US2 East Azure EU3 West Azure AU1 Australia East Azure EU2 Frankfurt AWS AU2 Sydney AWS US1 Oregon AWS |
Environment slowness observed during deployments. |
10.15.1 | FLOW-4209 | December 3, 2022 December 4, 2022 December 4, 2022 December 11, 2022 December 10, 2022 December 11, 2022 |
US2 East Azure EU3 West Azure AU1 Australia East Azure EU2 Frankfurt AWS AU2 Sydney AWS US1 Oregon AWS |
For Document types, the order of fields are now maintained during runtime. Earlier, the mapped fields were listed first followed by unmapped fields during runtime. |
10.15.1 | WFL-1168 | December 3, 2022 December 4, 2022 December 4, 2022 December 11, 2022 December 10, 2022 December 11, 2022 |
US2 East Azure EU3 West Azure AU1 Australia East Azure EU2 Frankfurt AWS AU2 Sydney AWS US1 Oregon AWS |
While configuring a customized input form in JSON Customizer, if users provide a numeric value for a particular field in the code block, the rendered input form shows the field type for that field as str instead of num. |
10.15.1 | WFL-1124 | December 3, 2022 December 4, 2022 December 4, 2022 December 11, 2022 December 10, 2022 December 11, 2022 |
US2 East Azure EU3 West Azure AU1 Australia East Azure EU2 Frankfurt AWS AU2 Sydney AWS US1 Oregon AWS |
Users receive invalid authorization error while testing a newly created authorization. |
10.15.1 | WFL-1209 | December 3, 2022 December 4, 2022 December 4, 2022 December 11, 2022 December 10, 2022 December 11, 2022 |
US2 East Azure EU3 West Azure AU1 Australia East Azure EU2 Frankfurt AWS AU2 Sydney AWS US1 Oregon AWS |
Users cannot save a workflow if the workflow contains a Run Workflow action that calls another webhook-enabled workflow having a $ key in the payload body. |
10.15.1 | BIC-17858 | December 3, 2022 December 4, 2022 December 4, 2022 December 11, 2022 December 10, 2022 December 11, 2022 |
US2 East Azure EU3 West Azure AU1 Australia East Azure EU2 Frankfurt AWS AU2 Sydney AWS US1 Oregon AWS |
The routing rules got deleted whenever users tried to update a routing rule for a subscriber from Messaging Service Trigger. This issue occurred because the cache memory was not getting refreshed. Modifications have been done to ensure that the data is stored correctly in the cache memory and the routing rules are not getting deleted. |
10.15.1 | BIC-17997 | December 4, 2022 December 4, 2022 December 11, 2022 December 10, 2022 December 11, 2022 |
EU3 West Azure AU1 Australia East Azure EU2 Frankfurt AWS AU2 Sydney AWS US1 Oregon AWS |
Tenant is not responding or loading pages. Connections are getting consumed by the storage services as part of checking if the previous scheduled integration is still in progress when the preventConcurrentExecutions option is enabled in the scheduler for Flow services. As the connections are blocked, any new execution waits for the connection. This issue is resolved by releasing the connections. |
10.15.1 | WFL-1266 | December 3, 2022 December 4, 2022 December 4, 2022 December 10, 2022 December 11, 2022 |
US2 East Azure EU3 West Azure AU1 Australia East Azure AU2 Sydney AWS US1 Oregon AWS |
Listener executions did not happen. During deactivation and activation of listeners, workflow and listener went into an inconsistent state because of a communication gap. The listener was active but the workflow was inactive. Changes are made to handle the edge case for deactivation and activation of listeners. |
10.15.0 | WST-6755 | December 6, 2022 | US1 Oregon AWS EU2 Frankfurt AWS |
Salesforce listeners were not working. Issues with missed events are now resolved. |
10.15.0 | WST-6755 | November 25, 2022 | US1 Oregon AWS | Listeners were not working. This issue is resolved. As part of this, added logic to capture additional logs that facilitate easy debugging. |
10.15.0 | WFL-1266 | November 24, 2022 | EU2 Frankfurt AWS | Listener executions did not happen. During deactivation and activation of listeners, workflow and listener went into an inconsistent state because of a communication gap. The listener was active but the workflow was inactive. Changes are made to handle the edge case for deactivation and activation of listeners. |
10.15.0 | BIC-17997 | November 20, 2022 | US2 East Azure | Tenant is not responding or loading pages. Connections are getting consumed by the storage services as part of checking if the previous scheduled integration is still in progress when the preventConcurrentExecutions option is enabled in the scheduler for Flow services. As the connections are blocked, any new execution waits for the connection. This issue is resolved by releasing the connections. |
10.15.0 | WFL-801 | October 13, 2022 October 18, 2022 October 19, 2022 |
EU3 West Azure AU1 Australia East Azure US2 East Azure |
Workflows scheduled to run every 30 minutes timed out after 30 minutes without showing the logs. Most of the executions timed out due to action timeouts. This was observed intermittently. |
10.15.0 | WFL-1111 | October 18, 2022 October 19, 2022 |
AU1 Australia East Azure US2 East Azure |
Some workflow executions fail with the following error message: Cannot convert object to primitive value. |