JetTrac SetVariables


Extracts data out of an XML file and populates variables in JetTrac JobController so any step in a job can use those variables to create files and documents.

Technical Support:

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

When to use:

When you need to use XML data to name files within a JetTrac JobController job.

Configuration file:

An INI file that specifies the XML field name and the Variable name you want to assign to the value in that XML field.
For example:
There can be any number of variables

These variables can then be used in JobConfig with the format “@JetTrac_FacilityName.” to reference the data saved from the XML to name files, write to the log, etc.


• JBC.VARS (built-in executable within JobController
• Input XML file
• INI file with mapping of XML fields to Variable names

Job Step Configuration Window in JobConfig for JetTrac SetVariables:


When setting up a job step using JTSetVariables in JobConfig the only lines of the config you need to worry about are the first and the second to last, the Config file and the Input file. 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 input file you want to create variables with. All other fields should be filled with the fully qualified path to the intended file. Eg: C:\JetTrac\…\input.xml
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.

Sample command line:

JBC.VARS Test.xml C:\JetTrac\JobController\Server\Config\VARS.ini

This command line starts with a built in executable within Job Controller, followed by an XML file defining the varialbles and then the file path to the VARS.ini file. Each part concerning a file is the fully qualified file path, and every part of the line is in quotes and separated by a space (it doesn’t matter how many)