Put different renewals in the same file

In the past, the renewal batches for season tickets and membership were created a new file for every new order they processed. As a result, a single customer could end up with several files depending on the way batches were run or if it had different products (e.g. a membership and a season ticket). To provide easier processing in the box-office and an easier display of the order history online, it is now possible to group all renewal reservations of a customer inside the same file.

Solution

A new parameter "Re-use existing file" is available in the renewal batches for season tickets and membership to activate this new behaviour.

When active, the system will first search for an existing file for the same main contact that contains Reservation or Sales created by the same batch for the same season. If such a file is found, new reservations are consolidated inside the same file.

Impact when used with multi-threading

The renewal batch includes an option to process renewals in parallel to speed-up the process. When the parameter "Multithread size" is set to a value greater than one, the system will process in parallel different renewals.

The new "Re-use existing files" parameter is not fully compatible with multi-threading and a warning is shown next to the "Multithread size" parameter in case you input a value greater than one. If you still decide to execute the batch, then in case, within the same execution and at the same time, 2 orders are processed in parallels for the same contact, then the batch may create 2 different files in this edge case. If you want to avoid all edge cases, then leave the "Multithread size" empty.

How to get started?

If you do nothing, your existing schedules will keep the existing behaviour. Activate the new parameter "Re-use existing file" when your perform your next season renewal to activate the new feature.