Summary

Event: waiting list & registration closing date and time
Waiting list
It is possible, if an event is full, to put yourself on a waiting list.
Persons registered on the waiting list receive an SMS or email when a seat becomes available. If the registration is completed, the person is removed from the waiting list.
The settings are configured at the event subject level: do not notify, by email, by SMS, or leave the choice to the visitor.
Full events with this option enabled are clickable in the booking module; the email and/or phone number are requested depending on the option selected in the settings.
You can register for multiple events within the same or different subjects. Unsubscribing from the waiting list is done manually using the button in the email.
In the event window from the agenda, you can see the number of pending reservations.
Places reserved for last-minute registrations are not affected; those on the waiting list will not be informed when these places become available.
Registration closing date and time
You can set a registration closing date and time for an event. This can range from -8 hours (for late registration) to +3000 hours (or 4 months).
Last-minute registrations override the closing date/time.
Example:
Registration opens 60 days before the event
Registration closing: 48 hours
Last-minute registration: 60 minutes
This means that:
– you can start registering 60 days before the event starts,
– you can no longer register 48 hours before,
– you can register again 1 hour before.

Other new features
Alerts
- Alerts can be used with third-party messaging systems.
Appointments
- The option to notify users when a slot becomes available has been improved to limit the choice offered to visitors between email and SMS. This option is now consistent with the option for events.
Photobooth
- The photobooth process also works for appointments.
Event registration
- The seat is reserved for 5 minutes while information is being entered.
Appointment configuration has been added to the APIs.
New optional “appointmentConfig” field in the following APIs:
- Bookslot
- createAppointmentFromSlot
- getSlotList
- updateAppointment

Bug fixes & performance improvements
Visit database
- At home interviews now have the value “H” in the data export.
- The “Ticket Type”, “Taken on”, and “Taken with” columns are correctly tagged in the data export.
- The correct user is now tagged when a recurring appointment is modified.
- Automatically closed interviews or missed appointments were previously tagged by the user “ROLE_SUPPORT”, now replaced by “Orion”.
- Agent data is no longer anonymized at the same time as visitor data.
- Fixed an unexpected date change on sites with dates in the American format.
Agenda
- Future events can be deleted from a series of events even if there are past registrants.
- Fixed some cases where the registrant counter calculation was incorrect.
- Visibility of required custom fields is now managed on a site-by-site basis.
Appointment making
- We no longer offer slots when there is an event on the slot.
- Email addresses with a subdomain are accepted.
Reception
- An interview can be closed if a direction purpose has been added and then removed.
- The disability prefix is used for tickets distributed via a local printer.
- Video interviews can be closed even if the connection is lost.
Survey
- In data export, times are based on the location’s time zone.
- SMS surveys will no longer be sent unless configured to do so.
Monitoring
- The monitoring indicators per queue work well even for more than 200 locations.
Analytics
- Managers can now access the Orion BI module.
- Automatic email reports are sent correctly.
Messages
- A single line break between the text and the signature in the SMS.
Kiosk
- Compliance with waiting time thresholds for display on the kiosk.
Alerts
- Displaying time in the location’s time zone.
Picking
- The video is updated correctly when the order status changes.