If your Trumba representative has enabled your Trumba® Connect account for event submission forms, you can add a form to any calendar you publish. You can also set up your event approval process and customize the form. If you want to change something later, you can go back and edit the form whenever you want.
Note The procedures in this topic assume that your account is enabled for submission forms, that you have already published your calendar, and that you have a website in which you've incorporated Trumba calendar spuds. Learn more about publishing and spuds.
You add and customize event submission form spuds in the Publishing Control Panel. Each published calendar can have only one submission form spud.
Tip For help with submission form settings, click the blue buttons () you see on the page.
Tip If you added a custom font to your publication, that font will be applied to your event submission form.
You can manage submitted events in two ways:
Recommended only when all event submitters are trusted colleagues who are familiar with the way your calendars and events are organized.
Note If the submission form is available to the general public, we strongly recommend that you approve submitted events before they go live.
These instructions assume you already added an event submission form spud.
The Submitted sub-calendar is a temporary holding calendar for submitted events. The events remain on this sub-calendar until you approve and move them.
Tip If calendars you expect to see are not listed, it's probably because they're not sub-calendars of the published calendar. Only mixed-in sub-calendars show up here.
You can still add a submitted event to any of the mixed-in sub-calendars at the time you approve that event.
The following image shows the relationship between settings on the Edit Submission Form page and how Submitted sub-calendars work.
|A||Published calendar This is the calendar you publish. It may or may not include mixed-in sub-calendars.|
Category calendar Category calendars are mixed-in sub-calendars. When you select one or more of these sub-calendars on the Edit Submission Form page, two things happen:
|C||Submitted calendar This is the sub-calendar that Trumba Connect creates under the category calendar (if it exists) or the published calendar (if you don't use category calendars). Submitted events show up on this calendar. You promote submitted events to the parent calendar only after you approve them.|
If your Trumba customer account was created after Thursday, August 13, 2015 or you have enabled the New Event Actions, you can make sign-in an optional or required part of the event submission process. You can also control which sign-in methods are available.
Watch a short video that describes the event submission sign-in and tracking options.
Tip By default, the settings reflect the visitor account settings a publisher with administrative privileges set up for your organization. You can switch submission sign-in settings from optional to required and vice versa and limit the available sign-in methods. However, if visitor accounts are enabled for the account, you can't disable them for event submission.
Select Required to make sign-in mandatory before events can be submitted.
Tip If your organization enabled single sign-on for Trumba® accounts, you'll also see an organizational ID sign-in option in the drop-down list. Learn more about single sign-on.
You can control the relationship of the form's Submitter Information and Event Information sections to one another. And you can control the width of the form by placing labels above or to the left of the text entry fields.
These instructions assume you already added an event submission form spud.
Tip Even though layout settings are in the submitter info section, these settings apply to both the submitter and event info sections of the form.
Tip This topic gives you an overview of how event templates and custom fields work in relation to your event submission form. For more details about the settings described here, follow the instructions for adding an event submission form and then click the green Help buttons () on the Edit Submission Form page.
Your submission form has a default event template. It gets that template from the published calendar you added the submission form to.
Why does a submission form's event template matter? Because the template determines the fields the submission form contains. For example, if you want to let submitters submit images along with events, the template associated with the submission form must include an event image field.
In addition, if you have enabled more than one template on the published calendar, you can decide which template to associate with the submission form. You can even give event submitters a choice of templates by adding an event template field to the form.
|A||Default event template Same as the default for the published calendar you added the submission form to. If more than one template is enabled for the published calendar (as shown here), you can switch the default.|
Available templates If you have enabled multiple templates for the published calendar, the templates are listed here. Selecting one or more adds an Event type field to the submission form and gives submitters the opportunity to decide which template they want to use.
Tip If you use only one template, ignore the check box you see here.
|C||Event template field The event template field on this form is labelled Event type.|
In certain cases, you might want to add a field to the event information section of the submission form that does not appear in published events.
For example, you might want to add a hidden Request for Additional Services field to the submission form. This lets the person approving events know if an overhead projector, wheelchair access, or other special accommodations are needed. However, no Request for Additional Services field appears on the published calendar.
You add hidden fields by selecting them from the Display hidden fields list.
Tip The hidden fields list includes all unpublished custom fields and fields set to not show on the submission form. The field you select shows up on the submission form only if it is enabled for the template(s) associated with the form.
By default, when you create a new event submission form, an HTML editor is added to the Description and other multi-line text fields included in the published form.
The HTML editor makes it easy for event submitters with no knowledge of HTML code to add formatted text, images, and other content to fields in the events they submit.
Tip You can find the setting for showing or hiding the HTML editor on the Edit Submission Form Settings page in the Event Info Section under Options. To show the editor, select Enable HTML editor. To hide the editor, clear the check box.
Tip You can also customize the content of the confirmation email messages that event submitters receive. Learn more about customizing event submission emails.
You can add custom content to your event submission form in the following ways:
For example, you might want to let submitters know that personal information is never published. Rather, it serves as contact information in case you have questions about submissions.
For example, you might want let submitters know that all event information is public and that it appears in the published calendar. You might also want to inform them that you approve events before they go live.
If you leave this field blank, a default message appears: "We care about your privacy. Information provided via this form will not be resold or redistributed."
Any content you add to the privacy message field automatically replaces this default text.
Submitters see a success page after they submit an event. You might want to add a message to this page that thanks submitters and gives them an estimate of when they can expect to see their events go live.
Each of the content fields includes the HTML editor that makes it easy for you to format text, insert images and lists, add hyperlinks, and more. You can also use the Source button on the HTML editor to add your own HTML source code.
The following steps assume that you already added an event submission spud to the current publication.
Tip Even if you don't add a custom privacy statement, a default statement is added at the bottom of the submission form. ("We care about your privacy. Information provided via this form will not be resold or redistributed.")
To make sure a calendar's editor knows when events have been submitted, you can sign that editor up to receive an event submission notification email message. The notification message looks something like this:
The notification message includes details about the submitted event and, by replying to the email, the editor can contact the submitter to clear up event questions or provide information about the event's approval status.
If you enter multiple email addresses, use a semicolon to separate them.
If part of your internal workflow involves approving/reviewing events added to shared calendars by editor account-holders, you can use submission forms to help manage that process.
When you create submission forms with submission approval enabled, submitted sub-calendars are added automatically to each published calendar.
Tip Notification emails are triggered only by added events the submitted sub-calendar actually owns. For example, if an editor adds an event to another calendar and also shows the event on the submitted sub-calendar, no emails will be sent.
Tip For specific details about the Email on add and Email on submit options, click the green buttons next to the options on the Edit Submission Form Settings page.