Release 1.3

This readme includes improvements, usage notes, and known and resolved issues that have been implemented for the webMethods.io B2B 1.3 release.

Highlights

Component	Description
Support for XML document	webMethods.io B2B now supports XML documents. It allows you to: Extract and build from an existing XML schema. Verify schema and associated processing rules using a testing tool. Create custom document attributes and utilize them within processing rules. For more information, see XML Documents.
Support for trading partner extended fields	Extended fields are now available to hold unique data values for trading partners. For more information, see Extended Fields.
User and role-based access	You can assign one of the following roles to new users: Administrator Developer User Each role allows specific access to features. For more information, see User Roles.
Deployment	A system to move, update or delete assets across registered environments. For more information, see Migrating Assets.
Deployment logs	All deployments are logged and available to view. For more information, see Monitoring Deployment logs.
Data purging	Data can be purged based on customized schedule. For more information, see Purging Data.
Support for UN/EDIFACT 93A	UN/EDIFACT 93A standard document types are now available. For more information, see Supported Business Documents.

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

Secondary certificates are not used for sign-verify, encrypt-decrypt, or SSL usages for any document received over any AS2 channel. To work around this issue, ensure that only valid certificates are set as primary certificates.
Secondary certificates cannot be imported or exported.
Purge webMethods.io B2B provides data purge capabilities. This capability can be applied by Administrative users to configure the desired data purge policy. In case the policy is enabled, the transactions are permanently deleted from the system. This is as expected based on the configured policy.
webMethods.io B2B is currently only available in the US West (Oregon) region. More regions would be added soon.

BOC-4420.

Updating a purge schedule is allowed at the time of schedule execution.

webMethods.io B2B allows updating of a purge schedule, which is already executing. This leads to data inconsistency in the database as some of the data is already purged.

There is no workaround for this issue.

Note: Ensure that you do not update the Purge schedule at the schedule execution time. webMethods.io B2B displays the next execution time under the Next execution column.
BOC-4929.

Extracting a custom attribute fails in a special case.

Extracting a custom attribute, which has the same name as one of the system attributes SenderID, ReceiverID, GroupID, DocumentID, ConversationID, UserStatus, Signature, SignedBody) fails with an error.

To work around this issue, rename the custom attribute and try extracting it.
BOC-4940.

Ordinal indices of rules get corrupted due to some race conditions observed.

Some race conditions are observed when multiple actions, such as import, rule movement, applying a deployment, are simultaneously performed on rules. This makes changes to the ordinal index of rules due to which some ordinal indices go missing or get repeated because of which some rules would have problems in updating the details.

There is no workaround for this issue.

BOC-4111.

During an active webMethods.io B2B user session, a user is logged out abruptly from the user interface. This happens after every 10 minutes.

It is because, a Single Sign On (SSO) session is invalidated based on the access token lifespan.

This issue is now resolved.