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.

Recommended frequency

Every 5 minutes.

Batch size

Recommended value: 1000

Non-dated ticket injection

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 variables affecting TIXnGO data.

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 - Getting issue details... STATUS
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 - Getting issue details... STATUS
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 - Getting issue details... STATUS

Further information and more detail:

Point of sales configuration

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.

Filtering

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

Barcode format

Allows adding a prefix/post-fix to the barcode

File number filtering

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

Mandatory ticket holder fields

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.

Main Applicant

Will send the mainApplicant 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.

Simulation mode

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

File and contact filter

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

Customization of data sent to TIXnGO using the template editor

If you use the ticket template editor to inject tickets, you must not configure the following on the Technical tab.

Check the custom ticket details, if you want to send the custom ticket details defined in the two parameters below (put {"":""} if you want to empty them)

/wiki/spaces/CF/pages/40576543 TIXnGO.

To which contacts are the tickets assigned?

The tickets are assigned to the person defined in the spectatorDetails data pushed to TIXnGO, identified through its email.
By default, the tickets are assigned to the cultural contact, with a fallback to the purchaser contact..
But, IF the tickets have been reprinted, it will be assigned to their last known holder, as retrieved from TIXnGO.

In which orders are the ticket pushed?

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

Push cancelled and invalidated tickets

This batch pushes the cancelled and invalidated tickets to TIXnGO.

The tickets pushed are all the ones that:

Have been injected
Have been cancelled/invalidated
Comply with the filter (shipment mode)
Have not been already pushed by that function for that given interface

Recommended frequency

Every 5 minutes.

Date from

Can be used to force the sending of all cancelled tickets as if the last successful execution of the function was on the given date...

Do not use it if you don't understand clearly the usage, it may trigger thousands of unwanted notifications on remote cell phones.

Batch size

Recommended value: 1000

Push controlled tickets

This batch pushes the controlled status of the tickets to TIXnGO

The tickets pushed are all the ones that:

Have been injected
Have been controlled
Comply with the filter (shipment mode)
Have not been already pushed by that function for that given interface

Recommended frequency

Every 5 minutes. Can run every minute during the event.

Date from

Can be used to force the sending of all controlled tickets as if the last successful execution of the function was on the given date...

Do not use it if you don't understand clearly the usage.

Batch size

Recommended value: 1000

Retrieve ticket status from TIXnGO

This function retrieves information from TIXnGO about the ticket holder and stores it inside SecuTix.

Only the batch size not already handled tickets are retrieved from TIXnGO.

Only one function "retrieve ticket status from TIXnGO" must run for a given organizer, regardless if tickets are injected from multiple organizations.