Using overrides

You can either specify resources used by the template in Designer in the Publish for EngageOne task or by using an override production settings (OPS) file; this allows you to specify supplements and alternatives to some of the job settings that were used in Designer. Note that the use of overrides is valid only for templates run Express Batch processing mode.

An example OPS file is shown below:

<input>
Datainput=C:\NABatch\SET2\data\Letters-ORG.xml

<KeyMap>
Showroom=ACompanyxml
Showroom=C:\key\keymap4.xml

<LookupTable>
Dealers=C:\NABatch\SET2\data\Dealerships.ETS

<Output>
Default PDF=c:\myoutputs\SET2\ACompany-KeyedImages-Lookuptables.pdf

<DIJ>
AFP300=c:\myoutputs\SET2\1.jrn

<trace>
Outputfile=c:\myoutputs\SET2\Trace.out

TraceLevel=Complete 
; TraceLevel=default
; TraceLevel=verbose
; TraceLevel=off

OutputCodepage=UTF8
memlimit=0

Supporttrace=on
; supporttrace=off 

For a complete list of OPS file settings, refer to OPS file reference section of the latest EngageOne Designer User's Guide.