Advanced document properties facilitate the setting of document properties
from multiple sources. Document properties can be set from Barr Enterprise
Print Server headers, LPD headers, job tickets, data contained in the
document, or fixed values, and so on. Advanced document properties is
a complex feature that only advanced users and professional
service engineers should configure.
To configure document properties, you must first configure one or more
profiles for the desired type of header data. Your profile options are
native header profile, job ticket profile, job parsing profile, and headers
from data profile. The configuration of these profiles includes specifying
which headers to use, what EOM document properties to map them to, and
potentially which job ticket values to match to which EOM property values.
Once the profiles are configured, choose the order in which the configured
profiles are used when a document is received, and what the default static
value is if no data is found in the respective header.
The profiles of the individual document information sources (native
header, job ticket, job parsing, and headers from data) can be reused
in many different advanced document property profiles, just as the advanced
document property profile can be reused by many different Barr EOM source
devices.
Complete the following steps to configure document profiles during source
configuration.
Complete the following steps to configure native header profiles. Native
headers contain information that arrives as part of the transmission protocol
that is used to receive documents.
Next to Native
header profile, click New
to create a native header profile. You can also select a profile in the
list and click Edit to make modifications.
Enter the profile Name and Description.
From the Native
headers tab, select the EOM device types whose headers should be available
for mapping. You can choose one or more of the following: email, FTP,
LPD, network folder, socket, WebSphere MQ, Windows queue, or BEPS devices.
The selected native headers will be available on the Document
property mappings tab and the Document
owner mapping tab.
Complete the following steps to configure a job ticket profile. Job
tickets contain information about the document, and/or how the document
should be treated. Tickets are logically separate from the document, and
in some cases are inserted in front of the document file.
Next to Job
ticket profile, click New
to create a job ticket profile. You can also select a profile in the list
and click Edit to make modifications.
Enter the profile Name and Description.
From the Job
ticket tab, select the job ticket Type.
You can select one of the following types:
XML
Job Ticket - An external job ticket template in an XML format.
The XML tags are accessible throughout the job ticket profile configuration.
Barr
Spool Header - A group of fields that are associated with Barr
Enterprise Print Server.
Output
Statement - A list of fields associated with the Barr RJE header.
If you selected XML Job
Ticket, click Map job ticket.
From the Open dialog,
select one or more sample tickets to create the ticket mappings.
This option is not available for Barr Spool Header and Output Statement
tickets, as they have fixed mappings. If necessary, click Clear
mappings to remove any associated job mapping.
Once one or more sample tickets have been mapped, use one
of the following methods to search for the job ticket.
Embedded
in the document - Searches for the job ticket embedded in a document.
To use this option configure the following options:
In the Start
of job ticket recognition string box, enter the appropriate string
value.
In the End
of job ticket recognition string box, enter the appropriate string
value.
Use the Remove
from document check box to determine if the job ticket data should
be removed from the document.
When using job
tickets, all lines up to and including the job ticket are deleted from
the file. Select the Keep data prior
check box to prevent data loss.
In
a separate file - Searches for the job ticket in a separate file.
To use this option, configure the following options:
In the Folder
to search box, click the ellipsis (...) button to choose a folder
to search or type the folder location in the box.
In the Match
job ticket file name using this document property list, select
the appropriate property.
In the Match
job ticket extension using this extension box, enter the appropriate
file extension.
Use the Delete job ticket file after processing document
to determine if the job ticket profile should be deleted after
processing.
In the If
the job ticket is not found, take the following action list, select
how to process the document if the job ticket is not found. You can choose
to process the document normally, receive the document and place it in
error state, or reject the document.
Complete the following steps to configure a job parsing profile.
Next to Job
parsing profile, click New
to create a job parsing profile. You can also select a profile in the
list and click Edit to make modifications.
Enter the profile Name and Description.
From the Job
parsing tab, select the Originating
printer family. You can select one from the drop-down list. To
manage the printer family profiles, click the Browse button. The Manage
Printer Family Profiles dialog box is displayed.
Complete the following steps to configure a headers from data profile.
Headers from data profiles consist of information that Barr EOM can extract
from specified location within the actual document data. Barr EOM can
extract data from documents in various formats including ASCII, ASCII
with ASA, S/370, and VBM.
Next to Headers
from data profile, click New
to create a headers from data profile. You can also select a profile in
the list and click Edit to make
modifications.
Enter the profile Name and Description.
From the Headers
from data tab, select the Data format.
You can choose ASCII, ASCII with ASA, S/370, or VBM.
In the Code
page list, select the code page for the document.
Specify the Extraction
method, you can choose one of the following:
Line-based
- Searches for the header based on a particular line.
Record-based
- Searches for the header based on a particular record, regardless of
page breaks.
In the Headers
to extract grid, click in the grid to enter the headers
to extract. These variables will appear on the Document
property mappings tab and Document
owner mapping tab. Enter the following information in each column.
Line-based
Name
column - Specifies the header field for the data to be placed in.
Page column - Specifies the page where data extraction
will begin.
Line column - Specifies the line number in the file
that contains the data.
Column column - Specifies the column where data extraction
will begin. For ASCII with ASA carriage control files, the first column
is not counted (in other words, the second column is treated as the first
column).
Length
column - Specifies how many characters to extract.
Record-based
Name
column - Specifies the header field for the data to be placed in.
Record
column - Specifies the record number in the file that contains
the data.
Position
column – Specifies the position where the header data will begin.
Length
column - Specifies how many characters to extract.
From the Document property
mappings tab, use the grid to configure the document property mappings
for the extraction profile.
To enable a document property
mapping, click the Map Values
check box for the appropriate property.
Click in the External
Field column, to select the mapping from the list shown. If necessary,
you can use the look up table to adjust the values.
Click in the Unmapped
Value Action column to select what happens when there is a missing
look up table entry. You can choose to skip the property mapping entirely,
assign the external value as-is, or assign the unmapped value default.
Click in the Unmapped
Value Default column to specify a default value.
Choose one of the following
options for setting the document owner.
Use the Windows user
id (if available) - Sets the document
owner to the Windows user ID. This can be used with the following source
types: Windows queue, network folder, and Web file upload.
Map
to the following external field - Sets
the document owner to external field selected in the drop-down list.
For
job ticket profiles, the ticket information
fields are expressed as XPath statements. XPath statements show the structure
of the ticket information. It allows the ability to specify a specific
instance of a field if that particular information field occurs more than
once in a documents metadata. If a particular external field is not listed
in the list, the XPath statement can be directly entered.
For headers from data profiles,
this list will be populated with the headers specified.
If you chose to map to
an external field. Use one of the following methods to map the field.
Use
the external value as the EOM user name - Uses external document
property information as the EOM user name. Note, when the document is
first received by the source the document has existing properties. These
properties are called external document property values.
Use
the following lookup profile - This is not currently implemented.
When implemented, you will be able to use a lookup table to map Personal
Identification Numbers to user names.
Use
the following value mappings - Uses the values entered in the table
for the external document property value. Click directly in the table
to enter the mapping values. When the external document property has one
of the values listed in the External
Field Value column, the value in the Property
Value column will be used.
If desired, under If unable to determine the document owner,
assign the following user, click the ellipsis button to assign
a document owner from the User
and Group Selection dialog box. This user will be assigned if the
document owner cannot be determined using the above mapping settings.
Click OK.
Determining the profile order
You can determine the order in which the configured profiles are used
when a document is received, and what the default static value is if no
data is found in the respective header. The mapping order can be configured
for each document property.
From the Document
Properties Profile dialog box, in the grid, click in the Mapping
Order column for the EOM document property. A configuration grid
displays below the cell. Use the following procedures to configure the
mapping order.
Configure the order
in which headers are processed by selecting the appropriate rows and clicking
the Up and Down
buttons.
To enter a default
static value, click in the Mapping/Value
cell next to Static Value and
either type or select the value. This static value is used if no data
is found in the preceding headers. The static value by default is the
value for that document property in the source’s Document
properties tab.
For
job ticket profiles, the ticket information
fields are expressed as XPath statements. XPath statements show the structure
of the ticket information. It allows the ability to specify a specific
instance of a field if that particular information field occurs more than
once in a documents metadata. If a particular external field is not listed
in the list, the XPath statement can be directly entered.