Add S-360 tickets into TINXGO. Allowing spectators to see & use them into TIXNGO Wallet.
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 |
|---|---|---|---|---|
| TIXAct | start_of_season | 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 : |
| TIXStart | start_of_season | start_of_season | 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 : |
| TIXExp | start_of_season | start_of_season | 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 : |
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.
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
This one is exclusive to all the other ones. If a file number (file id) is provided, it will exclude all the other 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.
Will send the main applicant flag to true to TIXnGO only when the beneficiary's first name, last name and email (and
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.
If you use 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.
Please refer to that specific page on how to use the ticket template editor for TIXnGO.
The tickets are pushed ordered by ticket id. This likely
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.
| 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
| |||||||||
| Batch Size | No |
| |||||||||
| 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 (once) and contains the codes of an existing sales channel & point of sales codes. | |||||||||
| 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 function will realize all the steps ( tickets retrieval, properties mapping, template usage, ...) but won't send tickets to TIXnGO. | |||||||||
| 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
| |||||||||
