Page History

...

However, SecuTix doesn't recommend this option since it breaks the fixed seat logic. Indeed, the box office will automatically switch to this logic if no seat is available for all the performances sharing the same physical configuration.

The seat map will select by default:

• The preferred seat of the selected contact(s) if the information is available
• Otherwise, the best seat (i.e. the seat returned by the best seat selection feature)

Preferred seat

After the purchase process, the selected seats are stored as preferred seats. For a given contact, there may be one preferred seat per physical configuration. If a preferred seat already exists for the given contact and physical configuration, it will be overridden by the newly selected seat. Preferred seats may be viewed in the Contact module with the new menu entry Preferred seats. The operator may delete a preferred seat, this action having no impact on the purchased tickets. Preferred seats are only stored during a purchase process. They can't be defined directly from the screen below.

...

However, SecuTix recommends to keep the default behaviour unless you need to handle very specific cases.

This parameter only impacts the renewal of fixed seat season ticket.

Other new parameters

The renewal batch may be run in reservation only mode. More precisely, the Create reservation field proposes following values:

• Always: a reservation is systematically created (no sales order)
• Never: a reservation is never created. In other words, the batch tries systematically to create a sales order and, in case of payment failure or shipment information missing, no order is created at all
• If payment fails: the batch tries to create a sales order and creates a reservation if payment fails or shipment information is missing

Current restrictions

...