The purpose of this demo is to perform a native ELP_Command  based upon data stream content.

The modifications of the fist two examples may still remain in the ini file, as the priority for ELP using a found  ELP_Command is in this order:

A. A command found in the data stream
B. The last command of a true TRIGGERED section
C. The last command of a found SEARCHED section
D. The command found in the section named like the incoming queue (previous example)
E. Lowest priority: The ELP_Command  found in the GLOBAL   section

  1. Activate the Configuration Tab   and click Add key to rule
  2. Type in a new section name like TEST_TRIGGER
  3. Select the new section and add an ELP_Command  and a TRIGGER_WINDOWS key.
  4. Modify the ELP_Command  of TEST_TRIGGER: C1:1S2F500FFF;C1:2SF501;C1S0F500;
    This command will print the first page in duplex (if the printer has a duplex unit installed) then terms and conditions (Form 501) on the back page, all other pages of the job are in simplex mode with the letter head.
  5. Modify the key TRIGGER_WINDOWS like this for example: INVOICE

Return to your application. By default any data stream will be treated the same way as before, Unless:
The wording: INVOICE is found. So type in those 2 words, be careful, the triggers are case sensitive. Within a windows application use for the trigger a printer internal font like Arial, avoid Courier.


order the section is performed.
There are even more criteria, like a page

You my use several trigger in one section. The need to become all TRUE, in needs to be A4 and portrait. So you can position logos on the page depending of print direction and page size.

New rule/section    Add key to rule    Rule assistant