Default Template File

When used to create a fax or e-mail directly (that is, without FN= on the action line) FFMERGE operations are specified by the entries in an FS Template file, which is used as the basis of each generated FS file.  The default template file is named DEFAULT.FST, and resides in the TASKS folder below the FFMERGE local output folder (normally C:\FFMERGE).

If you upgrade from FFMERGE version 7, a DEFAULT.FST file is created for you from the 'template items' in the FFMERGE configuration. These formerly appeared in FFMRGNT, but no longer do so.

A typical template file would contain the following items:

; DEFAULT.FST

; select convert TIF to PDF for e-mail attach ("yes" or "")

; and format of PDF conversion ("yes" or "")

$var_def        FFM_EmailToPDF    yes

$var_def        FFM_PDFA4         ""

; specify name for e-mail attachment file

$var_def        FFM_ImgName       "results.pdf"

; specify TOSEND priority (can override with TS= on action line)

$fax_tosend     4

; select record of transmission in your STATUS file ("yes" or "")

; and name of user to be selected

$var_def        FFM_MonitorStatus yes

$var_def        FFM_MonitorUser   "Steve"

 

; specify USR whose $image_locn will be used to find Attach files

$var_def        FFM_UserPath "\\M1\COPIA\FAXFACTS\FAX.USR

$var_def        FFM_EMUserPath "\\M1\COPIA\FAXFACTS\EMAIL.USR

 

; set standard default settings

$fax_user       @FFUSER\FAX.USR

$email_subject  "Attached PDF file"

$fax_sender     "Steve Hersee"

$var_def DATA5  "@ROUTETO"

$var_def DATA2  "FFMERGE"

$var_def DATA1  "FFMERGE"

Variables with names FFM_ ... defined with $var_def in the template file control various details of the generated output syntax: for more details of the FFM_ variables, see Appendix D.

The template should also include the other FS commands such as $fax_user or $email_from which you want to have transferred to the FS files generated for the task.

Task-Based Template Files

Unlike in earlier releases, it is no longer necessary to set up all the template items (using FFMRGNT) for a single merge operation.  Instead, you can run several completely different types of merge operation in succession, or even at the same time, without having to set up parameters immediately before performing a merge.

To do this, you need to pre-specify a Task, and a template for it, and then simply select the task from the FFMERGE action line.  To save space on the action line, you can use single-letter task names, although this is not essential.

For example, you could set up the following separate tasks:

a mail merge to e-mail with settings in C:\FFMERGE\TASKS\E.FST

a mail merge to e-mail with a PDF attachment with settings in C:\FFMERGE\TASKS\P.FST

a mail merge to fax with settings in C:\FFMERGE\TASKS\F.FST

Then when you create the document to be merged and its action line, you can select the task name using the T= element on the line.  For your fax merge, you would need:

Once the F.FST task template file has been set up, you can then run this merge at any time.  In a Terminal Services environment, different users could run different tasks concurrently. A merge action line without any task selection will use the DEFAULT.FST template.