Version 0.29.0.1 Release Notes

Below are the highlights of this release. With the features, updates and bug fixes in this release, be sure to read the Important Items before installing in a Sandbox or Production.

Appointment Type and Appointment Enhancements and Improvements
Itinerary Generation (for Appointments)
Google Analytics taging and utm tracking
Registrant Experience improvements and additional Event Manager controls for filtering and display options
A LOT of Bug Fixes

These release notes are broken down into multiple parts, Functional Features, Updates and Bug Fixes and Technical Features, Updates and Bug Fixes

Important Items and Upgrade Action Steps are things you should read to determine if your org needs to take an action prior to upgrading or what post upgrade steps need to be taken.
Known Issues highlights issues we recognize not functioning as expected and will be working to fix in the next release.
Functional Features, Updates and Bug Fixes captures everything in the release that have a direct impact on the Registrant or Event Manager experience. These are features or functionality utilized and noticed as part of the Summit Events App
Technical Features, Updates and Bug Fixes captures everything in the release that are withing the codebase. They impact the functionality and features of the Summit Events App, but aren’t likely noticeable from an Admin or Event Manager perspective.
Issues Closed is a comprehesive list of Github issues (Bugs and Feature Requests) that are closed as part of this release.

Important Items and Upgrade Action Steps

Below are important items to note prior to upgrading to 0.29.0.1.

Guest User Access

There were several updates in this package that impact the Summit Event Registant Permission Set and access needed for the Guest User. Below outlines what access is needed to avoid disruption as well as a new standard for Summit Evnets App and how to configure and manage Guest User Access.

The Guest User is required to have READ access to the Account Object. No additional field access necessary.
- A lookup to the Account Object on the Summit Event Record prompted this update.
It is recommended and encouraged that upon installation or prior to upgrading, you create a custom permission set, granting READ access to the Account Object and add that to the Guest User. While previous documentation encourages cloning the Guest Permission set, we’re adjusting those instructions to create a custom permission set (not clone) in addition tothe Guest User having the packaged permission set (Summit Event Registrant). This will allow for a more seamless upgrade process while then allow you to manage your own customization on a single permission set.
- While in the code base, the Summit Event Registrant has READ access to the Account object. Upon install we found that the permission was removed, likely due to Salesforce Security protocols being enforced.

Page Layouts and Picklists to Update

The following Lightning Layouts and Page Layouts need to be updated to expose new fields that leverage some new functionality/updates. Below we’re sharing the API name, which has a matching label:

Layout: Summit Events Lightning Record Page Layout
- Edit Lightning Record Pages and add the following fields:
  - Add Event_Appointment_Submit_List_Label__c to Page Details Tab in the Submit Page section
  - Add Event_Guest_Submit_List_Label__c to Guest Registration Tab in the Guest Registration Details section
Layout: Summit Events Registration
- Edit Page Layout and add the following fields to the top section:
  - Add BCC_Transactional_Emails__c
  - Add BCC_Transactional_Email_Statuses__c
Layout: Summit Events Registration
- Create a new section in the layout called “Analytics” and add the following fields:
  - Event_Website_Referrer__c
  - Event_Website__c
  - gclid__c
  - utm_campaign__c
  - utm_content__c
  - utm_creative_format__c
  - utm_id__c
  - utm_marketing_tactic__c
  - utm_medium__c
  - utm_source__c
  - utm_source_platform__c
  - utm_term__c
Layout: Summit Events Question
- Edit Page Layout and add the following fields to the top section:
  - Add Display_Style__c
Picklist Field: Summit Events object
- Edit Ask_Phone__c field and add the following values:
  - Ask mobile
  - Ask mobile and require

Known Issues

[BUG] Summary

The Open Registration checkbox field on the Summit Events Instance object isn’t calculating the same way the Registrant will experience. With this release there is improved confidence in what the registrant experiences than what may display on the Instance to the Event Manager. The registrant experiences what the Event Manager would expect, causing confusion as to why an event may appear open based on the Open Registration checkbox field, but isn’t (or vice versa) within the Event Manager or Admin perspective of Salesforce.

Reproduce

Create an Event with an Event Instance
Set the Date and Time to be Today while “Keep Registration Open During Event” on the Event is false.
When the Registration is supposed to be closed, see if the Open Registration checkbox field on the Summit Events Instance object is marked True
Click the “Register” link on the Summit Events Instance Object
The Registrant may experience that the event is no longer receiving registrations, though the Open Registration checkbox field indicates something different

