Introduction:

Translates data that comes from other systems to the field names in the PDF forms so the data can be pre-populated. Conversely, after the forms are filled out if the data needs to go back to some other system in a specific XML format then this module will do the normalization and translation.

Technical Support:

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

A bat file or job step in Job Controller can execute this module.
To run JTXMLNormalize you will need these files in the same file:

• JTXMLNormalize.exe
• ExitHandler.dll

Executable files and dll files should not be edited for any reason.

Default Functionality:

Normalize XML data coming from and going back to other systems. For example I want to be able to convert XML data from a PDF form that contains unique field names ending in _1, _2, etc. to normalized XML so the data can be fed to another system that requires normalized XML

Job Step Configuration Window in JobConfig for JetTrac XMLNormalize:

When setting up a job step using JTXMLNormalize in JobConfig the only lines of the config you need to worry about are the first and the last two, the Config file, the Input XML and the 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 input xml to be edited. All other fields should be filled with the fully qualified path to the intended file. 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.

JTXMLNormalize Command Line:

“C:\JTXMLNormalize.exe” “C:\JTXMLNormalize_Input.xml” “C:\JTXMLNormalize_Output.xml” “C:\JTXMLNormalize.ini” “C:\JTXMLNormalize.log”

The command line begins with the file path to the module’s executable file followed by the path to the input XML file, the desired path and name for the output XML file, along with the file paths to the config and log files. Each part of the command line is the fully qualified path to the file, in quotes, separated by a space (it doesn’t matter how many)

Sample Config File:

DetailFields=WorkerDate|WorkerTimeIn|WorkerTimeOut|WorkerHours|WorkerID|WorkerCharge|Page
DetailParentTag=Worker
SuperParentNode=WORKERS

Root names of fields in detail line, first one MUST be first one occurring in file
Parent node to place each detail line into

Additional Notes:

The INI file is key-value format and has two required keys.
1) A list of fields in the repeating detail section, without suffixes, in order from first to last, separated by a pipe symbol ( | )
2) The name of the parent node to create to contain each repeating detail section.
# root names of fields in detail line, first one MUST be first one occurring in file
DetailFields=ItemNumber|Quantity|Price|Desc
# parent node to place each detail line into
DetailParentTag=item