Watch Video

 

Overview 

The managed event object is the object you need if you are running a conference, or any kind of event that requires ticketing. The object has a lot of options on it, but the chances are you won't need to use all of them.

Guidance

Event Name

This is the name of your managed event/conference, and is shown to your users at certain parts of the process (eg abstract submission).

EventNotice ntext

This is a html field that you can use to show an important piece of information to your users in multiple places. For example, you could put a reminder to contact the hotel to book their room before a certain date. Then, you can use content repeaters to display this information on webpages (on a side bar, header, footer etc) and in emails. When you want to change this notice, you'd then only have to change it in one place.

TicketPaymentDeadline datetime

This is the date on which your users must have selected their tickets - on this date ticket selection (through the managed event - register atom) will be disabled. 

ObjectId int

Attendees Tab

This is your list of users who have a confirmed main ticket - your attendees. it also shows the name of the main ticket they purchased. You can sort/filter this grid as you can with most, making it easy to find a certain person, or everyone who has purchased a certain ticket type.

• Export - You can click this button to export this list as a CSV file (open in Excel).

Calendars Tab

This shows all the calendar objects in your XPOR installation so that you can quickly and easily add this event into different calendars.

Event Tickets

This is where you create and set up your tickets.

EventOrderTypeObjectId 100055

This controls most of the ecommerce side of your managed event. If your users need to select and purchase tickets then you need to set up an Order Type object, and associate it by 'event order type'. Please see separate help resource on the Order Type Object.

Tickets

On the 'Event Tickets' tab you can set up the different ticket products that users can select. There are 'main products' and 'additional products'. You need to create at least one ‘main ticket product’ – if a user has one of these then they are attending your event. NOTE Users can only select one main ticket type for each user.

To create a Ticket Product:

• Click ‘Add Ticket Product’
• Then fill in the details. Theres a lot here
  Ticket name – Enter a name for your ticket
  Basket Qty non-editable – Tick this to make it so users cannot change the number of tickets in their basket - recommended.
  Qty Added to Basket – The default number of tickets a user will have added to their basket, normally 1.
  Description – This will show underneath the name of the ticket when the user is viewing the ticket options on the managed event - register atom. Enter something useful such as "ticket valid for all 3 days of the conference".
• Stock tab - Stock control method - This is up to you. If your event is unilimited on tickets then leave it as "none". If not, then "Simple" is probably best.
  Total stock - If you've chosen a stock control method then enter the total number of tickets you have in stock.
  Waiting List - Tick 'enable waiting list' at the bottom of the Stock tab. If the ticket sells out then users can add themselves to the ticket's waiting list (instead of adding it to their basket). You can then 'notify' (sends an email) the user if more become availble so that they can go in and purchase it.

AllowPurchasingOnBehalfOf bit

If you would like users to be able to register other users for your event, simply tick "Allow purchasing for Guests".

TicketsSameForGuest bit

If you would like the ticket options for guests to be the same as the ones you've already set up, then you can simply tick "Tickets are the same as the main tickets".

 

EnablePresentationSubmission bit

Tick this field to allow users to upload a presentation file as well as their paper file.

PaperSubmissionMode 110

There are three submission modes:

1. Paper Submission Disabled - Your users do not upload any files (papers or presentations).
2. Submit on Abstract Submission - Your users are asked to upload their files (papers and presentations) at the same time as when they submit their abstract.
3. Submit on Abstract Accepted - Your users are asked to upload their files (papers and presentations) only after their abstract has been accepted.

PaperAbstractLength smallint

This is the maximum character limit for the abstract field. This helps you to prevent users from copy & pasting their entire paper in!

SubmissionDeadline datetime

The date and time by which users entire submission must be completed (this includes upload of paper files). This is optional - you do not need to have a deadline.

AbstractDeadline datetime

The date and time by which no new abstracts will be able to be submitted. This is optional - you do not need to have a deadline.

PresentationSubmissionDeadline datetime

The date and time by which users must upload their presentations by. The presentation file upload file will be greyed out after this date and time. The intention of this is you can collect the Presentation files before your event because you will need them on the day, and to put them on the Event Programme. This is optional - you do not need to have a deadline.

Abstract Submitted Email

Select an email object that will be fired when an abstract is submitted. The email will go to the author, and whomever is associated to the managed event as BCC notification.

PaperSubmittedEmail 100038

Select an email object that will be fired when an submission has had its files uploaded. The email will go to the author, and whomever is associated to the managed event as BCC notification.

PaperAcceptedEmail 100038

Select an email object that will be fired when a submission has been accepted. The email will go to the author, and whomever is associated to the managed event as BCC notification.

PaperRejectedEmail 100038

Select an email object that will be fired when a submission has been rejected. The email will go to the author, and whomever is associated to the managed event as BCC notification.