Event Manager

Overview

  • The event manager can be opened from the scanner view by tapping the button with the ticket icon in the upper right corner.
  • The event manager can be used to create new events or edit existing events.
  • An event may hold a certain number of tickets, which can then be distributed to guests or attendees in order to perform accreditation or admission control at the venue.
  • If desired, an individual layout can be defined for the tickets using the integrated ticket designer (see section "Ticket Designer").

Managing Events

  • Existing events will be displayed in a list grouped by their status, which can be "active" or "inactive".
  • New events can be created by tapping the "plus" icon in the upper right corner.
  • By "swiping left" on a list entry, more options will be displayed ("delete", "activate" and "deactivate").
  • Tapping on an entry opens the event's details view. Here you can specify the event's title and a short info text to be printed on the tickets.
  • In addition, further optional properties such as the validity period can be set.
    • The validity period may be defined for the entire event or for each ticket individually (in the ticket details view).
    • If both values are set, either the overlapping of the time periods or primarily the restriction of the event applies (in case there is a conflict).
    • Selecting "Ignore Time" limits ticket labeling and validation to the date (e.g. for all-day events). If time and/or date are to be used exclusively for labeling, date verification can be turned off for Ticket Validation in the Settings.
    • The "Dating Mode" will determine the type of text output for the date label (see section "Tickets with Date Label").

Using Tickets

  • The ticket validation can be carried out either with tickets that were generated and designed entirely by the app or with tickets that were created externally.
    • For the latter, tickets must be provided with compatible barcodes. The identification numbers (validation IDs) contained therein must have been imported into an event in advance.
  • Events have to be marked as "active" in the event manager in order to have their tickets taken into account when performing ticket validation tasks.

Tickets with Date Label (Dating)

  • If events and/or tickets are provided with a start or end date, a date label ("dating") can be printed.
  • The type of dating can be defined individually for each event using the "Dating mode".
  • The modes "Expression" and "Listing" are available as presets.
    • Depending on the information available in each case (e.g. start and end time, number of days), a corresponding output is automatically compiled for every ticket using various text blocks.
    • If changes to the wording of certain text blocks are desired, these can be adjusted in the event's details in the "Dating" section under "Formats".
    • Certain formats contain a placeholder (represented by three consecutive dollar signs "$$$"). These placeholders must be kept, i.e. appear at least once within the text block. If a placeholder is missing, it is automatically added at the end.
  • Another alternative is to define a dynamic labeling pattern in the "Custom" dating mode.
    • A dating pattern is a markup string consisting of text sections that can be enhanced with variables for inserting individual ticket data. In addition, certain tag sections for control structures (e.g. conditions) are available.
    • The associated editor can be accessed from the event details in the "Dating" area under "Patterns". The latter is only visible if the dating mode "Custom" has been selected in the section "Presets" at the top.
    • After entering the editor, the archive button (top left in the navigation bar) can be used to load and save your own patterns. In addition, sample patterns may be opened or the pattern of another event can be copied.
    • In the lower area of the editor is a text field for entering the pattern. The upper area features a preview window, which displays the result of the pattern output.
    • If the event already contains tickets, this data will be used for the preview. If the event does not contain any tickets yet, sample data will be used. The ticket or example can be switched using the arrow buttons (top right in the navigation bar).
    • Markup tags may be inserted with the "Variable" and "Control" buttons. When tapped, a popup menu opens, which displays the available options for selection with a brief description of their particular functionality.
      • Each control tag is available in the variants "wrapping" and "non-wrapping". Their respective function is identical, but wrapping tags may offer better readability, e.g. for longer patterns, because each condition can be written on a new line and hence allows structuring.
      • In the final output, the contents of wrapping tags will be inserted directly into the preceding and following text without line breaks (if line breaks had been entered at these places in the pattern).

Data Export

  • If you wish to create a backup or if you would like to process the app-generated identification numbers externally, either ticket lists or complete events can be exported in CSV, JSON and XML format. It is also possible to reimport these files later.
    • Please add a demo event (see section "Samples & Demo Data") and export it if you would like to get a better understanding of the data structure.