Events

It would be helpful to have the Const ID included in the invitee export file.

Create custom sections or tabs to break up information for complex events, and make it easier for users to find the information they are looking for. Another option would to instead create a resources section similar to Spaces where you can add a link or a file to information users might need. This would be helpful for giving pages as well.

Event might not have a set date or time yet but we know it will be happening in a certain month or we have some details but not all and would like the event to show up on our events page but not be clickable yet. Ie: a published event but not a LIVE event.

We'd really love to have "Class Year" be a field we can toggle on and off on our event form setup, just like you can toggle on or off the "Affiliation" field. We'd like the Class Year question to show up on the first page of the registration form.

Could we add event description to the page showing our upcoming events? This could either be a new custom field, or it could show the first 100 or so characters from the event details section. This would be helpful for making the upcoming events page more useful and user friendly.

For large events, it's not tenable to have the organizer receive an email notification for every registration or registration edit. (And having all admins receive notifications if it's left blank is bananas.) It would be helpful if we could select to receive all notifications (current) or only ones that need attention (ie cancelations and waitlists that need to be managed).

When the “Edit Registration” option is toggled off for an event, it currently prevents users with existing registrations with pending payment from completing their payment via the “Pay Outstanding Amount” button in their confirmation email. ​ We would like a feature that still allows users to complete payment for the same registration, even if we are blocking other changes to the registration. This would let us restrict edits while ensuring payments can still be processed for pending registrations.

We suggest a time limit (30 minutes?) to check out your event registration/cart. The pending payments cause us a lot of issues. I don't want to make a new record if the person is never going to pay. And I don't want to ignore it in case they come back to pay. If the registrant doesn't check out in the allotted time, their registration is automatically removed.

Accurate Identification of Alumni a. Many attendees may have changed their last name after graduation. b. During events, people often recognize classmates by their maiden names, not their current/married names. c. Without a clear maiden name field, attendees may not recognize each other on guest lists or name tags. Consistent & Reliable Data for Reporting and Name Tags a. The team wants to include maiden names on name tags as a part of their event protocol. b. If maiden names are bundled inside the last name field or another custom field, it becomes inconsistent and unreliable for backend tasks like reporting or printing name tags.