Avery Dennison Pathfinder 6057 LNT Programmer Manual using XML - Manual (Page 55)

Creating Job Data 5-1
C R E AT I N G J O B D ATA
Job data defines the data printed in each field on the supply. You can also specify printer
configuration information to override any values set in the Job Packet.
Field data is applied in numeric order or by the optional id. Each job data file must use the
same method for each field on the supply. If data is supplied for two fields by the optional id,
the remaining fields on the supply must also have data supplied by the optional id.
JobData packets are not necessary for most applications. Standard print and apply
applications use the device API to issue print commands directly to the system. JobData
packets provide a file-based mechanism that may prove useful in print server-style
applications. You can test JobData packet functionality by putting the packet into a file with a
.job extension and moving that file into the Print hot folder.
D e f i n i n g t h e Jo b D a t a Co n t ai n e r ( R e q u i r ed )
The JobData tag is a container for the list of all fields (label layout) in the LNT file. There
must be one of these per job.
It contains the following attributes: id and count.
Syntax
<JobData id=”value” count=”value”>
job data information
</JobData>
id The identifier (name) of t he target LNT. An y appli cations using LNT should
reference this data. Use any 32-character ma ximu m (UNICODE) string. Do
not use the same name for t wo files or an erro r occurs!
count The number of fields in th is file. If it is not defined, the count is automatically
calculated.
Example
<JobData id=”SaleText” count=”2”>
job data information
</Fields>
Specifies data for SaleText, which contains two fields.
Defining the Fie ld Container (Optional)
The Fields tag is a container for one field’s data.
Valid values include: Any UNICODE string containing less than 256 characters.
It contains the following attribute: id.
Syntax
<Field id=”value”>Data</Field>
id The identifier (name) of t he target <Field>. All Fie lds in a <JobData> file should
have this attribute or non e of the fields should have it defined. If all
<Field>s
have an id defined, the d ata is used in the named fields. If all <Field>s do not
have an id defined, the d ata is used in the order it is received.
Example
<Field id=”Price”>$19.99</Field>
Defines $19.99 as the data for the Price <Field>.
5