Workaround

Remove the “Open Registration checkbox field from the page layout to avoid confusion

BUG 149

Summary

In referrence to the new BCC Transactional Email feature, please note that if the Summit Events Email record includes an Action Sub status the Email will not send. This functionality is limited to Summit Event Registration field Status and Summit Events Email field Action Status matching without a Action Substatus. An enhancement request has been entered for the functionality to send regardless of Summit Events Email field Action Sub status.

Functional Features, Updates and Bug Fixes

Analytics

To allow for enhanced marketing reporting on registration records, utm tracking codes can be recorded on registration. The following utm parameters can be captured:
- Event_Website_Referrer__c
- Event_Website__c
- gclid__c
- utm_campaign__c
- utm_content__c
- utm_creative_format__c
- utm_id__c
- utm_marketing_tactic__c
- utm_medium__c
- utm_source__c
- utm_source_platform__c
- utm_term__c

Appointment Type, Appointments and Itinerary Generation

The overall Appointment Type functionality has improved to meet expectations. The primary feature of receiving registrant input, when asked for, is now recorded on registrant related appointment record.
The “Appointment Date” field is now populated with improved formula.
If an Appointment Type configured to be Required, the appointment option no longer highlights an error when the input is not required. Previously, if the appointment type was required, but the registration wasn’t required to input anything, it would error. Now Appointment Types can be required with optional input. If both are required they will work as anticipated.
On the Appointment Type record, users and Event Managers can set a sort Order. When the Once the Appointments are selected by the registrant and they see a summary on the Submit page, the appointment type sort order is respected. Previously this was not the case and it sorted alphabetically.
Appointments/Sessions with a value of Do Not Show, with the field “Auto Confirm” set to True, will now have the Appointment record status set to “Confirmed” if the appointment page is skipped. This was previously not working as expected.
Auto Add Building and Auto Add Time configured on the Appointment Type record will now also flow to the Appointment record, associated to the Registrant. This was previously not working as expected.
Appointment type records leveraging the “Chosen State” field, where values of “Added”, “Added and Required”, and “Added and Not Shown” are being recorded earlier in the registration process than before. This previously happened later in the process and was causing errors. These appointments are working and being captured as expected.
Appointment Type records that only have an Appointment Category will no longer create a registration error. This is also the case is there is a single value on the Appointment Type field.
On the Appointment Type record, If an Appointment Category AND Appointment Type are established they will be added to the registrants related appointment record without asking the registrant for a selection. Similarly, if the registrant is asked for a selection based on the Appointment Category, the Appointment Type value selected by the registrant will be recorded on the registrant related appointment record.
Introduce an Itinerary Generation feature. This captures the related appointments and details from the appointment record to create a schedule or itinerary. There are two that may be generated and are based off of status. If an Appointment record has a status that is NOT “Confirmed”, they will generate in the Generated Itinerary field. If the Status is Confirmed, the itinerary will gradually build as each appointment record is changed to Confirmed.
Event Mangers can control what fields will display on the generated itinerary through fields on the Summit Event Object. They will also be able to determine what the headers are. Those fields are:

Communication and Transactional Emails

On the registration record, an Event Manager can manually add a(n) email(s) to the BCC Transactional Emails field on the Summit Events Registration record while selecting a corresponding status on the BCC Transactional Email Status field to allow for unique individuals to be added on triggered email communications to that specific registrant. A higher education use case may involve adding a coach or faculty member on a confirmation email that has the registrant’s itinerary on it as a reminder/notification. For more information about this feature go here.
The Summit Event Email record wasn’t appropriately displaying the visualforce page, allowing the user to select an Org Wide Email Address or Classic Letterhead Template. This essentially made the functionality unusable in a production environment. The visualforce page has been fixed and working as expected.
When utilizing th Guest Registration feature along with transactional emails within Summit Events, previously it would send an email to all who were registered. So if a registrant registered themselves and 5 guests, 6 emails would send. In an effort to stay compliant, because the guest didn’t voluntarily give their email address (someone else other than themselves did), Summit Events App will now check for whether the email address on the registration record is for a hosted registrant before adding to list of emails to send. The hosted registrant is the individual who submitted the registration for themselves and guests.

Filtering and Display Options

