Ticket Configuration and Overview

Owned by Nathan Bergeron (Unlicensed)
Last updated: Jan 10, 2022 by Heidi Adams
3 min read

Overview

A ticket format 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.

Types of Information

Tickets may contain the following types of information.

  • Ticket Sections (Header, Body, Footer)
  • Static Text
  • Database Fields
  • Flag Fields
  • Printer Commands
  • Horizontal and Vertical Positioning
  • Images and Logos

Ticket Sections

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.

Format CharacterDescriptionSample

#

Comment - This comments out the whole line. Can be used anywhere in the ticket file as long as it's the first character of a line in the ticket.# Test comment.

H

Header - All header formatted lines will print first on the ticketH [HPOS] "2.5" "Account: " [Account Name]

B

Body - All Body lines will print for each item when there is a multiple item ticket and the B lines will printer after the H - Header lines.B [HPOS] "2.5" "Material: " [Material Description]
FFooter - All Footer lines will print after the B - Body lines.F [HPOS] "2.5" "Signature:______________"

Static Text

Static text fields are contained in double quotes ("). 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 in the Flag Fields section of the Ticket Keywords page.

Printer Commands

Every printer has its own set of commands. Refer to the printer manufactures documentation for additional information.

Horizontal and Vertical Positioning

Commands used to align text and database fields on a printed ticket. Instructions to use horizontal and vertical positioning commands can be found on the Font and Positioning Commands page.

Images/Logos

Images can be added to a ticket design using the following command format: {IMAGE "filename,Horizontal,Vertical,Width,Height"}. In order for an image to be added to a ticket the file must be uploaded into the database.

Images can be uploaded by selecting Setup | Configure - Static Images or by clicking the  Modify static images button in the Ticket Design window.

Additional examples can be found in the Static Images and Dynamic Images section of the Ticket Keywords page or the Sample Tickets page.

Ticket Priority and Custom Ticket Designs

Other ticket files can be created and used as custom tickets. Click the above link to learn more about custom tickets and ticket priority.

Related Links

Table of Contents