| Table of Contents |
|---|
Objectives
...
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 : |
...
Please enter here one or many of the following values, separated by commas
FIR,LASTNAME,BIRTHDATE,ID_NUMBER,COUNTRY_CODE,BIRTH_REGION,BIRTH_PLACE
Only the tickets having those beneficiary values filled will be sent to TIXnGO.
...
Check the custom ticket details and put {"":""} in the fields.
Please refer to that specific page on how to use the ticket templ TIXnGO.
To which contacts are the tickets assigned?
...
| 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
| |||||||||
...