This special process is designed to scan and find files with a specific extension in a specified folder, and to write a CopiaFacts FS file to initiate the further processing of the file. It is intended to allow CopiaFacts scripting to be used to find and process any types of file dropped in the folder by user applications. Multiple instances of this special process can be configured to handle output from different applications.
Enter the file pattern to be scanned for, and the folder, in the setup dialog; for example *.doc* to find .DOC and .DOCX files.
The folder to be scanned must have a subfolder named TEMPLATES in which FST files should be stored to act as a template for the creation of the FS file. The file Default.FST in this folder will be used as the default template for processing files found in the scanned folder. Before the FS file is written, the file found in the scan will be moved to CALLBACK\TEMP and referenced in the generated FS file in this position.
A custom template file can be selected by arranging for its filename part to be a prefix for the name of the scanned file, separated by an underscore. If the template name is all-numeric and has fewer than eight characters, it will be extended to eight characters with leading zeros. So for example a file found in the scan named 1234_987654321.DOCX would use 00001234.FST as its template file. When this syntax is used in the filename, the prefix and underscore are removed before the file is moved to CALLBACK\TEMP.
The following variables are placed at the top of the generated FS file:
| FSG_PATH | The full pathname of the file which has been moved to CALLBACK\TEMP |
| FSG_TEMPLATE | The filename part, without extension, of the template file |
| FSG_FILENAME | The filename part, with extension, of the file to be processed |
A $fax_user command in the template file will overwrite a user profile entered on the process setup screen.
