JetTrac TransactionSummary

Introduction:

Creates a summary of the JetTrac transactions that have taken place.

Technical Support:

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

To run JetTrac TransactionSummary, you will need these files in the same folder:

  • JTTransactionSummary.exe
  • ExitHandler.dll

 

Default Functionality:

JobController writes an entry to a Transaction Detail file for every job. This module summarizes the Transaction Detail file into a summarized Excel file that can be used by customer management and for billing.

Job Step Configuration Window in JobConfig for JetTrac TransactionSummary:

transactionsummary.PNG

When setting up a job step using JTTransaction Summary in JobConfig the only line of the config you need to worry about is the first, the Config file. This field should be filled with the fully qualified path to the JTTransactionSummary Config file. Eg: C:\JetTrac\…\config.ini
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.

JTTransactionSummary Command Line:

“C:\JTTransactionSummary.exe” “C:\20150831_ISS_JTTransactionHistory.log” “C:\20150831_ISS_JetTrac_Summary.csv” “C:\JTTransactionHistory.ini” “C:\JTTransactionSummary.log”

The command line begins with the fully qualified path to the module’s executable file followed by the path to the input log file, then the desired path of the output csv file, it then ends with the module’s log file.

JTTransactionSummary Configuration.ini:

ExcludedJobs=HistoryLog,JBCError,tst_SubContractorOrderCorrected,tst_SubContractorOrderNew,tst_VendorPayments

ReportHeader=JetTrac Transaction Summary|Interface Security Systems

ColumnHeaderLabels=Job Name|Total Jobs|Successful #|Failed #|Date First Run|Date Last Run