Release 10.11

Highlights

Usage Notes

The following functionalities have certain restrictions in webMethods.io B2B system:

• Partner certificate automatically gets associated with the new partner created with the same details as the deleted one. Also, the certificate is not listed in the certificate monitoring page.

• To use 2-Way SSL/TLS functionality, business documents must be sent to a channel URL with the port 8443 appended to the hostname. The 2-Way SSL/TLS functionality is an additional-level of validation and security. This along with the partner-user credential-based authentication ensures secure exchange of business documents.

• While synchronizing partner profiles as part of partner onboarding, webMethods.io B2B ignores all new partner profiles, retaining only the pre-existing profiles. Additionally, a message about the duplicate occurrence is logged in the Activity logs under the General category.

• Software AG recommends that you do not create, update, or delete any B2B assets during the upgrade window.

• If you are not able to map multiple documents to a document array based on indexing in a Flow service, create a document array that holds all the required documents using the “insertDocument” operation of the “Document” service.
  For example, if you want to map three documents (D1, D2, and D3) to a document array (DA1[]), add the “insertDocument” operation thrice: once for each document, and insert D1, D2, and D3 into the “documents” array. You can also use loops to run the “insertDocument” operation thrice. Finally, map the “documents[]” array, which holds all the three documents, to DA1[].

• Publishing of assets from one environment (the origin) to another environment (the target) with inherited users is not supported.

Known Issues

This section lists any issues for the current release that were known when this readme was published:

• BOC-2204
  If you create a tenant user in Software AG MyCloud with a username that is identical to an existing partner user in webMethods.io B2B, an Internal Server error appears when the tenant user attempts to log in to webMethods.io B2B.
  Workaround: Delete the partner user and create another partner user with a unique username that does not match any of the existing tenant usernames. However, if you do not want to delete the partner user, delete the tenant user and create a tenant with a unique username that does not match any existing partner users. You can do this on the MyCloud > Administration > Users page.

• BOC-13620
  For UNDEDIFACT documents, the FA status is not reconciled correctly when FA is received. Instead a new record of FA is shown for FA Reconciliation.

• BOC-13607
  When duplicate documents exist for UNEDIFACT documents, the status is not reconciled to duplicate under FA Reconciliation.

• BOC-13549
  Occasionally, an “Authorization Required” error occurs while reprocessing a transaction when the following sequence of actions are performed:

  1. Add a user in MyCloud.
  2. In webmethods.io.B2B, select this new username in the processing rule action to call an integration.
     Workaround: Ensure that the user with that username logs in to webMethods.io B2B at least once.
     
     

• BOC-8265
  In the Full Message log entries for Course of transactions, webMethods.io B2B renders the timestamp in Universal Time Coordinated (UTC) rather than the current time zone.

• FLOW-1912
  Flow services using the webMethods.io B2B connector fail with an error message indicating that the webMethods.io B2B connection is disabled.
  Workaround: Update the webMethods.io B2B account, this refreshes the account and enables it.

• BOC-10263
  During the product upgrade window, you might notice a few failed transactions that involve execution of an operation in webMethods.io B2B connector on webMethods.io Integration.
  Workaround: You can resubmit the failed transactions after the upgrade window.

• BOC-12853
  Although tenants with custom domain names can deploy on-premises assets to the cloud, thereafter, certain configurations involving cross-applications and runtime invocations do not work.
  Workaround: There is no workaround for this issue.

• BOC-13552
  webMethods.io B2B resets the AS2-related runtime options to default values.
  Workaround: Update the affected runtime option again.

• BOC-13902
  webMethods.io B2B does not support two-way SSL communication with webMethods Cloud Container. If two-way SSL is configured in Cloud Container, executions in webMethods.io B2B that invoke Cloud Container services fail.
  Workaround: Change the authentication mode in Cloud Container to allow one-way and two-way SSL API execution calls (credentials and certificate).

Resolved Issues

This section lists any issues that were resolved as part of this release:

• BOC-12893
  Transactions failed while extracting the attributes of a business document.
  This issue is resolved.
  
  
• BOC-12881
  webMethods.io B2B could not recognize the sender and receiver for EDI transaction with qualifier set to 16.
  This issue is resolved.
  
  
• BOC-13069
  In webMethods.io B2B, when you copy-paste some payload in the Document Submission form, upon modifying or deleting any character in the payload, whitespaces turn into tab spaces resulting in incorrect number of characters.
  This issue is resolved.
  
  
• BOC-13042
  In the Attributes page under Transactions, long values are truncated, and the complete attribute name does not appear for you to copy it.
  This issue is resolved.
  
  
• BOC-12913
  You could not add and modify processing rules in certain scenarios.
  The issue is resolved.
  
  
• BOC-12894
  Browser was unable to load large transaction data.
  The issue is resolved.
  
  
• BOC-13037
  setXpathForDocAttribute operation in the webMethods.io B2B connector in webMethods.io Integration caused technical issues. The operation is removed.
  
  
• BOC-12747
  RNIF version 1.1 was not supported, but was listed in RNIF TPA.
  The issue is resolved.
  
  

Fixes

This section provides information on the fixes for webMethods.io B2B v10.11.