As mentioned previously, we’re introducing quite a few new CiviEvent features in CiviCRM 2.3. Most of them are still undergoing our internal CiviCRM QA cycle, but do check them out at our CiviCRM 2.3 sandbox if you’re interested (there is still time for some minor fixes to accommodate your use-cases!).
CiviCRM 2.3 introduces the concept of wait lists, where participants who registered after a given event was full are placed. These participants are informed before their initial registration that the event is full, and if they continue their registration process, they are put on a waitlist. Once the event gets some free spaces (because some other participations expire, or participants cancel their participation, or are removed by an admin, or the event gets more spaces…), a cronjob-based script makes sure that the participants from the top of the waitlist (first-registered-first) are moved to pending state.
Another new feature is the participant approval – any event can be configured in a way that participants can he hand-approved by an admin before they’re considered registered for that event.
To make the above concepts workable, CiviCRM 2.3 introduces a two-stage registration process. Participants can partially register for an event and then finish their registration in a separate step (for example when they’re hand-approved or when they’re moved from the waitlist because of free event spaces).
Again, to make the two-step registration manageable, a new per-event setting was introduced. If a participant is put in a pending state (because they chose to pay later, or got in from a waitlist, or were approved), a time limit when they have to finish their registration (or get cancelled) can be set.
To make new event creation simpler, the concept of event templates was introduced. One an event template is constructed (in the Administer CiviCRM area), new events (and, actually, new event templates) can be based on it. This should make the creation of recursive (or otherwise similar) events a breeze.
Separate Profiles for Additional Participants
To enhance the features for group registration, separate profiles can now be set for the main and for the additional participants. To keep backward compatibility, all upgrades from pre-2.3 will assume that additional participants should use the same profiles as the main participant, but this can be quickly adjusted on a per-event basis.
You can see the full list of CiviEvent issues targeting CiviCRM 2.3 in our issue tracker.