Prepopulate submission form fields

If you offer an event submission form on your website for internal users who must sign in to your environment to access the form, you can prepopulate the name and email address fields with each submitter's authenticated credentials.

Note Prepopulating submitters' names and email addresses prevents submitters from signing-in on the event submission form itself. If you enable submission form sign-in, do not prepopulate the fields on the form. Learn more about submission form sign-in options.

The fields will be grayed out, making it impossible for submitters to edit the information.

Tip Prepopulating fields in an event submission form is an advanced developer-level procedure. You must provide web server code that dynamically populates arguments in the Trumba spud code with a submitter's credentials.

Prepopulated, noneditable name and email address credentials in an event submission form.

Process for setting up prepopulated submitter fields

Prepopulating fields requires the addition of two arguments to the event submission form spud code, the visitorName and visitorEmail arguments. You provide the web server code to dynamically populate the arguments with each submitter's name and email address credentials.

To set up a prepopulated event submission form

1. Make sure that an event submission form is enabled for your account.
2. Set up the event submission form the way you want.
3. Instead of embedding the submission form spud script provided on the Event Submission tab, embed the following script. Replace the blue text with the code value from your submission form script.
   <script id="Script1"
   src="http://www.trumba.com/ea/scripts/submitevent.js"
   type="text/javascript">
   </script>
   <script type="text/javascript">trumbaInsertSubmitEventForm({
   code: "your submission form code value",
   width: 385,
   height: 775,
   backgroundColor: "white",
   visitorName: "Prepopulated Name",
   visitorEmail: "prepopulated_name@example.com"});
   </script>
4. Write server code that dynamically populates the visitorName and visitorEmail arguments in the code with an authenticated user's name and email address.

   When a signed-in user accesses the event submission form, your web server dynamically delivers values for the name and email address arguments in the spud code.