The iModules product delivers a power module for registering Alumni for events.  There are four basic types of events models that can be built to register and if necessary collect fees for events that can be held for Cornell Alumni and guest.

The basic process for creating events are:

1. Determine what type of event model needs to be used
2. Determine if there is an existing event template that I can use to clone my new event.
3. Create the event.
   1. A series of 4 videos were created outlining building events covering the following subjects
      1. Overview of events homepage and different reporting options.
      2. Event name, event listing, custom URL, identity checkpoint, pre-populate, start and end date and times, registration page format, capacities, attendee list, event description, location information.
      3. New fields, existing fields, reusable fields, deleting fields, rich text fields, fee/commerce items, guest step, payment gateway.
      4. Editing landing page, adding photo, editing attendee list, landing page URL, review/finish pages, confirmation email
   2. Nadia Kiechle created this very nice working document on building events.  Feel free to refer to this along with the best practices  below when creating events.

 

iModules provides a link with a checklist or series of questions to ask yourself before you create an event.

A Best Practice for iModules (updated 11/10/2021) has been created to provide guidelines for creating events that will interface with the AAD website (alumni.cornell.edu/events) and meet AAD design guidelines.   Events that do not follow these guidelines may not present themselves as expected on the AAD website.  An image managing tool is available to help create images that will work within the best practices laid out.

We have created a ‘fake event‘ called “AAD Sample event- Fields – DO NOT DELETE” that displays what every type of field you can place on an event.  This may help you investigate the various types of fields and how they will look on your event form.

iModules events are able to collect on-line payment for registration fees, activity fees, and ticketing fees.   When an event will be collecting funds,  there is configuration that must be set up.  Additionally there are numerous tracks and trades that can be deployed.

The ability to manage event behavior through roles is one of the more power tools that can be deployed.     The use of roles can be used to display and hide fields, steps, and categories.

Member vs Non-Member Records –  iModules events can be configured in a manner that will manage or limit the generation of non-member (or temporary) records that are created by events.

Suggestions:

With the flexibility and wide functionality of events,  its recommended to utilize the training material,  web/written/video,  then experiment with creating events.  Events can be deleted so the advice is practice, practice, practice to understand the process.