In case of S-360 integration, S-360 is the Master for tickets issuing, meaning that once a ticket is issued and injected to TIXNGO, we must insure that, at any time, tickets statuses are aligned between both tools.

Summary of the possible actions on a ticket in a S-360 integrated TINXGO context

Overview of the interface

The interface provides 4 functions :

• Tickets external printing pushes the designated tickets to the TIXNGO aka "Tickets injection".
• Retrieve ticket status from TIXNGO retrieves information from TIXNGO about the ticket (status, holder) and stores it inside S-360 aka "Feedback interface".
• Push cancelled and invalidated tickets pushes tickets that have been cancelled or invalidated since the last execution to TIXNGO in order to remove them from the spectator's Mobile Wallet.
• Push controlled tickets pushed tickets that have been controlled since the last execution to TINXGO in order to hide the QR code from the spectator's Mobile Walle

Configuration of the interface

Global / Custom Parameters

The interface behaviour can be tweaked by using Custom Parameters. These parameters are defined in the General tab of the interface

Image Added

For the full list of available parameters, please refer to the section "Custom parameters" of the official page or click here.

Injection

S-360 is able to customize the json data sent to TIXNGO using a specific ticket template that contains all the formatted data.

Through the ticket template editor’s predefined syntax, configure custom variables which will then be mapped to TIXNGO Ticket Injection JSON variables and overwrite the data previously set via the comfort variables and the ticket injection batch interface.

For more details on the available variables, see the page Understand S-360 variables for tickets Injection