Important update

‍

New default template and new registration flow

We have updated the core registration flow so it now reflects how most events actually work, with a clear attending yes or no choice. Previously this conflicted with the built in unregister function, which resulted in unnecessary complexity. Now everything has been combined into a single, coherent and much better flow, together with a new default template that will be used for all new projects.

‍

New static pages

With this release we introduce static pages. These are system pages that are not part of the menu or the timeline but are used for specific states in the flow. They can be edited and styled just like any other page.

Two static pages are created by default

• unregister
• waitlist

If a participant is unregistered either by themselves or by an administrator, they are redirected to the unregister page instead of the timeline. The same applies if a participant is placed on the waitlist.

‍

What happens after an unregistration

A participant who is marked as unregister is not removed from the event. They have simply declined. This means they can register again at any time. When they re register, the registration form is shown with all previously entered data already prefilled. No information is lost.

‍

New field in the default template

The new default template includes a system field called attending. This field can of course be removed if needed.

All "fields" placed within attending automatically get ready made conditions connected to this field. This means that if a participant selects attending no, no additional "fields"  have to be completed. Previously this required custom "fields"  and a large number of manual conditions.

‍

Why this is better

The new flow provides several important benefits

• Participants can clearly see if they are unregistered
• Administrators get a correct and consistent participant status
• Dashboard, seat handling and segmentation work properly
• All data entered by the participant is preserved and available to both participants and administrators

‍

Important to know

When a participant becomes unregister, all related seat limits are released automatically. This applies whether the participant unregisters themselves or is unregistered by an administrator.A participant therefore cannot be unregistered and still occupy a seat in a limited capacity activity. For example, if an activity has five seats and someone unregisters, that seat immediately becomes available to another participant.

‍