...
- Seatmap inside SecuTix and Fortress Gb has to se synchronized:
- same area codes + block codes + row + seat number
- Secutix Area matches with Fortress Stand
- Secutix Block matches with Fortress Area
- SecuTix outer perimiter entrance codes must match with Fortress gates' codes
- SecuTix inner perimiter entrance codes must match with Fortress turnstiles' codes
- Product + Tarriff + XXX codes have to match between SecuTix and Fortress GB
- When a ticket is created, Fortress generates
- a standard barcode, which is stored in SecuTix ticket's barcode and in ExternalManagerMovement barcode field.
- an Adult barcode, stored in external manager movement externalValue2 field, which is then available on ticket editor with field named zzz_customParameter02
- a Concession barcode, stored in external manager movement externalValue3 field, which is then available on ticket editor with field named zzz_customParameter03
- a ticket identifier,stored in external manager movement ticketReference and externalValue1 field, which is then available on ticket editor with field named zzz_customParameter01
- When a season ticket card is printed, secutix stores season start and season end dates in card validity dates
{"serverDuration": 174, "requestCorrelationId": "f21d4fc0499d47939be13c656c947548"}