This option delivers FormTrap standard output files to a specified
directory, as well as the opportunity to run processes over the
FormTrap output.
To set the properties of output to file:
- Enter the full Destination
folder path of where to save the file to. Environment
variables are accepted. See notes following the image below if you are
attempting to write to a network drive.
- Enter the File title.
Use an associated file variable by quoting the associated file name in
square brackets "[" and "]". For example quoting [PO
Num] would deliver “PO22344”
from the associated file line PO Num=PO22344.
Make sure that your data fields do NOT contain characters that are
illegal for Windows file names, (*\.: and so on).
These may cause the file save to abort, with an error message.
More information on Using
Associated Files in FTSpooler Queues Properties
- Select any standard files you wish to add
to output. There are three types of standard files: Output
file (PostScript (.ps) or PCLXL (PCL6) or PCL5 (.pcl)), Associated
file (.af) and Input file
(.txt).
- Click Add/Remove to
edit which (if any) output conversion filters should be used to add
additional files (commonly .pdf files).
More information on Define Output Filters
-
Click the Apply
button to save the changes.
Notes on writing
to network drives:
When the output folder is located on a network, both a UNC path
(\\server\folder) or a mapped drive (Z:\Folder) may be used.
Mapped drive(s) must exist for the user account that runs the FormTrap
service (drive mappings are maintained per user account). Please check
by interactively logging in as the user that runs the FormTrap service.
The drive(s) should be mapped permanently. If you are running the
FormTrap service using a LocalSystem account you will not be able to
log in as the user account running the FormTrap service and will
not be able to output to the mapped drive.
In both cases you need to ensure the user account that runs the
Formtrap service has sufficient privileges to read and write to the
required folder.
Drive errors as above show up in the Archive, Errors list as (for
example) "Z:\Folder is not a directory. " when that
folder exists.
|
|
