Release 1.1

Usage Notes

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

• User Roles.

  B2B Cloud provides only a user to manage all the system capabilities. This means, the same user name can perform all other roles (Administration, Business Analyst, or Developer).

Known Issues

• BOC-1453.

  Partner user and B2B Cloud user name cannot be same: You must not create a partner user with the same username that you use for logging into B2B Cloud. Additionally, you must also not modify your username to match an existing username of a partner user in the My Profile page of Integration Cloud. This will result in an access denied error after you log into B2B Cloud.

  Workaround: If a partner user is created with same name as the B2B Cloud login username, delete the partner user and create another partner user with a different username other than the login username. If the login username is changed from the My Profile page of Integration Cloud to an existing partner user, then use a unique username in My Profile page on webMethods Integration Cloud.

• Forgot password functionality.

  B2B Cloud supports the forgot password functionality by leveraging webMethods Integration Cloud capabilities.

  Workaround:

  1. Log on to webMethods Integration Cloud.
  2. Link to change the password https://tenantSpecificDomain.webmethodscloud.com/integration/#/forgot-password
  3. Type your user name and enter the captcha code.
  4. Click Change Password.
     
     

• BOC-2358.

  Secondary certificates are not used for sign-verify, encrypt-decrypt, or SSL usages for any document received over any AS2 channel.

  Workaround: Ensure that the valid certificates are set as primary certificates.

• BOC-2266.

  Secondary certificates cannot be imported or exported.

  Workaround: No workaround.

• BOC-2386.

  Irrespective of the signing algorithms mentioned in an EDIINT message, B2B Cloud signs the MDNs with SHA1 algorithm.

Resolved Issues

Release 1.1

• BOC-1511

  Partner user validation with AS2 protocol: When a partner-user sends a document over AS2 channel, B2B Cloud does not validate if the partner user is associated with a partner. The document is processed regardless of whether the partner and partner user association exists.

• BOC-1239

  AS2 resubmit: B2B Cloud allows you to resubmit all the transactions and the corresponding content parts without any checks. In the AS2 channel, some content parts are not relevant for resubmission. There is no way to identify the non-relevant content parts on the UI.

  For inbound AS2 transactions, when you resubmit, activity logs are added to indicate the error.

  For outbound AS2 transactions, UI shows the corresponding error message.