Page tree
Skip to end of metadata
Go to start of metadata

25Live provides multiple methods to build event relationships, each with its own set of features and benefits. 

You do not need to build a complex event if your event is simple enough to meet these conditions:

  • The event information (Name, Title, Description, Type, etc.) accurately represents the additional occurrence(s) being added
  • The occurrence(s) being added can have the same setup, pre-event, post-event, and/or takedown time (if applicable) to the existing event occurrences
  • All occurrences can be published to a calendar without fear of oversharing information or creating confusion.
  • There is a desire to keep all portions of the event under one reference number.

If your event is more complicated, you can use this information to choose the most appropriate type of event structure. There will be cases where using a combination of approaches might be the best way to meet very specific needs.

Guide to Complex Event Structures

Related Events

Related Events

Create this type of event if...

  • The event information (Name, Title, Description, Type, Description, Organization, Custom Attributes, Requirements, Contact Roles, Categories) of the existing event do not accurately represent the additional occurrence(s) being added
  • The occurrence being added needs different setup, pre-event, post-event, and/or takedown time (if applicable) from the existing event occurrences
  • Either the existing event, or the newly created one, should not be published to a calendar without fear of oversharing information or creating confusion
  • Confirmation reports are needed for only a portion of the event
  • There is a need to break up invoicing of a series of events based on a date range or other business process related constraint
  • The ability to hide a portion of the event (using Object Security) is important

  • Read More:
Event Segments

Event segments

Create this type of event if...

  • The event information (Name, Title, Description, Type, etc.) accurately represents the additional occurrence being added
  • Adding a name to the occurrence(s) will help to further define it (in addition to the event name)
  • The occurrence being added needs different setup, pre-event, post-event, and/or takedown times (if applicable) from the existing event occurrences
  • All occurrences can be published to a calendar without fear of oversharing information or creating confusion
  • There is a desire to keep all portions of the event under one reference number
  • There is no desire to invoice parts of the event separately
  • Read More:
Bound Events

Bound events

Create this type of event if...



Copyright © 2021 CollegeNET, Inc.  Note: This information is for CollegeNET Series25 customer use only.
Series25 Customer Resources • Terms of Use •  Privacy Policy • Learn About Series25 • Contact CollegeNET