TTicket Check Batch Upload Process

Ticket Check® Availability of Processing Ticket Batches

 

Availability for Processing Batch Files

Some Facility Operators will prefer an automated method of providing status to responding to individual tickets by hand.  To give these Facility Operators an alternative, Ticket Check® provides an “upload” feature for the processing of batch files.  Uploading batch files is a great way for larger Facility Operators to handle large quantity of tickets, and allows a single login to submit responses for multiple district codes in a convenient fashion as well.

This on-line processing feature is available by selecting Ticket Management on the navigation bar then selecting Batch Upload.  This utility is available for all Facility Operators and requires no special set-up from OCC Personnel.  The only requirement is that the file must be formatted correctly (as specified in the following) in order for it to be batch processed.  If you want to load this page by default upon logging in, go to the Administration and make Batch Upload your default page.  For additional information regarding administration, see that section below.

 

Batch Upload File Format

The key to using this feature is creating a correctly formatted batch file.  Files need to be named with the extension of .mn to be processed.  The filename should be login_mmddyyhhmm.mn.  Files should contain one ticket per line to be statused and must have the pattern shown in Table 1.

Field	Size	Description
Ticket Number	8	The ticket number to be statused.  If the ticket number is less than 8 characters in length then it should be left-padded with zeroes.
Status	1	The number of the status the ticket is to be set.  The available statuses are 1 (Cleared/No Conflict), 2 (Marked), 3 (Marking will be Delayed), and 4 (Not Complete/In Progress).  No others will be accepted.
District Code	1-8	The associated district code that is to be statused.  The login ID for the user MUST have permission to update the district code.

Table 1 – Batch File Format for On-line Processing

This means than an example batch file should look something like this:

704015741ATTCLC01

704047592ATT01

703705673ATTLCL01

704022614TEST01

704050853COMCST01

703938704ATT01

 

As stated previously, this file shows that each entry is on a single line.  This sample also illustrates how multiple district codes can be handled within the same file.  The key is that the user logged in must have permission for each of these district codes. 

 

Processing a Batch File

In the example provided here, the user will have the previous batch file processed on-line.  This is done by logging into the system selecting Ticket Management on the navigation bar then selecting Batch Upload.  Once there, the user can upload a file by either typing in the complete path name of the location of the file on their computer or by browsing for the file by clicking the Browse button.  Once the file has been selected, the screen should look like Figure 1 shown below. 

Figure 1 – File Selected for Batch Upload

Now, to have the file processed, simply click on the Process File button.  This will cause the file to be uploaded and processed in real-time.  This means that the results will be available as soon as the system has finished with the file.  The results are shown in Figure 2.

Figure 2 – Results of File Being Processed with Batch Upload

There are several pieces of information contained in the results file.  First, the summary of the success of the uploaded file is displayed.  In the above example, there are 2 successful updates and 4 failures.  Below this summary, a table with the details of the files is listed.  This shows which tickets failed and are accompanied by an error which lists the reason.  The reasons for failure are as follows:

Results Code	Description
00	Success
01	Ticket does not exist.
02	District Codes does not exist.
03	Response is unknown value.
04	District Code is not valid for Ticket Number.
14	Unknown system error.
15	Illegal attempt to status ticket cancelled by excavator.
16	Login ID does not have permission to status District Code.
18	Ticket is already locked.
19	Operation Timed Out. Recommend Retry.