Enables exactly-once processing for the trigger and instructs the server to check a document’s redelivery count to determine whether the trigger has received the document before.

Specify that exactly-once processing is provided for documents received by this trigger and instructs the server to check a document’s redelivery count to determine whether the trigger received the document previously. The redelivery count indicates the number of times the routing resource has redelivered a document to the trigger.

Specify that exactly-once processing is not provided for documents received by this trigger.

Indicates whether a document history database will be maintained and used to determine whether a document is a duplicate.

Indicate that Integration Server maintains a history of documents processed by the trigger. When the trigger receives a document, Integration Server compares the document’s universally unique identifier (UUID) to the UUIDs of documents processed by the trigger. If there is a match, the Integration Server either determines the second document is a duplicate and discards it or, if the first document has not finished processing, marks the second document’s status as In Doubt.

Indicate that Integration Server does not maintain a document history database. The Integration Server will not use document history to determine whether a document is a duplicate of one already processed by the trigger.

Specifies the length of time the document history database maintains an entry for a document processed by the trigger. During this time period, Integration Server discards any documents with the same universally unique identifier (UUID) as an existing document history entry for the trigger. When a document history entry expires, Integration Server removes it from the document history database. If the trigger subsequently receives a document with same UUID as the expired and removed entry, the server considers the copy to be new because the entry for the previous document has been removed from the database.

The document resolver service must use the pub.publish:documentResolverSpec to define the service signature.