S-360 Documentation

Page tree

Versions Compared

Old Version 1

changes.mady.by.user VLA

Saved on

compared with

New Version 2

changes.mady.by.user LKL

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

  1. Seatmap inside SecuTix and Fortress Gb has to se synchronized:
    1. same area codes + block codes + row + seat number
      1. Secutix Area matches with Fortress Stand
      2. Secutix Block matches with Fortress Area
    2. SecuTix outer perimiter entrance codes must match with Fortress gates' codes
    3. SecuTix inner perimiter entrance codes must match with Fortress turnstylesturnstiles' codes
  2. Product + Tarriff + XXX codes have to match between SecuTix and Fortress GB
  3. When a ticket is created, Fortress generates
    1. a standard barcode, which is stored in SecuTix ticket's barcode and in ExternalManagerMovement barcode field.
    2. an Adult barcode, stored in external manager movement XXX externalValue2 field, which is then available on ticket editor with field named ZZZ_???
    3. a concession barcode, stored in external manager movement YYY externalValue3 field, which is then available on ticket editor with field named ZZZ_???
    4. a ticket identifier,stored in external manager movement TTT ticketReference and externalValue1 field, which is then available on ticket editor with field named ZZZ_???

...