Introduction to Tickets V4
- Julie BONNARD
New ownership-related ticket properties: Initial & Previous Owners
TIXNGO tickets v4 now include standardized ownership properties:
current owner (improved since V3)
initial owner (improved since V3)
previous owner (in case of ticket transfer)
These new Ownership fields will be visible from the V4-version of the Support Ticket screen.
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 |
|---|---|---|
|
|
|
Please note:
These “business-oriented” properties
are automatically injected by S-360, removing the need for custom mapping in the template.
will be visible from the V4-version of the Support Ticket screen.
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.
Ticket Status
Status | Description |
|---|---|
| The ticket has been injected (via S-360, CSV, or API) but not yet downloaded to any device. |
| The ticket has been downloaded at least once to a spectator's device. |
| A transfer has been initiated but not yet accepted by the recipient. |
| The ticket has been deleted by the issuer. It may still appear on devices until synchronization is completed. |
Ticket Attributes
Attribute | Type | Description |
|---|---|---|
| Boolean |
|
| Boolean |
|
| Boolean |
|
| Boolean |
|
| Boolean |
|
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.
Please note that, despite the technical refactoring, the new Ticket Status Logs will be presented in a V3-style format, enriched with V4-only details and will remain visible from the V4 Support Ticket screen.
New Ticket Deletion Reasons
To simplify the invalidation logic inherited from S-360, TIXNGO V4 introduces its own set of 10 dedicated ticket deletion reasons, rather than retrofitting those from S-360.
This change streamlines both notification customization and manual ticket deletion from the TIXNGO back-office, offering a clearer, more consistent approach to managing deleted tickets.
Deletion Reason | Notification Template Key | Visible on Mobile |
|---|---|---|
|
| Yes, in the Deleted Items screen. Hidden if the screen is not enabled. |
|
| Yes, in the Deleted Items screen. Hidden if the screen is not enabled. |
|
| Yes, in the Deleted Items screen. Hidden if the screen is not enabled. |
|
| Yes, in Resale screens. Hidden if Resale screens are not enabled. |
|
| Yes, in Resale screens. Hidden if Resale screens are not enabled. |
|
| Yes, in Resale screens. Hidden if Resale screens are not enabled. |
|
| Yes, in the Deleted Items screen. Hidden if the screen is not enabled. |
|
| Yes, in the Deleted Items screen. Hidden if the screen is not enabled. |
|
| Yes, in the Deleted Items screen. Hidden if the screen is not enabled. |
|
| Yes, in the Deleted Items screen. Hidden if the screen is not enabled. |
© TIXNGO 2023 - Login