Pre-prepared faxable TIF files can be named on $job_document commands.

When using Job Administration IVR, the master TIF document can be faxed in by the originator during an IVR session, with an optional proof faxed back for confirmation.  The $job_document command should have the keyword FAXIN in the filename parameter.

SingleDoc: If the $job_options keyword of 'SingleDoc' is given, then multiple separate faxable files will be faxed as a single document.

A TIF file can be customized for each recipient by overlaying variable data defined in a graphical customization file (GCT or GTT).  In this case the $job_document command should name either a GCT which references the TIF as a watermark file, or a GTT filename.

When using Job Administration IVR, the 'watermark' or background TIF for the customization can be faxed in by the originator during an IVR session, with an optional proof faxed back for confirmation.  The $job_document command should have the keyword WATERMARK in the filename parameter.

SingleDoc: If the $job_options keyword of 'SingleDoc' is given, then multiple separate faxable TIF files will be faxed as a single document, using a GCT or GTT file supplied on a separate $fax_cover command, if present. This feature allows the recipient to receive a document which appears to consist of customised 'headed stationery' and customised 'continuation pages', and which is built from separately submitted $job_document items. If the GCT file specifies a watermark file, or if a GTT file is given as a cover sheet, the referenced watermark document will precede any faxable TIF files.

PreConvert: If the optional Document Converter feature is installed, the $job_document filename parameter can specify the name of a supported document filename, such as .DOC .PDF, etc.  The $job_options keyword of 'PreConvert' should be given so that the system will determine if the document can be pre-converted once to TIF format before the job is launched.  Otherwise a separate conversion operation will need to be performed for each document.

One or more instances of FFEXTERN must be running, no more than one on each machine, with access to the CopiaFacts application data area.  The appropriate applications (e.g. Microsoft Word, Adobe Reader) must be installed on these machines, and the CopiaFacts Document Converter printer driver must be installed.

Two types of convertable document can be customized before conversion to fax format, when either a .DOC (or .RTF) file or a .HTM (or .HTML) file appears on the $job_document command:

WordMerge: Word documents (.DOC or .RTF) prepared for a normal printed Word merge operation can be supplied together with one or more data source files in a format supported by CopiaFacts Job Administration for broadcast lists. The $job_options keyword of 'WordMerge' should be given so that the system will determine automatically whether the document contains merge fields. One or more instances of FFEXTERN must be running, no more than one on each machine, with access to the CopiaFacts application data area. Note that because Word must be loaded to process each item, this feature is expensive on conversion resources. The job launch will fail if the header fields are different in multiple supplied broadcast lists, or if any merge fields in the Word document are not available in the data source.

HtmlExpandVars: HTML documents can contain variable names preceded by the e-mail variable introducer, which defaults to accent grave (`). These will be substituted in a single pre-conversion operation provided they do not include BCFx, JOB_ITEM or other per-item variables, in which case a separate conversion operation will need to be performed for each document. The $job_options keyword of 'HtmlExpandVars' should be given so that the system will determine automatically whether the document contains variables.