Specifying Preprocessing Actions When Using TRADACOMS
Default preprocessing actions are defined in TN document types. However, you can override the settings in the processing rule. For more information about how the preprocessing actions apply to EDI documents, see the section about preprocessing actions in webMethods Module for EDI Concepts Guide .
The following table lists the preprocessing actions you can set in a processing rule and the default settings for each action as set in the TN document types for EDI documents.
Preprocessing action | Description | Default setting in TN document type for the EDI document |
Validate Structure | Validates the structure of the EDI document | Validate the structure of the envelope |
Check for Duplicate Document | Determines if Trading Networks already has this document in its database | Do not use Trading Networks check for duplication |
Save Document to Database | Saves a copy of the document content, attributes, and/or activity log information to the Trading Networks database | Save document content, attributes, and activity log |
If a preprocessing action fails, Trading Networks records the error and continues processing. Trading Networks records the error in the errors variable in the BizDocEnvelope, which is in the bizdoc pipeline variable. Subsequent processing that you add, for example a service invoked by the Execute a Service processing action, can access the error information.
Note: You cannot use the Verify Digital Signature preprocessing action because values for the SignedBody and Signature system attributes are not set for EDI documents.