Fixes

This section provides information on the fixes for IBM® webMethods Integration version 11.0.10 and the subsequent release patches.

Issue ID Release Date Region Description
ATC-49 March 19, 2025 West Europe Netherlands Azure EU3 In the receive operation of the Applicability Statement (AS2) connector, the output parameters request > stream and request > payload > stream are empty when the payload received exceeds 500KB.This issue is now resolved.
PIE-95854 March 12, 2025 Europe Frankfurt AWS EU2West Europe Netherlands Azure EU3East US Virginia Azure US2 Provisioning a package to a project with IBM webMethods Integration fails if the target Integration Server installation includes a folder for the package. This issue is now resolved.
PIE-97173 March 12, 2025 Europe Frankfurt AWS EU2West Europe Netherlands Azure EU3East US Virginia Azure US2
  • Users can now add packages from external Git repositories successfully. Earlier, users were not able to add packages as the complete Git URL was not considered to pull packages.
  • The project creation for GitLab has been enhanced to support a broader scope and to use a general-purpose authentication mechanism for Git operations.
WFL-8464 March 12, 2025 Europe Frankfurt AWS EU2West Europe Netherlands Azure EU3East US Virginia Azure US2 The Select Integration Runtime drop-down list now displays all runtimes. Earlier, all runtimes were not displayed in the drop-down list due to resolution issues.
FLOW-7001 March 12, 2025 Europe Frankfurt AWS EU2West Europe Netherlands Azure EU3East US Virginia Azure US2 Previously, reopening the Set Value field caused \r to disappear and rendered as ENTER, positioning the cursor on the next line. The Set Value field now retains \r as text instead of rendering a new line when reopened.
FLOW-7008 March 12, 2025 Europe Frankfurt AWS EU2West Europe Netherlands Azure EU3East US Virginia Azure US2 Previously, when expanding document reference fields in the pipeline panel, the system showed no indication while waiting for the API response. A latency indicator has been added to inform users that data is still loading.
WFL-8672 March 12, 2025 Europe Frankfurt AWS EU2West Europe Netherlands Azure EU3East US Virginia Azure US2 While configuring an operation for OData V2, users encountered a limitation where the $expand parameter was restricted to just 36 characters, significantly impacting various use cases.To address this, the character limit for the $expand parameter has been increased to 2048 characters.
FLOW-7024 February 26, 2025 Europe Frankfurt AWS EU2US West Oregon AWS US1Australia East Azure AU1 Users experienced slowness while interacting with the IBM webMethods Integration user interface. To address this issue, the Project variables API will now only be fetched when a set value operation is performed. The fetched response will be stored at the application level and used until the pipeline is closed. A new fetch will only occur when a set value operation is invoked after reopening the pipeline.
FLOW-6884 February 19, 2025 Asia Pacific Sydney AWS AU2Europe Frankfurt AWS EU2US West Oregon AWS US1Australia East Azure AU1West Europe Netherlands Azure EU3East US Virginia Azure US2 Users experienced slowness in opening the pipeline and rendering the mapping lines. This has now been optimized.
FLOW-6908 February 19, 2025 Asia Pacific Sydney AWS AU2Europe Frankfurt AWS EU2US West Oregon AWS US1Australia East Azure AU1West Europe Netherlands Azure EU3East US Virginia Azure US2 An issue was observed with "the updated_at" information on the project card view when performing any DAF flow CRUD operations.
FLOW-6984 February 19, 2025 Asia Pacific Sydney AWS AU2Europe Frankfurt AWS EU2US West Oregon AWS US1Australia East Azure AU1West Europe Netherlands Azure EU3East US Virginia Azure US2 Previously, check boxes to enable business data logs for the document or document reference fields were unavailable. These have now been added.
BIC-45627 February 19, 2025 Asia Pacific Sydney AWS AU2Europe Frankfurt AWS EU2US West Oregon AWS US1Australia East Azure AU1West Europe Netherlands Azure EU3East US Virginia Azure US2 Users observed an issue where the runtime status was displayed incorrectly in the user interface when two listeners with the same name existed in different projects.
FLOW-6994 February 19, 2025 Asia Pacific Sydney AWS AU2Europe Frankfurt AWS EU2US West Oregon AWS US1Australia East Azure AU1West Europe Netherlands Azure EU3East US Virginia Azure US2 The "Add Package" functionality was not working correctly for Git URLs that contained the .git extension in the middle of the URL.
BIC-45999 February 19, 2025 Asia Pacific Sydney AWS AU2Europe Frankfurt AWS EU2US West Oregon AWS US1Australia East Azure AU1West Europe Netherlands Azure EU3East US Virginia Azure US2 Users observed an issue where the server attempted to connect to the Integration Server to fetch project variables, even when the tenant did not have the Develop Anywhere, Deploy Anywhere capability enabled. This resulted in unnecessary admin alert emails being triggered. The issue is now resolved by updating the logic to ensure that the server connects to the Integration Server only if the tenant has the Develop Anywhere, Deploy Anywhere capability enabled.
FLOW-6892 February 19, 2025 Asia Pacific Sydney AWS AU2Europe Frankfurt AWS EU2US West Oregon AWS US1Australia East Azure AU1West Europe Netherlands Azure EU3East US Virginia Azure US2 The limitation where semicolons (;) were not supported in the "Field" and "Value" drop-down list within the IF condition has now been resolved.
BIC-45785 January 29, 2025 Europe Frankfurt AWS EU2 Some tenants were incorrectly charged 1 transaction per 3 seconds, which is the default metering limit, instead of the custom metering limit set for them. Changes have been made to ensure that the customer’s custom metering limit is applied, rather than the default limit.
BIC-45751 January 28, 2025 US West Oregon AWS US1 An incorrect property was being considered for some paid tenants, leading to their inclusion in the list of tenants that surpassed the defined metering limits. Consequently, workflow and flow service scheduled executions ceased for these tenants. Changes have been made to consider the correct property, flowTransactionLimit , ensuring that paid tenants are not included in this list. This ensures uninterrupted workflow and flow service execution.
CCH-8411 January 23, 2025 Europe Frankfurt AWS EU2 The issue with account creation in the Cumulocity IoT connector has now been resolved.
UHM-7731 January 10, 2025 Asia Pacific Sydney AWS AU2 The workflow engines were restarting due to a parsing exception when receiving the <="" i="" style="box-sizing: border-box;">header in the E2EM agent. This issue occurs only when the incoming request contains a traceId in the OTel standard header format.The traceId in the OTel standard header format is now discarded, as E2EM agents do not currently support it. Additionally, all exceptions occurring during the request header parsing process are now handled gracefully. This ensures that the workflow engine remains stable and unaffected by any parsing issues in the E2EM agent.
FLOW-6680 January 05, 2025 Asia Pacific Sydney AWS AU2 Previously, the HTTP 412 Precondition Failed response was interpreted as a sign that the tenant's credit limit had been reached. This resulted in a message stating, Tenant credit limit exhausted; flow services cannot be executed. Please upgrade your plan. This validation has been removed from the user interface to avoid implicit error inference.
FLOW-6762 January 05, 2025 Asia Pacific Sydney AWS AU2 Previously, users could not specify if a field in the input or output signature could accept null values. A new option, Allow Null has been added enabling users to explicitly configure fields to allow null values when needed.
FLOW-6711 January 05, 2025 Asia Pacific Sydney AWS AU2 Previously, the field name `$rootArray` was restricted, and documents containing this field name could not be saved. This restriction has now been removed, allowing users to save documents with the `$rootArray` field name.
WFL-8292 January 05, 2025 Asia Pacific Sydney AWS AU2 Renaming a segment in the JSON Customizer moves it to the end of the JSON structure, disrupting the order of segments. This misalignment causes issues during JSON to CSV conversion and creates discrepancies in the schema and test input screen.
WACN-261 January 05, 2025 Asia Pacific Sydney AWS AU2 At times, accessing the Edit Account page in a connector without disabling the account caused a connection failure. The Edit button behavior is now updated and the users can only edit the account when it is disabled. If the account is enabled, the Edit button is inactive and prompts to disable the account to enable editing.
BIC-45083 January 05, 2025 Asia Pacific Sydney AWS AU2 Users were not able to define the REST API path if it included special characters like underscore and blank spaces. Changes have been made and the following special characters are allowed:(_) Underscore, (-) Hyphen, (.) Period, ($) Dollar sign, (!) Exclamation mark, (~) Tilde, (=) Equals sign, ( : ) Colon, (') Apostrophe or Single quote, (*) Asterisk and (,) Comma.
BIC-45196 January 05, 2025 Asia Pacific Sydney AWS AU2 OAuth 2.0 authorization stopped working due to the accumulation of expired tokens over time, resulting in the system becoming unresponsive. Changes have been made to ensure the expired tokens are deleted from the system daily.
WACN-264 January 05, 2025 Asia Pacific Sydney AWS AU2 At times, Connection pool exhausted error occurs despite setting the minimum and maximum pool limits. Changes have been made to ensure the connection pool values are read as configured in the database.