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.
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.
Click the 
Save button to continue. To undo any changes click the 
Undo button.
| Note | ||
|---|---|---|
| ||
A ticket format file created using a text editor such as Notepad, can be imported into Interact. Once the file has been imported additional modifications can be made to the ticket using Ticket Editor. 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; the file extension will tell Interact if the ticket should print for an outbound transaction or an inbound transaction or an unattended transaction. Go to the Ticket Extensions page to learn more about ticket extensions. |
Ticket Design
Types of Information
Tickets may contain the following types of information.
- Static Text
- Database Fields
- Flag Fields
- Printer Commands
- Column Positioning
- Images and Logos
To accommodate multiple item transactions, the ticket is split into three sections: header, body, and footer. Header lines are printed once before the first transaction item. Body lines are printed once per transaction item. Footer lines are printed once after the last transaction item. Header lines are designated by the letter 'H' in the first character position of the format line. Body lines are designated by the letter 'B' and footer lines by the letter 'F'. Each section letter must be followed by a space.
Any format line without a section identifier is considered a header line.
Static Text
Static text fields are contained in double quote ("). Any desired text character enclosed in the double quotes, spaces included, will appear on the ticket.
Database Fields
Database fields that are stored in the Interact database. A database field is placed on a ticket by enclosing the field name in square brackets ([ ]). A list of available database fields can be found on the Ticket Keywords page.
Flag Fields
A flag is set in the database whenever a special condition has been met by a transaction. A list of available flag fields can be found on the Flag Fields page.
Printer Commands
Every printer has its own set of commands.
Column Positioning
Images/Logos
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
| Panel | ||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| ||||||||||||||
|