Sender and receiver the document must have

Document type for the document

User status the document must have (for example, Needs Approval)

Whether errors were or were not encountered during document recognition or attribute extraction

Custom attributes the document must have (for example, Total_Order_Amount custom attribute value greater than $10,000)

Perform the action that is defined in the document type.

Perform the action that you define in the rule.

Never perform the action at all.

Execute a Service action, to execute a custom service. For example, you could execute a service to send the document to a back-end system for processing or to update data in an internal system with extracted attributes. You can use data that is in the pipeline in the service; for example, you could perform the Check for Duplicate Document pre-processing action and then execute one service if the document is a duplicate and another service if the document is unique. Trading Networks places the service results in the pipeline so you can use them in output templates or other processing actions.

Alert Email Message action, to send a message to a contact in the sender’s or receiver’s profile, the webMethods system administrator, or a specified email address when document processing is complete. For example, if the document is a purchase order, you could send a message to alert the person who approves purchase orders. You can include pipeline data in the message (for example, the document type for the document).

Change User Status, to assign a user status to the document for use when searching for documents or generating reports. For example, if the document is a purchase order, you could set the document’s user status to Needs Approval. The person who approves purchase orders can search for documents whose user status is NeedsApproval. The user status is assigned to the User Status system attribute.

Deliver Document By action, to deliver the document to the receiving partner using a specified delivery method.

Respond action, to send a message back to the document sender (for example, an acknowledgement for a purchase order). You can include data from the pipeline in the message. For example, you could have the Execute a Service action asynchronously invoke a service that performs the appropriate processing for the purchase order, then return confirmation that the purchase order was received and processed. You could then have the Respond With action return an acknowledgement that indicates that the purchase order was received.