Introduction:

Used in production jobs to control space by removing unneeded/irrelevant documents

Technical Support:

If you need assistance in installing and configuring JetTrac FileDelete™, call Pro Technology Automation, Inc. at 805-527-1248 or email us at support@protechinc.com. Please note that the JetTrac FileDelete™ license fee does not cover configuration services and technical support so there may be an additional charge. Please ensure you read these instructions carefully before calling for technical support.

How to run JetTracFileDelete:

There are actually 2 versions of JetTrac FileDelete, one built-in to JobController and another from an executable. The built-in version can only be run through a job in JobController and is easier to setup, the executable can be run both ways.

Default Functionality:

Server side production deleting of files and documents.

When setting up a job step using JTFileDelete in JobConfig the only line of the config you need to worry about is the second to last, the File to delete. The field should be filled with the fully qualified path of the file to be deleted. Eg: C:\JetTrac\…\input.pdf
In JobConfig, file paths entered should not be in quotes.

As with all modules, there is a dropdown to select whether or not the job should stop completely if this step fails. If you select Yes, any error will terminate the job process and write to the log file what happened, if no, then the job will try to continue anyways. However if any steps further down the line rely on the output of a job set to not stop on error, they may not work properly.

For more specifics go to the JetTrac Field ServiceJobConfig page.

JetTrac FileDelete Command Line:

Within JobController job:

!x FileDelete * C:\JetTrac\Programs\JTFileDelete\JTFileDelete.exe “””@MDFName.”” “”@LogFile.””” “Runs FileDelete”

Each part of the line is divided by spaces (the amount doesn’t matter), and contains the fully qualified file path to the file you are referencing surrounded by quotes.
The command line for FileDelete consists of the file path to the module’s executable file, followed by the path to the file that is desired to be deleted as well as the path to the log file. The line ends with a short description of what the module does.