S-360 Documentation

Page tree

Versions Compared

Old Version 1

changes.mady.by.user JMT

Saved on

compared with

New Version Current

changes.mady.by.user LBU

Saved on

Key

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

...

  • Files : you can input there the numbers of the filles to be handled by the batch if you want to run it on specific files
  • Simulation mode : when ticked, SecuTix will just check the configuration and not run the batch. To be used to make sure you did not forget anything.
  • Re-use existing files : gives the ability to set the different product renewed inside the same file. For instance, running a renewal on stadium season tickets with one execution of the batch, and then running the renewal for the parking season ticket will end up with 1 file containing the 2 products.
  • Multithread size : 8 4 is the maximum to be set. Numbers of files that the batch will process at the same time. Obviously running 8 4 files at a time will result in a batch running much quicker than running 1 at a time. Could impact performances of the environment.
  • Number of errors before stopping : if set to 20, the batch will automatically stop as soon as he detects 20 errors in the execution, allowing you to fix it and re-run the batch without having to wait for the initial execution to stop.


3) Activate online parameter to open renewal


Now that reservations are created, you can activate internet parameters on your sales channel so that your fans can resume the order and renew their Season tickets directly online.


Image Added

To do so, you just need to activate the parameter Season Ticket Renewal. You can also activate if you want the Dashboard of pending actions.

Image Added


Info
titleTips
  • Contingent : Before launching the batch, you may want to set all your stadium in a dedicated contingent. As SecuTix will create reservation or sales, it will use the contingent set at the moment the batch runs. It will not easily be possible to change it afterwards.
    Do not forget, if setting some contingents, to propagate those changes on all matches.
  • Change of tariffs : should your fan be able to select his tariffs at the moment of the renewal, you need to make sure that the expected tariff can be displayed on the shop at the moment of the renewal. Either by authorizing the season ticket product itself, or by creating an advantage integrating this tariff. That way fans would see a dropwodn on the tariffs before adding them onto the cart.
  • Yield management : if you want to reward early buyer, the Batch to update price for reservation orders may be useful as allowing you to change tariff (or price) of existing reservations. That way, renewal tariff at the beginning of the season ticket campaign can be much more interesting than tariff after 2 weeks for example.