JetTrac Lookup ConfigForm

Using the JetTrac Lookup ConfigForm:

JetTrac Lookup™ allows dynamic processing of any type of data needed in a Adobe Central Document Server application, particularly useful for processing multiple bank accounts for a check application within a Adobe Central Output Server process. This allows for one input data file that is produced by the Line of Business application (e.g. Oracle Financials, J.D. Edwards, SAP, etc.) to have checks that need to be written on multiple bank account to dynamically call the correct information on a check by check basis. This way only one form and one TDF file needs to be designed that is used for all bank accounts.

Please note that the documents (e.g. checks) will print in the same order as the input data file. If you want to print groups of checks together based on dollar ranges to print in batches, then you can implement our JetTrac GroupRange™ product which will print checks in groups, e.g. all checks requiring manual signatures would be printed in one group so no manual sorting of checks would be required.

JetTrac Lookup™ is written in Java so it will run on any platform that supports Java, including, among others, Windows, UNIX, and AS/400. See the JetTrac Lookup Installation and User Guide for AS/400 for help on AS/400 installation and configuration.


This document is a guide to installing, configuring and using the JetTrac Lookup™ Custom Agent. This document includes detailed instructions for installation and configuration in the Adobe Central Document Server Job Management Database and example files to help you see how the program works.
Technical Support

If you need assistance in installing and configuring JetTrac Email™, call Pro Technology Automation, Inc. at 805-527-1248 ext. 0 or e-mail us at Please note that the JetTrac Email™ license fee does not cover configuration services and technical support so there may be an additional charge. Please ensure you read these instructions carefully before calling for technical support.

Using ConfigForm to Configure JetTrac Lookup™:


Lines of the ini file:

First field of each document: The field name of the first field in each record in the input Field Nominated File, or an exact string if the first thing on the line is a ^

Field name of the key value: The field name of key value (or =keyValue for fixed keys) A fixed key would allow you to specify in this ini file a specific lookup value. This would not change in any given job step. This would allow you to print using several different jobs, all of which would pull from one .db file. This field MUST be only one line long.

Field name for the trigger field: The field name of trigger field (insert after this). The fields found according to the key will be inserted after this field. This cannot be the same as the key value (Line 2). If this line is blank, the fields will be inserted immediately after the key field.

File path for the lookup.db: The fully-qualified lookup db file name. This is decribed in section section 2.4.

Field name for zero-pad or !!: The field name for zero-pad or !! This will allow you to add zeros to any field value in the data file. This is most often used for check number fields in the MICR line as they often need leading zeros that do not appear in the normal output. Further information about this is included as a part of the JetTrac Lookup.db file. If zero padding is not desired, two exclamation marks, !! need to be entered.

Y, N, or D for action on not found: is an option on how to handle processing if a lookup in the DB file is attempted but there is not match found. Y = stop on “not-found”, N = continue on “not-found” but don’t insert any fields or do any zero fill, D = default on “not-found” and use the very first row of the DB file for processing.
Important Note: The order of the fields in the Field Nominated File is critical. The field name of the first field in each record must be first in the Field Nominated File, then the Key Value line Line 2 must occur after that, then the Zero Pad field (if used) must occur after the Key Value field, then the Trigger field from Line 3 must occur after the Zero Pad field.

Each Line Serves the Following Purpose:

First field of each document: This is the number of fields in each record of the DB file

Field name of the key value: This is the maximum number of entries in the lookup table. If this number is less than the number of entries, the remaining entries will be ignored. JetTrac Lookup uses this number to optimize memory allocation and processing speed.

Field name for the trigger field: This is the line where all of the output field names are declared. This also allows to specify whether they be ^field or ^global. The first field also specifies the name of the field that will contain a number to tell JetTrac Lookup the number of digits to place in the zero-padded field. Each subsequent field is separated by a pipe | character (usually the shift of the backslash key) and the line must end with a pipe character.

Lines 4-n: These lines contain the lookup value to match followed by the values to insert in the fields specified in line 3 above. Each value is separated by a pipe | character (usually the shift of the backslash key) and each line must end with a pipe character. The first value in each line is the lookup value that must match the value found in the key field specified in the .ini file. After the key value, the fields follow in order corresponding to the field names specified in line 3. There should be the same number of field values on these lines and there are field names on line 3.

To create a multiple line field, simply place a tilde ~ between the desired data. This will not change the way that JTLookup processes the data, but JFMerge will interpret and show this as a carriage return. (If you need to use tilde for some other reserved use, you can pick another character and use a –anl[x] option in the jfmerge.exe command line to change the default new line character. You can also change the default in the jfmerge.ini file.

A note on check number zero padding: If you are using check number padding, the number representing the length of the check number must immediately follow the lookup value, as the first “field” to be inserted. In order to use the padded check number in one of the inserted field values for that same key value, use a “@” character in the desired spot. The @ will be replaced with the padded check number. The fieldname used for the field containing the number of padding digits is not required, but the place (as the first field inserted) is reserved.