...
As for SecuTix 360, the TixNGo system is perceived as an external printing system. Tickets injected into TIXnGO are considered as printed.
Note |
---|
In case of multi organization, the organization must be set up in the organization owing the inventory of the tickets (the organization where the catalog is defined) |
To set it up:
1.) In Organization/Tools/Interfaces create a new External Printing Interface of type "TIXnGO" or "TixnGO with ticket template" (If you want to use the Ticket Template Editor to custom the data send to TIXNGO TIXnGO Customization of the data injected by SecuTix)
...
Prepare your ticket template and use this template when scheduling a Tickets external printing function
Example: event.name = ${Performance_hostTeam} - ${Performance_opposingTeam}
Other available multilingual fields:
TIXNGO name | S-360 Ticket template config name | S-360 usually uses variables | Translated values come from |
---|---|---|---|
Event group name | event.group.name | ${Product_externalName} | Organisation > Catalogue > Ordinary admissions > Competition |
Event group image | event.group.image | Static URL | Multilingual value has not been supported in S-360 yet but can update this value in TIXNGO |
Event name | event.name | ${Performance_hostTeam} - ${Performance_opposingTeam} | Organisation > Initialisation > Organisation parameters > Teams |
Event website | event.website | Static URL | Multilingual value has not been supported in S-360 yet but can update this value in TIXNGO |
Event address site | event.address.site | ${Space_externalName} | Institution > Venue > Venue parameters > Space |
Event address city | event.address.city | ${Site_externalName} | Institution > Venue > Venue parameters > Sites (General) |
Event address line1 | event.address.line1 | ${Site_street1} | Institution > Venue > Venue parameters > Sites (Address) Multilingual value has not been supported in S-360 yet but can update this value in TIXNGO |
Event address line2 | event.address.line2 | ${Site_street2} | |
Event address line3 | event.address.line3 | ${Site_street3} |
Set up multilingual ticket detail values in the ticket template
TIXNGO name | S-360 Ticket template config name | S-360 usually uses variables | Translated values come from |
---|---|---|---|
Ticket details main | ticketDetails.main.<sequence>.key | Static values | Multilingual value has not been supported in S-360 yet but can update this value in TIXNGO |
ticketDetails.main.<sequence>.value | ${Hospitality_seatRoomName}, ${External_Entrance_externalName}, ${Entrance_externalName}, ${Seat_block}, ${Seat_row}, ${Seat_nb},... | ||
Ticket details extra | ticketDetails.extra.<sequence>.key | Static values | Multilingual value has not been supported in S-360 yet but can update this value in TIXNGO |
ticketDetails.extra.<sequence>.value | ${LogicalSeatCategory_externalName}, ${Operation_field}, ${Ticket_taxnumber}, ${Amount_currency} ${Amount_baseUnitAmount}, ${Contingent_externalName} | ||
Ticket details hidden | ticketDetails.hidden.<sequence>.key | Static values | Multilingual value has not been supported in S-360 and TIXNGO yet |
ticketDetails.hidden.<sequence>.value | Any values |
*sequence: the order of information will be displayed on TIXNGO, the sequence is started from 0 and is independent in each section.
...