In order to be able to use these settings optimally, advanced technical understanding and knowledge of HTML and CSS are helpful.
Online bookings or subscriptions can be automatically deleted a certain amount of time after the end of the event (or church service). This is particularly useful for complying with data protection regulations, as subscriptions often contain personal information about participants.
Configure online booking as described here. You will find the following input field in the form and in the event (or church service):
Delete registrations after event (days)
This field determines the number of days after the end of the event after which bookings are to be deleted. If nothing is specified here, the bookings will not be deleted automatically.
In order for bookings to be deleted automatically, the administration also has to configure a process once in the app Scheduled jobs using the following Java class:
alkacon.mercury.webform.CmsDeleteFormDataJob
Enter the data as shown in the screenshot. Pay particular attention to the settings for username: Admin and Project: Offline.
Automatic deletion takes place via a process after the expiration date has been reached (see above). This means that if, for example, you set “Delete bookings after 2 days,” this will not happen exactly after 48 hours, but after 48 + x hours. The x depends on when the set process runs.
If the end date of the event is changed retrospectively, the deletion date of bookings that have already been created will not be changed. The same applies if you change the period for deleting entries retrospectively, e.g., from 14 to 21 days after the end of the event.
Automatic deletion only works for bookings that were created via “Events” or “Church Services.” It does NOT work for “pure” forms that use the booking function directly.