Save Document to Database Pre-Processing Action
You must save a document to the database when you want to:
![*](bullet.gif)
Deliver the document using reliable delivery with immediate or scheduled delivery.
![*](bullet.gif)
Deliver the document using queue for polling.
![*](bullet.gif)
Pass a document to a business process.
![*](bullet.gif)
Send a document back to the beginning as a “new” document (for example, because the document did not match any defined document type). This is called resubmitting the document.
![*](bullet.gif)
Send a document back through processing rules (for example, because the document was processed by the wrong rule). This is called reprocessing the document.
You can choose to save all documents, no documents, or only unique documents. If you want to save only unique documents, you must also specify the Check for Duplicate Document pre-processing action.
Option | Description |
Content | Save document content if you want to: ![*](bullet.gif) View the content in My webMethods when monitoring transactions. ![*](bullet.gif) Resubmit or reprocess the document. ![*](bullet.gif) Use the Deliver Document By processing action with reliable delivery. |
Attributes | Save custom attributes if you want to view attributes in My webMethods when monitoring transactions, search for documents based on custom attributes, or reprocess documents. Important: | If you reprocess a document without saving custom attributes, you might get unexpected results. Because the attributes are not saved, the document will not match processing rules that use extended criteria. Instead, the document will match another processing rule, such as the default processing rule, and Trading Networks will perform the processing actions defined in that rule. |
|
Activity Log | Record activity log entries when monitoring transactions. |