This broadcast type combines fax and e-mail in a single broadcast. Broadcast list items which have a fax number in the specified 'destination' column will be processed as for an FB broadcast, and those which have an e-mail address in the same specified column will be processed as for an EB broadcast. An e-mail address is identified as follows:
•the value contains an @ sign
•the value contains a . to the right of the @ sign
•the value does not start with sip:
Each $job_document command which has no content-type parameter is processed as described in Plain Fax Broadcasts when the destination is a fax number. Any email-specific items from $fs_template items or generated in the FS file are ignored.
Each $job_document command which has a content-type parameter and a keyword of 'nofax' is processed as described in Plain Email Broadcasts when the destination specifies an e-mail address. Any fax-specific items from $fs_template items or generated in the FS file are ignored.
The processing of documents which have a content-type but are without a 'nofax' keyword is as described below:
Pre-prepared faxable TIF files can be named on $job_document commands and will be faxed to fax destinations.
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 files will be faxed as a single document to fax destinations.
If the content-type is image/tif the document will be sent as an e-mail attachment to e-mail destinations.
If the content-type is application/pdf, image/gif, image/gif or image/png, the TIF original will be converted to the appropriate format and will then be sent as an e-mail attachment to e-mail destinations.
|
A TIF file can be customized for each recipient by overlaying variable data defined in a graphical customization file (GCT or GTT) and then the document will be faxed to fax destinations. 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 files will be faxed as a single document, using a GCT or GTT file supplied on a separate $job_document command, if present. This feature allows the recipient to receive a document which appears to consist of customized 'headed stationery' and customized 'continuation pages', and which is built from separately submitted $job_document items.
If the content-type is image/tif the customized document will be sent as an e-mail attachment to e-mail destinations.
If the content-type is application/pdf, image/gif, image/gif or image/png, the customized TIF will be converted to the appropriate format and will then be sent as an e-mail attachment to e-mail destinations.
|
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. (see below for HTML). 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 for a fax destination.
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 (Microsoft Word, Acrobat) must be installed on these machines, and the CopiaFacts document converter printer driver must be installed.
Documents with specific file-types matching the content-type (i.e. .PDF with application/pdf and .DOC with application/msword) will be sent as attachments to e-mail destinations. A full list of these correspondences is shown under E-Mail Attachments.
If the content-type is image/tif the converted TIF document will be sent as an e-mail attachment to e-mail destinations.
If the content-type is application/pdf (for originals other than PDF), image/gif, image/gif or image/png, the converted TIF will be converted to the appropriate format and will then be sent as an e-mail attachment to e-mail destinations.
|
PreConvert: If the optional Document Converter feature is installed, the $job_document filename parameter can specify the name of an HTML file to be converted to TIF. 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 for a fax destination.
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 (Microsoft Word, Acrobat) must be installed on these machines, and the CopiaFacts Document Converter printer driver must be installed.
HtmlExpandVars: For e-mail destinations, the content-type of text/html is processed specially if the $email_options keyword ExpandAttachVars is given and the original document is also HTML. In this case the converted document is not used for e-mail destinations. Instead the variables are expanded as the transmission is made, in the same way that body text and alternate body text are expanded.
Note that unlike body text files, e-mail attachments are not cached in the transmission process, and in addition all attachments are base64 encoded. It is therefore slightly less efficient to use HTML attachments than it is to use HTML body text.
|
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 if 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.
A WordMerge operation is performed for all job items. If the destination is fax or if the content-type is image/tif, a TIF output file is produced and the customized, converted TIF document will be sent as an e-mail attachment to e-mail destinations. If the content-type is application/msword the customized Word document will be saved and sent as an e-mail attachment to e-mail destinations.
|
