This content is a work in progress. If you’re interested in contributing to the Summit Events App and want to help provide support by reviewing or adding to this page, comment below and let us know!

Post-Installation Considerations and Configuration Before Creating Your First Event

After you install Summit Events in your org there are some additional considerations you’ll want to make to ensure there is alignment with your organization. This page will capture items you’ll want to review as part of your event before you start building and moving to Creating a Basic Event.

Because Summit Events is intended to integrate with your existing Salesforce org, you’ll want to consider exposing records on related objects. The Contact record is a good example as you may want to create visibility to an individual’s registration records from that object. Consider the following for visibility and clarity within your Salesforce org:

Review and Personalize Picklists

We deliver sample values for the picklist fields, but you will want to edit these fields to create your own values and deactivate some or all of our sample values. You can do this following the instructions here that show how to edit and create picklist values. Here are the picklist fields that need to be reviewed and personalized for your organization:

Summit Events object

  • Event Type
  • Audience
  • Event Sponsor
  • Location Type
  • Building

Summit Events Instance object

  • Category
  • Location Type Override
  • Building Override

Summit Events Appointment object

  • Building

Summit Events Appointment Type object

  • Appointment Category
  • Appointment Type
  • Auto Add Building

Summit Events Registration object

  • Registrant will see these picklist values
    • Applicant Type
    • Campus Tour Location
    • Preferred Visit Time
    • Registrant Gender
    • Registrant Program Interest
    • Registrant Pronouns
    • Relationship to Institution
  • Admin/Event Management
    • Presentation Location (should match “Building” on the Summit Events object)
    • Participation Type

Summit Events Questions object

  • Existing Picklist Values (Note: this will be based on any custom picklist fields on the Summit Events Registration object)

—To be continued-work in progress. Please check back later!—

Review Page Layouts

The Summit Events App was originally created for Higher Education institutions. You’ll notice there are some fields that are specifically related to Admissions, like “Applicant Type”. Based on your organization/institution, you may want to remove fields from the page layout to avoid confusion from your Users. We add the most commonly used fields that highlight existing functionality to the page layouts on install for visibility. You can modify these to add or remove fields so that the page displays fields that make sense for your organization. *We include all fields for an object on the page layout so you know everything that is included. You likely will not use all of these fields, so you should customize the page layouts so your users only see the fields you will be using.

Additionly, you will want to add the “Summit Events Registrant” related list to the Contact page layout so your users can easily see the events for which your contacts have registered.

For support in creating new or editing your page layouts, we encourage you to review Salesforce documentation: How to create and edit page layouts

Modify Search Layouts

Additional Considerations

There are some additional considerations to make Summit Events more personalized for your Organization/Institution. Consider the following and check out the provided resources:

  • Changing field Display Names
    • Changing the field display name to better match your organization’s/institution’s jargon may be helpful to users.
    • The following instructions how to change field label for managed package fields.
    • Note: Doing this may create challenges in leveraging some of the documentation, so be mindful on what fields you’re updating.
  • Creating Record Type and Custom Page Layouts
    • Create Record Type and Custom Page layouts can help guide users based on their specific use cases.
    • In Higher Education, you may have different layouts for Admissions and Advancements based on their needs and processes.
    • You can leverage Salesforce resources on how to create Record Types.
  • Add the Summit Events Calendar to your website
    • There are a couple of ways to do this and it may depend on your organization’s/institution’s website resources.
    • You can follow these instructions on getting the full calendar to a web page. - Instructions Needed
    • You can follow these instructions for more advanced calendaring functionality and leverage the Summit Events Feed. - Instructions Needed
  • Setup Contact and Lead Matching
    • Ideally, you’ll want Event Registrants to be added to your Salesforce org in a meaningful way. You may want to create and match Leads and/or Contacts. Review the following to create a process that supports your organization/institution: Contact and Lead Matching/Creation
  • Create a Custom Template
    • A custom template will allow for the registration form and pages to be branded for your organization/institution.
    • The “General SLDS” is standard and will allow for a professional looking form, but you may want more branding.
    • You can follow these instructions on how to create a custom template.
  • Add Summit Events Calendar to Website

Future

  • Add your custom parking pass for use with the “UG Parking Pass Link” on the the Summit Events Registration object.

  • Template - customize the “General SLDS” template or create a custom template.

Back to top

Have a question or need support?

The best place to ask questions or troubleshoot the Summit Events App is by posting your questions in the Commons Project: Summit Events App Salesforce Trailblazer Community . There you can ask questions, share your experiences, and help others!

Do you have a feature request or want to report a bug? Please submit an issue on our GitHub repository .

Edit this page on GitHub