Versions Compared

Old Version 36

changes.mady.by.user Irene PÉREZ VELASCO

Saved on

compared with

New Version Current

changes.mady.by.user Antonio PEREZ DIAZ

Saved on

Key

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

...

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:

...

Warning
titleConditions for a ST to be renewed

1. Does not Change Tariff mapping (e.g. a young person, can pass to an adult; hence it would new a new ST card) matches with both old ST and new ST that will be renewed.

2. Do not change the seat   Seat (same area mapping, block mapping, seat row, seat number) matches with both old ST and new ST that will be renewed.

3. Same cultural contactcontact  matches with both old ST and new ST that will be renewed.

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

...

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.

MessageCauseAction
[External error] Ticket with id 101729574868 [Barcode: 676852034024835003760168] could not be synchronized. The expected ACN is 7063357 but the one received is 7063358. Please open a Support ticket.

Consequences of a legacy bug in barcode generation. Some wrong ACN are still in the database, but we cannot identify them in advance.




Will be definitely solved with that JIRA

Jira Legacy
serverSecuTix JIRA Tracking System
serverIddb7e2039-f715-3f84-b1ed-ba058a819c06
keySTX-130152

In between, execute the following script:

Ticket with id ticketId [Barcode: xxxxxx] could not be synchronized. The expected ACN is expectedACN  but the one received is 7063358. (----).

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


TicketID 101835793445 could not be synchronized due to error: H For ProductCode T23C02-1 GameNumber is 179 but GameNumber extracted from the barcode is 180The ID mapping of the performance did change between the time when the barcode was generated and the time when the synchronization occurred
  1. Add the id to the list of skipped ids
  2. Have the operators reprint the ticket
  3. Communicate to the operators the importance of having the ID mappings rightly set up

[External error] Ticket with id 101812059516 [Barcode: 251146686039192242229055,Container Identifier: 244242,MemberID: 30034444] could not be synchronized due to the provided Membership ID was not found in the Fortress System. Please open a support ticket to investigate this issue.

Data issue, member id is missing in additionnal_info table.


  1. Fix this by script (not needed after this jira)
[External error] Ticket with id 101853377597 [Barcode: 070056601236163218016034,Container Identifier: 245819] could not be synchronized due to multiple card with the same Member Id. Ask Fortress support to fix this on their side.Error on Fortress side. Cause unknown.
  1. Contact Fortress as indicated. In-between, add the ticket ids to the ignored tickets list.
Warning: product T23C02-1 could not be synchronized due to error: H Membership is not Active (FGB_Web)This error message is due to the fact that the tickets has already been synced when V1 of the interface was active.
  1. Do nothing

[External error] Ticket with id 10228770369548 [Barcode: 245051249011197162072689] could not be synchronized: Turnstiles supplied in WS call WD - 18, service supplied inside the barcode 15

N/A

Contact with Fortress support, the issue is on their side.

support@fortressgb.com



Frequent Asked Questions (FAQ)

...