Page History

Versions Compared

Key

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

...

Identified seat based on origin season ticket

Identified seat based on preferred seatIdentified seat based on best seat allocation in same seat categoryActionRationale
Same physical configuration in target and origin season ticket
Found seat in new physical configuration with same area, row, seat number
Seat is availableSeat has same categoryInfo is available
Seat is availableSeat has same categorySeat is available

YesN/AYesYesN/AN/AN/AN/ARenew season ticket with identified seat
YesN/AOne (or more) of the conditions isn't metN/AN/AN/AN/ADon't renew this season ticketThe end customer expects to reuse the same seat but it isn't available or its category (and, therefore, the price) has changed. The venue must take contact with the end customer.
NoYesYesN/AN/AN/AN/AN/ARenew season ticket with identified seatSince the physical configuration is different, the end customer doesn't expect to keep the same seat category
NoYesNoN/AYesYesYesN/ARenew season ticket with identified seat
NoYesNoN/AYesOne (or more) of the conditions isn't metYesRenew season ticket with identified seat
NoYesNoN/AYesOne (or more) of the conditions isn't metNoDon't renew this season ticket
NoYesNoN/ANoN/AN/AYesRenew season ticket with identified seat
NoYesNoN/ANoN/AN/ANoDon't renew this season ticket
NoNoN/AN/AYesYesYesN/ARenew season ticket with identified seat
NoNoN/AN/AYesOne (or more) of the conditions isn't metYesRenew season ticket with identified seat
NoNoN/AN/AYesOne (or more) of the conditions isn't metNoDon't renew this season ticket
NoNoN/AN/ANoN/AN/AYesRenew season ticket with identified seat
NoNoN/AN/ANoN/AN/ANoDon't renew this season ticket

The batch will proceed in two different steps:

  1. It will first renew all season tickets that can reuse the same seat (same physical configuration or other configuration containing a seat with the same area, row and seat number).
  2. In a second step, all renewals requiring a seat change will be performed

The goal is to avoid following scenario:

  • A first season ticket uses seat A that has been marked as invalid. The batch allocates seat B
  • A second season ticket uses seat B that has been allocated in the mean time for the first season ticket. As a result, seat C is allocated to this season ticket
  • A third season ticket uses seat C...

By default, the batch will perform both steps mentioned above. You may change this behavior by adding the custom parameter renewStrategy. This parameter may have 3 values:

  • BOTH: performs steps 1 and 2
  • NOT_PROCESSED_SSTK: the batch performs only step 1 and stores the season ticket requiring a different seat in a temporary table
  • PROCESSED_ERROR_SSTK: the batch performs only step 2 based on the content of this temporary table

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

Image Added

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, no order is created at all
  • If payment fails: the batch tries to create a sales order and creates a reservation if payment fails

Image Added

Current restrictions

Warning
titleCurrent restrictions

The fixed seat season ticket can only be purchased from the box office

...