Published — v. 1
/
Introduction to Tickets V4

Introduction to Tickets V4

Owned by Julie BONNARD
Dec 03, 2024
2 min read

Hybrid release note

ZUM V4 release marks a significant step toward the new API version implementation. While screens are not yet available (their implementations will come later in this release and also in RIM V1 and V2), this article focuses on presenting the functional changes that will accompany these substantial technical advancements.

New Ticketing Business-oriented tickets

TIXNGO tickets v4 now include business-focused data by default. Alongside the classical ticket identification (ticket number, ticket external id, barcode, ….) we promoted the following properties:

Purchase Details

Seating Details

Advanced Seating Details

Purchase Details

Seating Details

Advanced Seating Details

  • purchaseDate

  • fileNumber

  • purchasePrice

  • purchaseCurrency

  • seatCategoryId

  • contingentId

  • tariffId

  • seated (Y/N)

  • numbered (Y/N)

  • gate

  • level

  • area

  • block

  • row

  • seat

  • physicalSeatId

  • companionSeatId

  • salesSeatId

  • leftSeatId & rightSeatId

  • frontSeatId & backSeatId

  • seatQuality & temperature

  • xcoord & ycoord

Please note:

  • These “business-oriented” properties are automatically injected by S-360, removing the need for custom mapping in the template.

  • While you can still use the standard MAIN, EXTRA, and HIDDEN key-value pairs to extend ticket content, TIXNGO back-office and mobile screens will focus on prioritizing and highlighting these business-oriented properties.

New ticket statuses, attributes and state machine

With Ticket V4, status will reflect where the ticket is (on the phone, not on the phone, in transit). Other pertinent info previously existing as individual status have been promoted as attributes.

Status

  • NOT_DOWNLOADED -  Ticket has been injected in the system (S360, CSV or API) but not yet downloaded to any device

  • DOWNLOADED - Ticket has been downloaded at least once on Spectator device.

  • PENDING_TRANSFER - Transfer has been initiated and not yet accepted by recipient.

  • DELETED - Ticket has been deleted by issuer. Ticket might still be present in some devices until synchronization is completed.

Attributes

  • Activated (boolean) - if the ticket has been activated at least only once since latest deactivation

  • Checked (boolean) - if the ticket has been checked

  • Controlled (boolean) - if the ticket has been checked in since latest check out

State Machine

image-20241203-103249.png
TIXNGO Ticket V4 - New state machine

New Ticket Status Log

Ticket Status Log (formerly known as Ticket History or Lifecycle) have been rearchitected to optimize back-end processing, and track all mutations applied to the ticket, no matter the origin (mobile, back-office, S-360) or the trigger action (injection, transfer, deletion, …).

Ticket Status Log aims to fulfil the following needs

  • support operations: provide a mean to understand what has been the lifecycle of a given ticket.

  • interact with mobile device and offer the ability to transmit only updated information.

  • support transfers by providing transfer keys for pending transfers.

© TIXNGO 2023 - Login