Document trigger

A Document trigger is a variable that determines the scope of the Document. For example, if you assign the variable $customerNumber to the Event field customerNumber, you can use $customerNumber as Document trigger. In this case, all documents with the same customer number in the input job are included in the same Document.

Beginning and end of a Document

The Document trigger determines the beginning and end of a Document. The current Document ends, and a new Document begins, when the Document trigger variable changes.

Sorting the input

Since a Document ends when the Document trigger changes, the input must come in the right sequence. For example, if customer number is used as Document trigger, all documents with the same customer number must be handled in sequence. This means you may have to sort the input before the Documents are created. See Sorting documents.

Output from several Runtime jobs

If the output connector handles output from several Runtime jobs, you must specify a Document trigger for each Runtime job. This means a connector can have several Document triggers – one trigger per Runtime job. Note though that you can use the same trigger variable (customer number, customer name, etc.) for all Runtime jobs.