NA batch and XML processing files

Note that referenced data files must be in a separate folder from the XML processing files.

Using the XML processing file option, you are limited in the batch job to specification of a single template, effective date, and delivery option per input file. This means you must split your input data files by these key characteristics (for example, by template and delivery option). If this option is not flexible enough, use the Native Input File Support option described in the next section.

Here is an example of how to process a template that implements the delimited data model using the NA-batch input files:

<?xml version="1.0" encoding="utf-8" standalone="yes"?>
    <batch xmlns="http://pb.com/EngageOne/batch-input"> 
        <records>
            <template name="CSV Fed Invoice_v1"/> 
            <deliveryOption name="OPTION01"/> 
            <data file="linked.csv"/>
        </records>
        <records>
            <template name="Some Keyed Record File"/>
            <deliveryOption name="OPTION02"/>
            <data file="linked_2.svd"/>
        </records>
    /batch>

Your input XML data file may contain data for multiple output documents. In this scenario, the input file will be divided into output files in as follows (in order of precedence):

1. Using the attribute, startOfPublication provided in the data element of the trigger file. In this attribute, the XPath to the element containing a single piece of document data should be provided. The input XML is divided into XML which contains a single instance of the element pointed to by the startOfPublication XPath, and the rest of the input XML is repeated in each output XML.
2. As detailed in the paragraph above, the startOfPublication XPath is not taken from the trigger but the template master XML file. Note that the startOfPublication may be missing in older templates, in which case this method of dividing output files is skipped.
3. If there is no startOfPublication in the trigger file or the template master XML, the input XML is divided on the first element after the root node.

The referenced data file linked.csv contains delimited-format records. These record sets are partitioned as they have been defined in Designer. EngageOne Server provides no way to identify a record set. This file contains the data for multiple document compositions. NA batch reads through the data file and partitions out the record sets that are then be processed as individual compositions.

C001,Gertrude,Forsythe,632 West Fifth Street, ,Covington,KY,41011,Sep 1,
    Sep 30,September,1,30,2005
K001,519-346-8,8000,10000,4,5,3905,1905,,
K002,Sep 2,Transfer to savings 3334411,,500,,,,,
K002,Sep 7,Point of sale debit - JC Penney,,100,,,,,
K002,Sep 9,Check # 1432,,200,,,,,
K002,Sep 11,Check # 1433,,100,,,,,
K002,Sep 15,Deposit,1900,,,,,,
K002,Sep 16,Transfer to savings 3334411,,500,,,,,
K002,Sep 21,Check # 1434,,475,,,,,
K002,Seo 23,Check # 1435,,30,,,,,
K002,Sep 30,Deposit,2000,,,,,,
K002,Sep 30,Interest Paid,5,,,,,,
S001,3334411,13990,15000,0,10,1000,0,,
S002,Sep 2,Transfer from checking 519-346-8,500,,,,,,
S002,Sep 16,Transfer from checking 519-346-8,500,,,,,,
S002,Sep 30,Interest Paid,10,,,,,,
D001,998123-B,19900,20000,0,100,5,5,"November 6, 2005",17000,,
H001,233-0124,199000,200000,,400000,201000,1000,250000,30,6.5,1400
C001,Manny,Ortiz,5424 WintercreekDrive,Suite 200,Glen Allen,VA,23060,Sep 1,
    Sep 30,September,1,30,2005
D001,168123-B,19900,20000,0,100,5,5,"November 6, 2005",17000,,
H001,933-0124,199000,200000,,400000,201000,1000,250000,30,6.5,1400

Based on the data model, NA batch identifies where each data block begins. In this example, the C001 record indicated the start of each data block.