7.5

Phase 2: Global Condition Resolution
In phase 2, the document runs any attachments you selected to run before the document prints, and then resolves all global
conditions for the current data page.
Phase 3: Document Page Printing
In phase 3, the document processes each page of the document. It uses the conditions it resolved in phase 2 to determine
whether to run and print the page and, if it prints the page, which objects to include in the output. In this phase it also evaluates
all local conditions as it encounters them. Thus the document evaluates conditions at two distinct points in time. It evaluates all
global conditions immediately after it fills the data page buffer, and maintains the results in memory for reference as it merges
the data page. It evaluates all other conditions as it prints each page of the document.
When it finishes processing all pages of the document, it re-initializes, empties the buffer and reads the next data page.
Techniques for Inserting Triggers
What are the common techniques for inserting a trigger?
How you create and insert a trigger is operating system dependent. There are four common techniques to insert a trigger man-
ually:
1. Manually concatenating two files
With this technique, you add a trigger by concatenating two files where the first contains the trigger and the second con-
tains the input data. You send the concatenated file to the printer using the DOS Copy command or the file transfer pro-
tocol (FTP).
2. Setting up the print server to automatically insert triggers
This technique works with a print server running either Novell or Windows NT. You create a print queue or print device
for each document installed in the printer, and associate the appropriate trigger for the document with the queue you
set up for it. All queues point to the same physical printer. When you send a job to that queue, the server automatically
inserts the trigger associated with that queue before it forwards the printer job to the printer.
3. Setting up the host to automatically insert triggers
This is the same technique as setting up the print server to automatically insert triggers. The only difference here is that
you set up the queues on the host on which the input data resides. The host inserts the trigger ahead of the spool file
when it sends the print job to the printer. This technique does not work with all hosts.
4. Including the trigger in application output
With this technique, you modify the output of the application that generates the print file so that it adds a trigger for the
appropriate document. It is important to understand that this hampers your ability to print these jobs using other
printers since two additional lines are added to the print file.
Printer-Specific Control Characters
You can precede a trigger with printer-specific control characters. The most common reason to do so is to ensure the printer
receives the job you send as a new job.
A printer expects each job that it handles to end with a special character that tells the printer it has reached the end of the input
data. Until the printer receives this special character, it continues to process all input it receives as part of that job. If there is
no input, the printer waits for a defined period of time, then times out and proceeds to the next job. If a new job arrives during
the period of time the printer is waiting for input, the printer does not recognize it as a new job; rather it processes it as input
for the current job.
Document Output and Preview
©2010 Objectif Lune Inc - 673 -