Expliquez quand ces informations sont utiles. Par exemple "lorsque vous vous connectez au réseau Wi-Fi pour la première fois".

General Principle

Fortress GB provides two very distinct and different functionalities.

• Providing barcodes for single match tickets
• printing (and re-reprint, and canceling) season ticket cards.

Beware : Fortress GB is not the same system as the Fortress (=StadAccess) used at Stade de France. Although they are related (they are both access control systems), their behavior in SecuTix is entirely different.

General setup of the interface

See example below in screen capture. Here are the explanations of the parameter.

• Synchronous, Export contact..., bypass contact : put "false". Not used in Fortress GB
• URL : url of the fortress GB at Everton, provided by Fortress GB team.
• Login, password, Agency code, client App Id, Client API Key : values necessary to connect, provided by Fortress GB team.
• Shipment modes codes w/o Fortress barcodes generation : if a tickets shipment mode code is one of those (comma separated), no call will be done to Fortress GB for barcode generation.
• Fortress MemberId for anonymous contacts : when SecuTix buys a ticket for an anonymous contact, the following memberId is passed to Fortress GB.
• Use virtual printer : for season ticket printing. The value "Virtual" is passed as printer code to Fortress GB.
• Season codes for which season ticket card printing is authorized : as explained. Season codes must be separated by commas.
• Forcing season ticket card reprint. Renewal on same card impossible. As explained. 

Definition of mappings

• Concerning product mappings : Fortress matches are mapped to SecuTix performances. But, in an external manager context, we must create a mapping for a product in ordre to tell SecuTix that this product is handled by Fortress GB. In consequence, every event or competition must be mapped to a value of -1, not used by Fortress GB, but indicating that this product is "managed by" Fortress GB.
• If no mapping is defined for the tariffs, physical configurations, areas, blocks and entrances, the object's code will be transmitted to Fortress.
• All the mappings must be defined (run batch "check mappings" to check that point). If a mapping is missing, SecuTix cannot guarantee the system behavior.

General Principle: Fortress GB generates the barcodes and prints the Season Ticket cards

this has some impacts:

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 turnstiles' 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 externalValue2 field, which is then available on ticket editor with field named zzz_customParameter02
   3. a Concession barcode, stored in external manager movement externalValue3 field, which is then available on ticket editor with field named zzz_customParameter03
   4. a ticket identifier,stored in external manager movement ticketReference and externalValue1 field, which is then available on ticket editor with field named zzz_customParameter01
4. When a season ticket card is printed, secutix stores season start and season end dates in card validity dates