Added two additional fields on the Summit Events record to support more complex needs for filter in the Event Feed. This may also help in reporting.
- Field: Where to Display (API Name: Filter_Where_To_Display__c)
- Field: Category (API Name: Filter_Category__c)
Additional Label fields have been added on the Summit Events object to allow for Event Managers to control values displaying on the submit page. The follow fields have been added:
- Event Appointment Submit List Label
- Event Guest Submit List Label
User can now control the default Country in custom settings. This value will default your country picklist if the value you entered in custom setting is in the global picklist packaged with SEA
Country/state are now dependent picklists if mapped in the global picklist value packaged with SEA. This should allow for additional mapping of other countries by SEA users.
The packaged calendar has been updated to reflect the Instance Short Description. If the Instance Short Description is blank, the Event Description will be utilized. Previously the calendar only reflected the Event Description, not leaving opportunity for different instance description on events that have multiple instances.
When there is a bullet or numbered list in the Event Descirption page, they should now display as expected. Previously, lists wouldn’t appear as list from the Registrants perspective.

General

The template on the Summit Event record is no longer automatically defaulting to GeneralSLDS when another template is configured to be the default. The Default label of GeneralSLDS was removed and marked the value as Default within the picklist. (#408)
There was a minor issue with the “Admin Open Registration” link where the registration would not fully complete. This has been fixed and the Admin Open Registration link is functioning as expected.
Fixed issue #425 by making the calculations only care about the end date if the “Keep Registration Open During Event” checkbox is checked (instead of caring about both start and end dates).
Changed the word “Additional” to “Custom” on the Page Details Tab on Summit Event Lightning Page. Also updated the field label on the Summit Events Object changing Additional to Custom to reflect the use of Custom Questions (#419).
Additional question (not Summit Event Question) heading on the primary registration page does not appear when no questions are defined on the Summit Events object record.
Additional questions are now shown only if question text and question type are both defined on the Summit Event object record. Previously, if one of them had a value, it would display to the registrant, but may not allow the registrant to input an answer.
Updated the Help Text and Description for “Event is Full Display Text” to better clearly articulate when the information in the field will display. The previous assumption was it would only display if capacity has been met, when in reality it would display if capacity was met, the event instance was in a status other than active or the event date had passed (#411)

Summit Events Questions

User will now have control over how Summit Event Questions are displayed on the registration page. You can select from display options to show the question full width, half width and third width with the default setting being half width. You can control this on each Summit Event Question record by utilizing the Display field. This feature will adjust on mobile devices to full width as well as adjust to browser size changes.
On the Summit Event Question Object, Event Manager can now create a picklist based on a list of registration records. This is in addition to the value “Lookup” which allows for type ahead and an option to enter something that doesn’t exist. “Lookup Picklist” will display all appropriate records (based on the query, similar to that of the Lookup functionality) and have the registrant select a value.
On the Summit Event Question object, a validation rule has added to ensure all appropriate fields are utilized when leveraging Lookup or Lookup Picklist.
Updated the Summit Event Question object to have specific required fields for the functionality to work appropriately. This is supported by additional validation rules based on the type of question being asked.
The registration experience now takes into account if the Summit Event Questions records are set to “Registrant and Guest”. Previously the Guest page would not display. It is working as expected now.
The Registrant Guest page will now only show if Summit Event Question records exist while defined accordingly AND the “Display Guest Registration” is checked on the Summit Event object record. Previously it would show a blank page if no Summit Event Question records were created but the “Display Guest Registration” was checked.

Summit Events Registration and the Registration Experience

When utilizing Summit Events with an Experience Site and the registrant is logged, the associated contact record is recognized and pre-fills with the contact information. If a field was empty and required, like Birthdate, the user could not progress because the field was locked, and validation would not allow any fields to be empty. Now registrants can fill in the blank information. Fields with existing information are still locked.
When utilizing Summit Events with an Experience Site and the registrant is logged, the associated contact record is recognized. Now the contact record is automatically connected to the registration. previously this was not happening and Contact matching had to be configured.
“Ask Phone” field on the Event Registration record now supports “Ask Mobile” and “Ask Mobile and Require”. The work “Mobile” is stripped off the front of the label when this option is selected and intended SMS consent message questions appear. In addition, the SMS Consent message is no longer bolded.

Technical Features, Updates and Bug Fixes