Built-in processing rules
webMethods B2B has a set of built-in processing rules to ensure the intended functions and flows for processing a specific set of business documents. Therefore, you cannot delete or modify a built-in processing rule. However, you can change the sequence of the built-in processing rules and activate or deactivate them to make webMethods B2B use the processing rules that you create to process inbound documents.
The built-in processing rules in webMethods B2B are listed in the following table:
Built-in processing rule name | Description |
---|---|
EDIINT Send Message Using Channel | Sends a synchronous EDIINT message by using the outbound channel that is configured for a partner. |
EDIINT Send MDN Message Using Channel | Sends an asynchronous MDN message by using the outbound channel that is configured for a partner. |
Deliver Functional acknowledgment | Delivers a functional acknowledgment by using the outbound channel that is configured for a partner. |
EDIINT Process Message | Persists EDIINT messages received from a partner. webMethods B2B creates several transaction documents for inbound EDIINT documents with the payload type EDI. webMethods B2B achieves this process by splitting the payload, group, and interchange of the message. |
EDIINT Process MDN Message | Processes and persists EDIINT MDN messages that are received from a partner. |
Profile Validation Standard Fields | Ensures that all the required standard fields of a partner profile have no blank values. |
Profile Validation Profile | Validates a partner profile for standard fields. In addition to
validating all the mandatory fields, it ensures that the partner profile has the corporation data,
and the required identity type, and identity value. If a preferred outbound channel is selected, it
validates all the mandatory values that are specified for the channel. Note: If a partner is
exchanging an EDIINT AS2 document, the partner must have the EDIINT AS2 identity type in addition to
the existing identity types, for the transaction to be processed successfully.
|
Profile Validation Extended Fields | Validates the extended profile fields. |
Default Rule | Matches an inbound document with any sender, receiver, document
type, document user status, and recognition errors. The pre-processing actions in the default
processing rule indicate that webMethods B2B must use the settings that are mentioned in the
inbound document. The default processing rule is not editable. Tip:
Keep the default rule as the last rule on the Processing rules page when no search criterion is applied. |
For details on a default processing rule, see How Does a Default Processing Rule Work?