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 Stad
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
| SecuTix concept | Fortress GB concept | Mapping data type | Mapped value |
|---|---|---|---|
| Performance | ProductDescription. | Performance | Product description's code |
| Season Ticket | ProductDescription | Product | Product description's code |
| Tariff | Price band | Audience sub category | Price band code |
| Physical configuration | Stadium | Physical configuration | Stadium code |
| Area | Stand | Area | Stand code |
| Block | Area | Block | Block code |
| Entrance | Service | NA | NA |
- 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's behavior.
Batches
- Read catalog : reads all the objects information accessible from Fortress system and dumps them into the logs. Read only batch.
- Check mappings : compares the mappings defined in SecuTix with the objects in Fortress. Throws an error if a mapping is missing. If a mapping is missing, SecuTix cannot guarantee the system's behavior.
Miscellaneous
- 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
Setup screen capture
