JetTrac Annotation Extract

Introduction:

This will create a log of all annotations on all pages found in a PDF Document. The main purpose is to create a file of all annotations that can be used in a PDF review workflow process. It can also be used for diagnostic and debugging purposes.

Technical Support:

If you need assistance in installing and configuring JetTrac Annotation Extract™, call Pro Technology Automation, Inc. at 805-527-1248 or email us at support@protechinc.com. Please note that the JetTrac Annotation Extract™ 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 JetTrac AnnotationExtract:

To run the program, you will need to have the following files located in the same folder:

  • JTAnnotationExtract.exe
  • ExitHandler.dll
  • DebenuPDFLibraryDLL1112.dll

The JTAnnotationExtract.exe, ExitHandler.dll, and DebenuPDFLibraryDLL1112.dll are files required for the program to run and should never be edited.

Default Functionality:

JetTrac AnnotationExtract takes an input PDF file containing any annotations and outputs an XML file with a list of all annotations found within the PDF.

Job Step Configuration Window in JobConfig for JetTrac AnnotationExtract:

When setting up a job step using JTAnnotionExtract in JobConfig the only two lines of the config you need to worry about are the last two, the Input PDF and Output XML. If left as an asterisk * the input will be whatever file is in the data folder that triggered the job running. This works well if it’s the first step but if the input is also the output of a previous job step you would need to specify the fully qualified path of the file you want to extract the annotations from. 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 BYODJobConfig page.

JetTrac AnnotationExtract Command Line:

The command line to run JetTrac AnnotationExtract contains the location of the executable, the input PDF file, the output log file. The following is an example of the command line used to run this module:

“C:\JetTrac\Programs\JTAnnotationExtract\JTAnnotationExtract.exe” “C:\Input.pdf” “C:\Output.xml” “C:\JTAnnotationExtract.log”

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 begins with the path to the module’s executable file and is followed by the path to the input file, the path you want to give to the output file it creates and then the path to the log file to track the progress of the module. Each command line ends with a short description of what the module does in quotes. For this module the input file is a PDF and the output is an XML.