Ticket Extentions
Interact uses file extensions to perform different functions; the file extension will tell Interact if the ticket should print for an outbound transaction or an inbound transaction or an unattended transaction. Standard ticket files have a .GTK extension.
Outbound vs. Inbound
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.
To print a different incoming ticket than outgoing ticket, the filename must match, only the extension will be different. In the examples below, TicketSample will be used as the filename. The ticket will print on the same printer as the outgoing ticket. The layout of each ticket can be entirely different.
- .GTK - This format file will be used for completed Outbound transactions (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 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 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 Net = 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 ticket will not be printed.
When Net > zero, Interact recognizes the transaction as an Outbound transaction. Interact will search for a .UTK version of the ticket filename (TicketSample.UTK). If a .UTK extension does not exist, Interact will search for a .GTK version of the filename. If a .GTK version exist, Interact will attempt to print this ticket. If a. GTK extentiosn does not exist, an error condition will occur.
Journal Ticket Extensions
The Journal Ticket feature was originally designed to be used as a printed transaction backup. It is now used as a second printer. When the Ticket Printer and Journal Ticket Printer are in use two different ticket designs can be printed to two different printers at the same time.
Examples:
- Unattended Ticket prints outside at the Kiosk, Journal ticket, prints inside on a laser printer.
- Attended Ticket prints on a local laser printer, Journal ticket is used to email a ticket to the Bill-To.
- Unattended Ticket prints outside at the Kiosk, Journal ticket is used to email a ticket to the Bill-To.
Journal ticket extensions follow the same rules as regular ticket extensions. Typically Journal ticket filenames are different from the standard ticket filenames. In order to print an inbound and outbound journal ticket, the filename must be different from the standard ticket filename (TicketSample in our above examples).
- .JTK - This format file will be used for completed Outbound transactions (JournalSample.GTK).
- .ITK - This format file will be used for Inbound transactions when a transaction is started (JournalSample.ITK).
Attended and Unattended Mode
When the Interact printing routine is initiated, Interact will determine if the transaction is an Inbound or Outbound transaction. If the transaction is an Inbound transaction (Net = 0), Interact will search for a .ITK version of the ticket filename (JournalSample.ITK) and print a ticket. If a .ITK extension does not exist, an inbound ticket will not be printed.
When Interact determines the transaction is an Outbound transaction (Net > 0), Interact will search for a .JTK and print a ticket. If the .JTK does not exist an error condition will occur.
Enable Incoming Ticket Print
To enable Incoming Ticket Printing, select Setup | Weigh Options - Ticket Printing.
JournalNameFromTicket - Is this in REv. 7?
System Default and Custom Ticket Designs (new page)
Other ticket files can be created and used as custom tickets. To use a specific ticket for a particular customer, truck, or truck type, design the ticket and give the ticket a meaningful name. Select the account, truck or truck type then select the custom ticket filename from the available drop-down list. Click the 
Save button to continue. To undo any changes click the 
Undo button.
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
- Ticket Keywords