API Summary Documentation: SPD0102_API_Summary_Ticketing(REST) 1.47.doc

...

It will generate a Fortress barcode for all the tickets linked to a seat linked to an area mapped to Fortress through an access control mapping (see below). Else it will generate a Date SecuTix barcode.

Concession barcode

Fortress tickets may have two barcodes, one being the concession barcode, displayed in template using key exr_fortress_concession_barcode

...

Important: if neither of these two methods is used, the concession Barcode will not be generated, but the ticket purchase will still work. This new barcode will be stored in an external reference related to the movement. It can be seen in the ticket details screen.

Restrictions related to smart barcode

Fortress barcode can only be used for seated sales. It is not possible to sell passes with Fortress, nor to do sales in "without seating" mode.

Access Control Interface:

...

• Fill area and block mappings, for every area and block of the stadium/venue that will be controlled by Fortress.
• Check that the physical configuration code is the same as the stadium code defined in Fortress.
• Check that the entrances' codes are the same as the gate codes defined in Fortress.
• Mappings are defined only in the access control interface. The printing interface must be linked to the access control interface.

Important: Mapping of Concepts

...

Advanced: useful Webservices to know Fortress IDs

For people expert in using postman, it is possible to get codes, ids or even create some entities using Fortress Webservices.

Tariffs: Get Price Band List (POST)

...

Product printables: Select season tickets for the current season.

It is possible to filter by product:

Image Added

If non-ticket is selected: All will be printed.

Season: Select season, by default current.

Product family: To filter by family → Membership or Season Ticket

New Season ticket Renewal

When printing the ST Cards through the Tickets' external printing Function, on External Printing Interface, ST will be automatically renewing the same cards; if the renewal is not possible, New ST Cards will be printed for the Fans.

A new specific section added → Previous season ticket to renew:

Image Added

Image Added

Season: The season of the ticket that will be renewed.

Product family: Season ticket

Product to renew: Specific season tickets to be renewed.

Print from multiple printers

In order to be able to print from multiple printers, the current Virtual printer Code will be able to process tickets, printing them from more than one printer at the same time. Conditions as follows: 

Image Added

the code is taken from the Logical name from the printer fro fortress in Organization> Inisialisation> Worksation> Hardware

Image Added

1. Add printer codes separated by comas in Virtual printer Code current field.
2. Season tickets will be printed grouped by order from lowest to highest number.
3. Each printer will be printing per order, not for individual Season card. When starting to print an order it Will be finalized always by the same printer.

*Please consider that this feature just works for mass printing, if a ticket it is printed from the file, make sure that the Printer logical name for direct printing  matches with the printer chosen for printing and reprinting tickets from the file.

Access control interface - frequent error message

Due to the complexity of the interface and the integration and the absence of idempotency, the following error messages are likely to show up.

update ticket
set additionnal_info='ACN=expectedACN'
where ticket_id=ticketId;

Frequent Asked Questions (FAQ)

Why are Tickets compared between Secutix and Fortress?

The new parameter which compares a list of tickets between Secutix and Fortress within the synchronize tickets schedule in Access Control Interface (Please refer to Ticket Synchronization schedule) has been created because none of the Fortress Services are idempotent. That means that, when calling a Fortress Webservice in multiple occasion, execution will fail because tickets would have been added previously to FT system

How does work the parameter to synchronize tickets for a specific match?

 The mandatory parameter, located on the Access Control Interface (Synchronize ticket schedule) “Event and performance” to synchronize ticket for a match follows the format: eventCode;DD/MM/YY hh:mm

...

Filtering by this parameter, just tickets from the specific match will be called in Fortress System.

Why is a ticket not present in Fortress when I print it during the purchase order, as it was the case with V1?

Even if a ticket has been printed on Secutix while a purchase has been completed, operator will need to use access control  interface and synchronise the tickets to call Fortress system and push the ticket on FT system. This will allow Secutix to communicate fortress that a ticket has been sold for the chosen match.

How Can I validate that Access control Interface is working properly?

1.Sell a ticket for each stand (STX = Area) of the venue, wait depending of Schedule synchronization ticket, check that those tickets can pass the gate in Fortress.

...

In case it where not working, check the error logs in the executions and work out until the tickets are accepted/are refused at the gates.

How can I validate that External Printing Interface is working properly?

1. Sell a season ticket mapped to Fortress and print it on the Fortress printer. It must be printed by the Fortress printer (check in the execution logs for errors if it does not print)
2. Add an additional match on this season ticket, wait depending of Schedule synchronization ticket and see if the ticket can pass the gate (it should). If it does not pass, check in the access control logs to find the error.

Is it possible to purchase by unnumbered seats?

Yes, it is possible to add in the configuration an "unnumbered seat area", and when purchasing the ticket select this area tickets.

...