NA batch and native input file support
NA batch supports the processing of keyed record and delimited-format data model types directly as input files. This eliminates the need for an XML processing file to provide control information for the non-XML data file.
Header value, template name, <effective date>, delivery option
The header value can be any character string you choose, but must be consistent after established within a data file and does not conflict with any of the data records.
The data file must begin with a header value record when the data file is presented to NA batch in native mode. This is true even if the NA batch process is launched with parameters that identify a template and delivery option. In this case, the control record could contain only the header value:
XXXXXXXXXXX,,,
In this
delimited-format native input file example, the first set of data is used by the
User-form template and delivered to
the PDF-BATCH delivery option. The second
and third sets of records are used to compose the same template, but are delivered
to the EMESSAGING-BATCH delivery
option.
XXXXXXXXXXX,User-form,2011-06-01,PDF-BATCH
001,Smith,"101, Princes Street",ED1 4DH
002,Debit,89.01,"Cash, charges apply"
XXXXXXXXXXX,,,EMESSAGING-BATCH
001,Smith,"101, Princes Street",ED1 4DH
002,Debit,89.01,"Cash, charges apply"
001,Smith,"101, Princes Street",ED1 4DH
002,Debit,89.01,"Cash, charges apply"Control information can also be embedded within the input data file to provide control information to NA batch. This is useful if you want to swap template or delivery option per customer. If this information is not provided, the parameters to the batch job can be used to provide these identifiers for the entire job. NA batch uses the specified template and delivery option for all records it is processing sequentially until a another processing instruction is found.
In this keyed record example NA batch requires that the
first record in the data file provide the header value to control information. Based
on this, if any data record within the data file begins with XXXXXXXXXXX then that record is considered a
control record and the remaining data can identify a delivery option, template name,
and template effective date. All of these values are optional after they have been
established. If no control record is provided between one data block and another, NA
batch assumes that the same template and delivery option are to be used as
previously defined. If some element of the control record is not provided, the same
rule apples and the previous value is maintained pending a subsequent
change.
XXXXXXXXXXX,insurance-application,,PDF-BATCH
100099756345Jack Laurence 945 Elm Street
PO Box 1324 Atlanta
1500 .13 180.05 09092000 168.27 168.27
8.32100920001200099931112400 180.05.00
2000EE1.1012434 10092000 35862 09092000 34812 1050 178.0810092000 343209092000 299830
2500E145610501120145613341120 987 992 818 754 768 887 9571010
3000GG1.1007135 10092000266551 09092000266537 14 1.50 15.97
3500 45 14 35 42 45 40 30 20 10 11 9 12 12 13
5000SS .1032312 10092000 46.00 09092000 46.00 10.00 56.00-DYNA
6000HH1.0023239 10092000 30.00 09092000 30.00 30.00
8000Msg3Msg4ALL
9999
XXXXXXXXXXX,insurance-application,2011-06-01,
100065445431Robert Jones 1431 Elm Street
Lanham
1500 .13 69.54 09092000 78.27 78.27 8.32100920001200099931112400 180.05.00
2000EE1.1012434 10092000 24500 09092000 23455 1045 1 69.5410092000 343209092000 299830
2500E16021045116013201602145412211032 956 949 852 833 957 923
3000GG1.1007135 10092000 12821 09092000 12807 14 1.50 15.97
3500 62 14 25 45 62 53 48 26 16 12 14 16 19 22
8000Msg1Msg4ALL
9999