JetTrac PrepopSaveData

Introduction:

The following document will go through the functionality found within JetTrac PrepopSaveData. This module is used to along with JetTrac PrepopFieldList in order to prepopulate XML data from previous PDF submissions into future dispatched PDFs. This module inputs the .txt file saved from JetTrac PrepopFieldList and an XML data file extracted from a filled PDF form. It then outputs an XML file with the data from all fields listed in the .txt file from the XML data file.

Please note that any files edited while setting up JetTrac PrepopSaveData should be edited using Notepad or Notepad++. Do not use Microsoft Word or Wordpad as these text editors will add formatting that will interfere with the program reading the files.

Technical Support:

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

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

  • JTPrepopSaveData.exe

The file is required for the program to run and should never be edited.

Default Functionality:

JetTrac PrepopSaveData takes an input XML file with field data, and outputs an XML data file with the values from each field in the input that match the names of the fields specified in the input .txt file. All fields that do not match a field name found in the .txt file are left out of the output XML data file.

Job Step Configuration Window in JobConfig for JetTrac PrepopSaveData:

When setting up a job step using JTPrepopSaveData you will need to enter in an input .txt, an input .xml file, and an output .xml file.

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 PrepopSaveData Command Line:

The command line for JetTrac PrepopSaveData is as follows:
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.

C:\JTPrepopSaveData.exe “C:\output.txt” “C:\sampleIn.xml” “C:\Output.xml” “C:\JTPrepopSaveData.log”

In this we are referencing the executable file path, the input .txt file that was output from JetTrac PrepopFieldList (or created manually), an input XML file, an output XML file, and the log file.

Additional Notes:

This modules functionality is specialized to work in tandem with JetTrac PrepopFieldList in order to allow you to prepopulate “previous inspection” data. When set up, both modules work to save data from a specified list of fields on each returned inspection so that the next inspection can be populated with that data during the dispatch. You can then use JTXMLCombine to combine the output XML with the rest of the dispatch data to prepopulate forms with last inspection data.

You can use this module individually if you manually create and store the input .txt file. The format of the file is simply the exact name of the fields as they are in the XML data separated by a line break. You can look at the sample files for JetTrac PrepopFieldList to see this formatting.