Comments
In the Event Planning Module, the current design allows the same Contact to register for an event multiple times.Can we have a feature that only allows each Contact to register once for each event?This makes sense, as registering the same person twice does not have any meaning. In the registration form, if we detect that the same Contact has already registered, it should return a warning or message on the front end to notify the user that they have already registered for this event.
The event registration process does not consider multiple submissions as duplicates because the platform allows a single contact to have multiple registrations for the same event. This design supports scenarios where attendees may register for different sessions or ticket types under the same event.To address your concern about preventing duplicate registrations for the same contact within the same event, the feature that should be implemented is a duplicate check at the Event Registration level. This enhancement would:Validate whether an existing registration already exists for the same contact and event combination.Block or prompt the user before creating a new registration for the same event.Provide flexibility to configure exceptions (e.g., allow multiple registrations for multi-session events if required).This functionality is not currently available out-of-the-box, as matching rules apply only to Contacts and not to Event Registrations. Implementing this feature would require either:A custom plugin for synchronous validation during registration, orA Power Automate flow with logic to check existing registrations before creating a new one.
+1 on this. Having the option to create a custom view and set it as default will allow admins to show only the email templates (Insert Email Template view) that can be used by specific groups. This will be easier than the current approach to control the hiding/showing of email templates via Type (Individual, Org) and Security Roles.
I agree with Wouter and Jaco !The BC Layout options (List, tall Tiles, Tiles) are already linked to the BC Views. When changing view BC knows the layout option. Is it a bad idea that the last selected view from the user is remembered and when opening the list page the last view that is used is openend instead of the "All" option...? This would make the last selected view option the default for reopening.