Add S-360 tickets into TINXGO. Allowing spectators to see & use them into TIXNGO Wallet.

Open

The ticket injection process pushes the designated tickets to the TIXnGO system, and then to the wallets of the final users.

To activate it, create a schedule to choose which tickets to process.

Every 5 minutes.

Recommended value: 1000

This new feature has been built in order to be able to inject other products such as Services in TIXnGO.

For non-dated ticket injection, please set custom variables in the chosen product following the format on the following table. Then try to inject tickets, as usual, filtering by the product instead of an activity.

Comfort variable code	Format	Example	Injected field inside TIXnGO	Notes

Comfort variable code	Format	Example	Injected field inside TIXnGO	Notes
TIXAct	start_of_season end_of_season +1d/-1w dd/mm/yy hh:mm	start_of_season end_of_season 2w 22/10/23 21:15	activationParameters.time	If not defined, nothing special happens Parts in blue will be implemented with :  STX-128539 - Not dated ticket injection - implementation DELIVERED
TIXStart	start_of_season end_of_season +1d/-1w dd/mm/yy hh:mm	start_of_season end_of_season 2w 22/10/23 21:15	event.startTime	If comfort variable is not defined, then the value is taken from the start time of the performance or the start validity date of the ticket. Parts in blue will be implemented with :  STX-128539 - Not dated ticket injection - implementation DELIVERED
TIXExp	start_of_season end_of_season +1d/-1w dd/mm/yy hh:mm	start_of_season end_of_season 2w 22/10/23 21:15	event.expirationDate	If comfort variable is not defined, then the value is taken from the end date of the performance + duration (or +24 hours if duration not defined), or the end validity date of the ticket. Parts in blue will be implemented with :  STX-128539 - Not dated ticket injection - implementation DELIVERED

Further information and more detail:

As this schedule must mark some tickets as printed, as if it had been done by a point of sales, you must set up (once) the sales channel and point of sales codes that will be used for that task.

Open

Many filtering options exist by-product(s), by performance(s), by tariff or category code... They are all cumulative (AND logical relation)

Allows adding a prefix/post-fix to the barcode

Open

This one is exclusive to all the other ones. If a file number (file id) is provided, it will exclude all the other fields.

Open

Please enter here one or many of the following values, separated by commas

FIRSTNAME,LASTNAME,BIRTHDATE,ID_NUMBER,COUNTRY_CODE,BIRTH_REGION,BIRTH_PLACE

Only the tickets having those beneficiary values filled will be sent to TIXnGO.

Open

Will send the main applicant flag to true to TIXnGO only when the beneficiary's first name, last name and email  (and NOT the cultural contact's) are matching those of the buyer.

Open

If this box is checked, the tickets won't be sent to TIXnGO.

If file or contact filter are selected, only the tickets associated to the file (resp. tickets associated to the contact) are exported.

When using the  ticket template editor to inject tickets, you must configure the following on the Technical tab.

Check the custom ticket details and put {"":""} in the fields.

Open

Please refer to that specific page on how to use the ticket template editor for TIXnGO.

1. The tickets are assigned to the person defined in the spectatorDetails data pushed to TIXnGO, identified through its email.

2. By default, the tickets are assigned to the cultural contact, with fallback to the purchaser contact..

3. But, IF the tickets has been reprinted, it will be assigned to its last known holder, as retrieved from TIXnGO.

The tickets are pushed ordered by ticket id. This likely means that ticket from a same order will come together.

If the TIXNGO interface has not been created or configured, please refer to S-360 to TIXNGO interface > 0. Initial setup of the interface

Once the basic configuration is completed, go the Schedules screen and click New button.

Select the function you want, in this case "Ticket external printing" to add and Click Next.

Open	Field	Mandatory	Description
	Internal name	Yes	Name for this function
	Launch	Yes	Either Manual or Automatic In case Automatic is selected, it's necessary to configure Frequency, Start, End
	Frequency	Yes*	Mandatory only if Automatic schedule Simple integration Advanced integration (high perf) "non-event" day  Every 5 minutes To be discussed with SECUTIX experts "event" day Every 5 minutes To be discussed with SECUTIX experts
	Batch Size	No	Simple integration Advanced integration (high perf) "non-event" day  1 000 To be discussed with SECUTIX experts "event" day 1 000 To be discussed with SECUTIX experts
	Point of sales (salesChannelCode;posCode)	Yes	Tickers are marked as PRINTED once successfully injected into TIXNGO, therefore, knowing that S-360 Ticket Printing can only be done by a Point of Sales, this field must be setup (on
	Tickets filters
	Sales Channel of Origin
	Season
	Product family
	Product
	Activity
	Event/Competition
	Performance
	Tariff
	Logical Category Code
	Contingent(s)
	Shipment modes
	Settle files only
	Mandatory ticket holder fields
	Mandatory question codes
	Set mainApplicant flag
	Barcode format	No	Allows adding a prefix/post-fix to the barcode
	Contact number
	File numbers
	Technical
	Custom ticket details
	Ticket main (JSON config)
	Ticket extra (JSON config)
	Other
	Fill only required fields before template overlay
	Simulation mode	No	Default: Unticked (aka false) If ticked (aka true), the
	Skip non seated tickets
	Ticket template
	Maximum number of tickets per contact
	File to upload	No	Will parse the attached file and process it as it was to TIXNGO  USE WITH CAUTION  Not suitable for day-2-day operations with an Automatic schedule In case of an automatic schedule, the same tickets will be sent over and over again.