A ticket format file is used by Interact as a template for generating printed or emailed transaction tickets. Use the Ticket Editor to create and modify ticket format files.
Multiple ticket formats can be created. Within the Interact program, a system default ticket is selected. Unless otherwise specified, all transaction tickets will print using the default ticket. A different ticket format file, that will override the system default ticket, can be selected for an individual account or truck.
Must have .gtk to appear in Weight |Options list
To open the Ticket Editor, select Utilities | Ticket Editor. A window similar to the following will appear.
To create a new ticket design, click the 
New button. A blank form appears.
Enter a meaningful name and file extension for the ticket, TicketSample.gtk for our example.
| Note | ||
|---|---|---|
| ||
A ticket format file created using a text editor such as Notepad, can be imported into Interact. Additional Once the file has been imported additional modifications can be made to the ticket using Ticket Editor once it has been imported. Select Setup | Weigh Options to learn more. This is a great way to import ticket format files used in older revisions of Interact. |
| Info | ||
|---|---|---|
| ||
Interact uses file extensions to perform different functions; such as which ticket is to used for the file extension will tell Interact if the ticket should print for an outbound transaction or an inbound transaction or for an unattended transaction. Go to the Ticket Extensions page to learn more about ticket extensions. |
Ticket Extentions
This document defines the ticket types used by the Interact software and describes the order in which they are processed
Interact has been designed to use Interact uses file extensions to perform different ticket printing functionsfunctions; the file extension will tell Interact if the ticket should print for an outbound transaction or an inbound transaction or an unattended transaction.
| Info | ||
|---|---|---|
| ||
An Outbound transaction is a completed ticket where a value greater than zero (0) exists in the Net field (weight, yard, or unit count). An Inbound transaction is not a completed ticket. A value of zero (0) exists in the Net and Weigh Out fields. |
In order for the file extensions to work, the filename must be the same, only the extension will be different. In the examples below, TicketSample will be used as the filename.
- .GTK - This format file will be used for completed Outbound transactions when a transaction is being completed (TicketSample.GTK).
- .ITK - This format file will be used for Inbound transactions when a transaction is started (TicketSample.ITK).
- .UTK - This format file will be used for Unattended Outbound transactions. Most unattended kiosk systems come with a thermal ticket printer. The .UTK contains all of the printer commands necessary to print and cut a tickets ticket sent to this printer. Using this file extension in combination with the .GTK extension will allow a user to design and print tickets for attended transactions to one printer type (i.e. a laser printer) and unattended tickets to a different printer mounted inside a kiosk. A ticket will only be printed to the printer mounted in the unattended kiosk when the system is running in unattended mode (TicketSample.UTK).
- .WTK - This format file will be used for Unattended Inbound transactions. Most unattended kiosk systems come with a thermal ticket printer. The .WTK contains all of the printer commands necessary to print and cut a tickets ticket sent to this printer. Using this file extension in combination with the .ITK extension will allow a user to design and print tickets for attended inbound transactions to one printer type (i.e. a laser printer) and unattended inbound tickets to a different printer mounted inside a kiosk. A ticket will only be printed to the printer mounted in the unattended kiosk when the system is running in unattended mode (TicketSample.WTK).
Attended Mode
The Interact printing routine is initiated when the Store Ticket or Print Ticket buttons are clicked. Interact first looks for the ticket filename, TicketSample for our example. Interact will then determine if the transaction is an Inbound or Outbound transaction.
When the Store Ticket button is clicked, Interact recognizes this as an Inbound transaction (Net = 0). Interact will search for a .ITK version of the ticket filename (TicketSample.ITK). If a .ITK extension does not exist, an inbound ticket will not be printed.
When the Print Ticket button is clicked, Interact recognizes this as an Outbound transaction (Net > 0). Interact will search for the .GTK version of the ticket filename (TicketSample.GTK) and print a ticket. If the .GTK file does not exist, an error condition will occur.
Unattended Mode
The Interact printing routine is initiated when the Enter key is pressed on the unattended kiosk. Interact first looks for the ticket filename, TicketSample for our example. When the Net value is zero (= 0), Interact recognizes the transaction as an Inbound transaction. Interact will search for a .WTK version of the ticket filename (TicketSample.WTK). If a .WTK extension does not exist, Interact will search for a .ITK version of the filename. If a .ITK version exist, Interact will attempt to print this ticket. If a. ITK extentiosn does not exist, an inbound Inbound ticket will not be printed.
When the Net value is greater than > zero, Interact recognizes the transaction as an Outbound transaction. Interact will search for a .UTK version of the ticket filename (TicketSample.UTK).
when the Store Ticket or Print Ticket buttons are clicked. Interact first looks for the ticket filename, TicketSample for our example. Interact will then determine if the transaction is an Inbound or Outbound transaction.
When the Store Ticket button is clicked, Interact recognizes this as an Inbound transaction. Interact will If a .UTK extension does not exist, Interact will search for a .ITK GTK version of the ticket filename (TicketSample.ITK). If a .GTK version exist, Interact will attempt to print this ticket. If a. ITK extension GTK extentiosn does not exist, an inbound ticket will not be printed.
When the Print Ticket button is clicked, Interact recognizes this as an Outbound transaction. Interact will search for the .GTK version of the ticket filename (TicketSample.GTK) and print a ticket.
Ticket Naming Algorithm
error condition will occur.
Journal Ticket Extensions
Journal ticket extensions follow the same rules as regular ticket extensions.
| .ITK | Inbound Journal Ticket |
| .JTK | Outbound Journal Ticket (also see JournalNameFromTicket) |
Journal Ticket Naming Algorithm
Journal Ticket printing will choose the ticket name (excluding
suffix) of the file based on the following priority ranking:
- JournalNameFromTicket mode uses the file name selected from Ticket Printing
- Account Journal preference ticket
- Default Journal Ticket name
Interact will always send the ticket printing routine the name of the ticket format file with the correct extension. If that particular ticket format file does not exist, the following algorithm is used:
| .GTK | Not Found => Error Condition |
| . |
| JTK | Not Found => Use .GTK |
| .ITK | Not Found => Use .GTK |
Examples:
- If
- ticket.GTK and ticket.ITK both exist, then an inbound transaction will print using the ticket.ITK file.
- If
- ticket.GTK exists but ticket.UTK does not, then an Unattended Outbound transaction will print using the ticket.GTK file.
System Default and Custom Ticket Designs (new page)
Ticket printing will choose the ticket name (excluding the suffix) of the file based on the following priority ranking:
- Truck Preference Ticket
- Truck Type Preference Ticket
- Account Preference Ticket
- System Global Ticket
Block Unattended Journal (This feature is incorporated in the Block Tickets feature below)
*Must be Interact 6.4.1 or newer (not implemented in 5)* This feature will allow a ticket to only be printed to the Kiosk (set as Ticket printer port) in unattended mode when you have a Journal printer setup. Use the following INI setting:
[Weigh Options]
BlockUnattendedJournalTicket=Yes
Block Tickets
*Must use Interact 6.4.107 or newer (not implemented in 5)* This feature will block certain ticket conditions from printing.
INI setting: [Printer Settings] TicketBlock=(List of conditions)
A condition is a 3 character definition. If that condition is present, the ticket will be blocked.
First char (T)icket or (J)ournal.
Second char (U)nattended or (A)ttended.
3rd char (N)et present or (O)pen, Open tickets are tickets without a net weight.
Condition | Explanation |
|---|---|
| TUN | Unattended Net Ticket |
| TUO | Unattended Open Ticket |
| TAN | Attended Net Ticket |
| TAO | Attended Open Ticket |
| JUN | Unattended Net Journal |
| JUO | Unattended Open Journal |
| JAN | Attended Net Journal |
| JAO | Attended Open Journal |
EXAMPLE
TicketBlock=TUO,JAO
These two settings will block the ticket printer from printing
1) Unattended ticket printer printing a no net weight ticket
2) Attended journal printer printing a no net weight ticket
Journal Suffix Formats
Journal Ticket Naming Algorithm
Journal Ticket printing will choose the ticket name (excluding suffix) of the file based on the following priority ranking:
- JournalNameFromTicket mode uses the file name selected from Ticket Printing
- Account Journal preference ticket
- Default Journal Ticket name
Interact will always send the ticket printing routine the name of the ticket format file with the correct extension. If that particular ticket format file does not exist, the following algorithm is used:
Examples:
If ticket.GTK andticket
.ITK both exist, then an inbound transaction will print using the ticket.ITK file.If ticket.GTK exists but ticket.UTK does not, then an Unattended Outbound transaction will print using the ticket.GTK file.| Panel | ||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| ||||||||||||||
|