Ticket Designer

Overview

  • The tickets of each event can be customized with an individual design by applying a self-defined layout.
  • You'll find these features in the event's details view when scrolling to the "Tickets & Design" section.
  • The layout options include adjustments for paper size, ticket dimensions or font sizes and the possibility of setting a custom logo.

Adding Tickets

  • The tickets of each event can be accessed from the event's details view by tapping the "Manage" button in the section "Tickets & Design" .
  • You may first create the tickets by using the "plus" icon and then edit them individually or as a block (using the "selection" button).
    • Alternatively, tickets (or even complete events) can be imported from a file in CSV, JSON or XML format.
    • Please add a demo event (see section "Samples & Demo Data") and export if you would like to get a better understanding of the data structure.

Customizing Tickets

  • Each ticket requires a unique identification number called "validation ID".
    • If the tickets are generated by the app, an appropriate ID will be assigned automatically. This ID is supposed to be unique (even across different devices).
    • If the database contains multiple tickets with an identical ID within all active events, an error will be issued when a ticket with this particular ID is scanned during ticket validation.
  • The identification number will appear in the form of a barcode on the ticket. The barcode's properties can be defined using the "Code Type" setting.
    • If "Auto" is selected as code type, any type of code is allowed during ticket validation (see also additional option "No Barcode Type Restriction" in the "Settings" section).
    • The default code type (usually QR code) will be used in "Auto" mode when outputting tickets.

Ticket Numbering / Implementing Seating Plans

  • When creating tickets, the ticket names can be enhanced with single or multi-level numbering.
  • This enables quickly creating tickets for seating plans with different areas, stagings or categories.
  • It is also possible to update the numbering of several or all tickets simultaneously by using the edit function after selecting the corresponding items in the ticket list.
Sequential Numbering
  • A basic sequential numbering will append a consecutive number to the default name.
    • This number reflects the ticket's index in the series of all tickets added to the event.
  • This numbering type requires to specify the amount of desired tickets.
Custom Numbering
  • The custom numbering is based on a pattern specification that can contain multiple variable fields for number and letter sequences or ranges.
  • As an example, the pattern "Row: [A-C] – Seat: [1-10]" generates a total of 30 tickets in rows A to C, each with seat numbers from 1 to 10.
    • The expressions in square brackets each represent an interval that is to be traversed when generating the tickets.
    • Any ascending series in the range of A-Z (uppercase letters), a-z (lowercase letters) and 0-10000 (numbers) are possible.
      • There is no explicit upper limit for number ranges. However, a system-dependent maximum number must not be exceeded. In this case, the app will issue a warning.
      • Numerical ranges can be prefixed with leading zeros, for example "[001-100]".
    • Alternatively, enumerations (separated by commas) consisting of ranges and any characters in any order are permitted, for example "[A,I,E,O,U,5,3,$,😀]" or mixed "[1-12,14-20,99,X]".
  • The use of multiple expressions within a pattern specification leads to nesting and multiplication of tickets.
    • Please note that this can quickly result in a very large number of tickets. In this case, the app will issue a warning.
  • If, in special cases, square brackets should actually appear in the name, the characters can be marked with a preceding backslash, for example "[" or "]".
    • This makes clear that the bracket does not belong to a range expression which is supposed to be traversed.

Layout & Page Setup

  • Multiple tickets can be printed together on one page. Alternatively, you can also output them as single tickets.
  • You may choose from standard paper formats or enter a custom page size.
  • For positioning the tickets on the page, the number of rows and columns can be specified. Furthermore, the page margins can be adjusted.
  • If the "Auto-Format" option "Single Ticket" has been selected, layout options and page sizes are automatically set to optimal values in order to create pages that fit exactly for a single ticket.
    • Manual changes to these settings are only possible if "Auto-Format" was set to "Off".

Design Template

  • A selection of predefined scheme types is available for customizing the template.
    • Alignment, width and height can be adjusted for each scheme type.
  • Every scheme has a field for logo, title, name, date and additional information.
    • Each field can be resized or hidden.
    • You may also insert a custom image or a logo.
  • In addition, every ticket will always contain a barcode. Position and content of the barcode are determined automatically.

Output

  • When generating an output, the template will be merged with the event's ticket data.
  • The fields on each ticket are filled with the corresponding record and a barcode of the selected type and with the specified content will be added.
  • The final tickets can either be printed directly (using AirPrint) or exported as a PDF if they shall be sent by email or are meant to be processed in some other way.
    • Tickets (or ticket sheets respectively) can be generated as multi-page documents or as separate PDF files.
    • You may also preview the ticket sheets directly in the app before generating the output.
  • Tickets can either be issued individually or in full for an entire event on multiple sheets.
    • If not all tickets should be contained (e.g. for reprints), these can be excluded from general output.
    • For this purpose, the "Included" flag in the "General Output" section may be removed (available in the ticket details and in the "Edit Tickets" dialog).
  • In the output dialog the image resolution can be selected at which logo graphics should appear in the PDF file.
    • Regardless of the selection, the result in the output cannot be higher than the resolution of the logo template.
    • The default resolution is 150 dpi.