Notices and slips

There are a number of notices to be set up for Events. All are sent via email.

• Confirmation -  This notice is sent to attendees when their status is set to "Confirmed".
• Confirmation - pending payment -  This notice is sent to attendees when their status is set to "Pending payment".
• Reminder - This notice is generated and sent via scheduled task to attendees with the status "Confirmed" or "Pending payment". The Reminder period in the session specifies when the notice is sent. The email is sent only once.
• Waiting list - This notice is sent to attendees when their status is set to "On waiting list".
• Waiting list - confirmation -  This notice is generated and sent via scheduled task if the attendees status has changed from "On waiting list" to "Confirmed". The email is sent only once.
• Waiting list - confirmation - pending payment - This notice is generated and sent via scheduled task if the attendees status has changed from "On waiting list" to "Pending payment". The email is sent only once.
• Event cancellation - This notice is sent to attendees when an event is cancelled.
• Registration cancellation - This notice is sent to a registrant when their registration is cancelled.
• Survey - This notice is generated and sent via scheduled task if an attendee was at a completed event/session that has a Survey URL. The email is sent only once.
• Event/Session Details Update - A notice is sent to the registrant (including those on the waiting list) if the Location, the Location Note, the Start date, or the Start time are changed. NB. This Event notice required Spydus server version 10.6.1 or higher.
  

The notices and slip can be maintained via Maintenance > General > HTML Email & Slips Configurator > Events tab.

• Use Server Test > Events > HTML to test the notices and see examples of each notice type. There are four examples for each type:
  • one where registration is for the session,
  • one where registration is for the event,
  • one where registration is for a library patron, and
  • one where registration is for a guest
    
• Use Server Test > Events > HTML Email to send the examples to a specified email address.

Use the slip parameters to set up the ticket to be printed (see example below). In the Barcode type field, select the type that the library uses.

 

Scheduled tasks

There are four scheduled tasks that must be configured on the Spydus server for Events.

• Completion task — to complete events/sessions - This task will mark an event/session as complete if today's date is after the event/session end date or, if there is no end date, after the start date.
• Survey task — to send survey emails - This task will send a survey email to registrants for completed events/sessions that require a survey. The email is sent only once.
• Reminder task — to send reminder emails - This task will send a reminder email to registrants for events/sessions that have a reminder period set. The email is sent only once.
• Waiting list confirmation task - This task will look at all incomplete registrations that have the Waiting List status (in ascending ranking order) and will confirm those where the required number of tickets are available for the event/session. If a registration is confirmed, it sends a confirmation/pending payment email to the registrant. The email is sent only once.