Introduction:
For more sophisticated reporting requirements for repeating data elements within a PDF form.
Technical Support:
If you need assistance in installing and configuring JetTrac DBLogicUpdate™, call Pro Technology Automation, Inc. at 805-527-1248 or email us at support@protechinc.com. Please note that the JetTrac DBLogicUpdate™ 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 DBLogicUpdate:
To run JTDBLogicUpdate, you will need these files in the same folder:
- JTDBLogicUpdate.exe
- ExitHandler.dll
Executable files and dll files should not be edited for any reason.
Default Functionality:
Update whole sections of PDF forms into multiple rows in a SQL table.
Job Step Configuration Window in JobConfig for JetTrac DBLogicUpdate:
When setting up a job step using JTDBLookup in JobConfig the only two lines of the config you need to worry about are the Config file and the Input 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 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 Field ServiceJobConfig page.
JetTrac DBLogicUpdate Command Line:
Sample command line:
“C:\JTDBLogicUpdate.exe” “C:\data.xml” “C:\config.xml” “C:\file.log”
The command line begins with the module’s executable file followed by the input xml, the xml config file and then ends with the log file. 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)
JetTrac DBLogicUpdate Configuration.xml:
<?xml version=”1.0″ encoding=”UTF-8″?>
<form1>
<xData_Base_ID>C:\Users\Dean\Dropbox\protech\c#\DbLogicUpdate\TankTest.accdb</xData_Base_ID>
<Data_Base_ID>TankTest@LCDEMO</Data_Base_ID>
<Data_Base_SQL>Y</Data_Base_SQL>
<Data_Base_User_Name>Matt</Data_Base_User_Name>
<Data_Base_Pass_Word>2828cochran</Data_Base_Pass_Word>
<Action ID=”MultiAdd” Table=”TankTest”>
<FieldName Column=”Fac_ID”>FacilityName</FieldName>
</Action>
</form1>