August 2024 - Version 4.31

Please review the updates below and follow the upgrade instructions to upgrade your Events application.

Table of Contents

• Breaking Change
• Off-Cycle Releases
• BT Salesforce Release
• Webapp Release
• Field/Layout Updates
• Mobile Check-in App
• Upgrade Instructions
• Important Definitions

Breaking Change

The August 2024 release changed the Google Tag Manager’s default behavior. By default, Google Analytics cookies will only be collected when the Cookies Consent Banner is enabled. Previously, analytics were collected when the banner was disabled. (Known Issue: 000003814) 

For customers who have not enabled the cookie consent banner, tracking was mistakenly disabled as of August 27th. 

If you wish to re-enable tracking, please contact Blackthorn Support. We will be happy to assist you by enabling the cookie consent banner. Please include your org ID and desired configuration. 

Off-Cycle Releases

July 29, 2024

• An Attendee can complete the checkout process and, at a later date, return to the same browser and complete the checkout process again. Previously, when an Attendee tried to complete the checkout process a second time, the checkout failed because the system retained the previously cached ERS ID instead of creating a new draft ERS. (Known Issue: 000003901 and 000003905)

July 22, 2024

• Attendees can now use their AttendeeLink to go to published and active Events and register for Events. Previously, when an Attendee used an AttendeeLink from a contactless record or the AttendeeLink was related to a non-sys admin permission set, they received the “Error: 2006 – Something was wrong. Redirecting to home in 3 seconds…” which redirected them to the Event Group webpage. (Known Issue: 000003897)

BT Salesforce Release

Bug Fixes

• Webinars/Meetings: The AddSessionAttendeeToWebinar batch job now works correctly for webinars that do not require registration, ensuring the Session Attendee’s Webinar/Meeting Join URLfield is populated correctly. Previously, the AddSessionAttendeeToWebinar batch job failed, causing the following errors. (Known Issue: 000003690)
  • "code":3001,"message":"Webinar [Webinar/Meeting ID] not found or expired."
  • "code":404,"message":"Registration has not been enabled for this meeting: [Webinar/Meeting ID]."
  • "code":200,"message":"Webinar plan is missing. You must subscribe to the webinar plan and enable webinars for this user in order to perform this action."}
• Attendee Registration Component: When using encrypted fields on Contact and Account records, the BT Event Attendee Registration Component’s Related To field will filter correctly, especially for Person Accounts. Previously, the Related To field did not filter results correctly when the Account Account Name and Contact Name fields were encrypted. (Known Issue: 000003389)
• Capacity: If an error unrelated to capacity occurs, the Pending Capacity will be returned to the Remaining Capacity. Previously, the Pending Capacity was not rolled back to the Remaining Capacity, causing Attendees to see the "Some items are sold out and not available for checkout" error message despite capacity being available. (Known Issue: 000003888)
• Event Builder: The Description rich text box on the Event Builder’s General Info page will cover the entire page width for both the Comfy and Compact Display Density settings. Previously, the Description text box did not render as full width when the Display Density setting was set to Compact, and the zoom level was at 110% or below.

Enhancements

Fees Feature

The updated Fees feature for Event checkout and Invoices allows Event organizers to collect the credit card processing fee separately from the total amount due and apply required taxes. Use the following links to learn more.

• New Functionality: Learn more about the updated functionality and new logic associated with the Fee object and related updates to the Company Info, Invoice, and Event Item objects.  
• Checkout Process:  Learn about the order of calculations and supported scenarios.
• Using Fees: Customize your Event with either tax-inclusive pricing or taxes calculated at checkout and create tax-exempt Event Items. 
• Set Up Goods and Services Tax (GST) Fees: For countries that use GST, the following steps will walk you through setting up Fees and the Invoice/DocumentLink. 

Event Builder

• When a user clones an Event in the Event Builder, they can edit all Event fields before saving the cloned record. This functionality now matches the Event Wizard.
• After clicking Clone an Event, users will stay on the General Info page instead of being re-directed to the Landing Page.
• Cloning an Event with an empty Event Location field will result in a newly cloned Event with Event Location = “Hybrid” by default.
• Event organizers can now create, publish, and manage Recurring Events with the Event Builder, streamlining the Event scheduling and management process.
• Users can now configure and manage emailsfrom within the Event Builder when editing existing Events. The “Emails” section is located in the left-side navigation under Attendees. Note: When the Event Builder is used to create a new Event, the “Emails” tab will be hidden. The “Emails” page includes the following components and functionality.
  • Email Templates Related List
    • Create new Email Templates
    • See Email Templates related to the current record.
  • Email Configuration
    • Includes the same functionality as the Event record page component (Send Emails From, Confirmation Email, Waitlisted Email, and Waitlisted Pending Email)
  • Send Email
    • Send emails instantly.
    • Includes the same functionality as the Event record page component (Send Emails From, Email Template, Attendee Filter, Total Attendees, Email List, Attendee Preview, Preview Email, and Send)

Click here to learn more about creating Recurring Events in the Event Builder.

Table Manager

• Using the new Table Manager, you can drag and drop Attendees onto the Table, and Seat assignments are automatically created.
• Each Table has a Pencil (edit) and Trash Can (delete) button located next to the Table’s Table Name.
• Each assigned Seat at a Table has a Seat Number next to the assigned Attendee’s name. 
• A user can create a new Table with either a Table Name or a Table Number. 
  • Tables with names will be sorted alphabetically. 
  • Tables with numbers will be sorted by number, lowest to highest. 
  • If a Table has both a Table Name and a Table Number, the Table Name will be displayed and sorted alphabetically. 
• When a user attempts to delete a Table with assigned Attendees in the Table Manager, the following pop-up message will appear. “Remove attendees from the table before deleting the table.” Once all Attendees are deleted from the Table, the user can delete it.

Click here to learn more about the new Table Manager.

Webinars/Zoom

The new field, Zoom Email Notifications, was added to the Event and Session objects to allow users to toggle Zoom's registrants_email_notification and registrants_confirmation_email settings to “True” (send email) or “False” (do not send email). This field is only available for Zoom meetings/webinars. (Known Issue: 000003541)

• Object: Event 
  • Field Label: Zoom Email Notifications 
  • API Name: conference360__Zoom_Email_Notifications__c 
  • Description: This field controls whether Zoom email notifications are sent to registrants for the associated event. It allows users to toggle email notifications using the Zoom Meeting API, ensuring flexibility in communication settings. 
  • Picklist Values 
    • “Use Zoom Account Settings” (default): When selected, do not send a value to the Zoom API (the same as the current functionality). 
    • “Send Zoom Emails”: When selected, send “True” for both the registrants_email_notification and registrants_confirmation_email settings. 
    • “Do not send Zoom Emails”: When selected, send “False” for both the registrants_email_notification and registrants_confirmation_email settings. 
    • If the value is null, do not send a value to the Zoom API (the same as the current functionality) 
• Object: Session 
  • Field Label: Zoom Email Notifications 
  • API Name: conference360__Zoom_Email_Notifications__c 
  • Description: This field controls whether Zoom email notifications are sent to registrants for the associated session. It allows users to toggle email notifications using the Zoom Meeting API, ensuring flexibility in communication settings. 
  • Picklist Values 
    • “Use Zoom Account Settings” (default): When selected, do not send a value to the Zoom API (the same as the current functionality). 
    • “Send Zoom Emails”: When selected, send “True” for both the registrants_email_notification and registrants_confirmation_email settings. 
    • “Do not send Zoom Emails”: When selected, send “False” for both the registrants_email_notification and registrants_confirmation_email settings. 
    • If the value is null, do not send a value to the Zoom API (the same as the current functionality)

Webapp Release

Bug Fixes

• Calendar: When an Attendee clicks the Add to Calendar button to add an Event to their Google calendar, the calendar’s description field will only include relevant information about the Event. Previously, the Event’s Webinar/Meeting URL was automatically included in the description. (Known Issue: 000003341) 
• Codes: If a Code with Type = “Access-Promo” is required to checkout for an Event, but if it is missing or invalid, the user will see the following error message early in the process. “A discount code is required to complete the checkout for your selected items.” Previously, the user received a generic error message when they were already on the Contact information screen. (Known Issue: 000003763) 
• Attendees: If a user creates an Attendee record with a value in the State field, the Attendee will see that their address, including the State field, contains the correct information when registering for an Event via their AttendeeLink. Previously, the State field was blank even though a state had been added to the Attendee record. 
• Custom CSS: Custom CSS for Post-Event Questions will be applied correctly, providing a consistent and customizable user experience. Previously, custom CSS was not applied to Post-Event Questions when using Cache 2.0. 
• Forms: Forms with Form Elements with Type = “Hidden” will now correctly map to the selected object/field when applied to the Form (Pre-Registration), Post Event Questions, and Form (Post-Registration) fields and will be recorded in the Form Submissions and Form Submission Answer records. Previously, hidden Form Elements were not mapped correctly and weren’t recorded in the Form Submissions and Form Submission Answer records. (Known Issue: 000003562)

Accessibility

• Tab key navigation is limited to interactive elements, improving the user experience for keyboard-only users. Previously, users could navigate non-interactive elements such as the Event Name, Date and Time, and Description by clicking the Tab key.
• A field’s picklist labels can now be read by VoiceOver on all devices, allowing users to navigate and select options with appropriate auditory feedback. This update adheres to WCAG guidelines for keyboard navigation and screen reader compatibility. Previously, VoiceOver could not read picklist values on Mac devices for Events with UI Experience set to “Tabbed,” “Full-Width,” and “Dynamic.”

Enhancements

• Forms: Post-Event surveys or questions can now be translated. However, please note the following. 
  • Default values, picklist values, and big list values will not be translated to accommodate custom flows and logic. 
  • Since Post-Event Questions can work independently from Events/Event Settings, they are not impacted by the Event Settings’ Source Language and Target Language fields. Instead, the questions will be written in the language set by the org’s locale.
• Checkout: During the checkout process for a paid Event, users must manually navigate between the fields when entering their credit card and CVV numbers. Previously, the form automatically moved users to the following field when they entered their credit card information.

Field/Layout Updates

New

• Object: Event 
  • Field Label: Zoom Email Notifications 
  • API Name: conference360__Zoom_Email_Notifications__c 
  • Description: This field controls whether Zoom email notifications are sent to registrants for the associated event. It allows users to toggle email notifications using the Zoom Meeting API, ensuring flexibility in communication settings. 
• Object: Session 
  • Field Label: Zoom Email Notifications 
  • API Name: conference360__Zoom_Email_Notifications__c 
  • Description: This field controls whether Zoom email notifications are sent to registrants for the associated session. It allows users to toggle email notifications using the Zoom Meeting API, ensuring flexibility in communication settings. 

Mobile Check-in App

Please review the updates below and follow the upgrade instructions for your specific device to upgrade your Mobile Check-in app. (iOS v1.2.0 and Android v1.2.0)

Bug Fixes

• Android Only - Badges: Android Mobile Check-in app users can now click the TAKE PHOTO button in the Attendee’s Badge section to take a photo of the Attendee. Previously, users could not launch their device's camera by clicking the TAKE PHOTO button.
• Sessions: When a user selects a Session with registered Attendees, they will see the list of registered Attendees for that Session. Previously, the list of registered Attendees was blank.

QR Codes

• To close the QR code scan feature on iOS devices, users must now click the Cancel button. Previously, the QR code scan feature stopped responding when a user tried swiping down to close the feature.
• When a user clicks the Cancel button to close the QR code scan feature, the app will close as expected. Previously, the user received an error message when they tried to stop the QR code scanning process.

Enhancements

• Biometric Authentication: Mobile Check-in app users can now set up and use their mobile device's biometric authentication feature to log into the app. Click here for instructions to set up and use the biometric authentication feature. 
• Accessibility: To help Android and iOS Mobile Check-in app users meet their reading preferences and/or accessibility needs, they can now customize the app's text size by changing their phone’s operating system’s text size in the phone’s settings. Note: The Larger Accessibility Sizes settings in iOS are not supported.

Attendees

• If the Event Settings One Unique Attendee Email Per Event = “True” (checked), then Attendees added via the Mobile Check-in app will only be registered if their email address isn’t associated with another Attendee registered for the Event. The registrant’s email address must be unique. 
• If a user changes an Attendee’s information, including their name or email address, in Salesforce, the Mobile Check-in app will correctly display the new information on the app’s history screen. Previously, the app only displayed the old information on the check-in history screen.

Upgrade Instructions

Go to the Blackthorn Candy Shop to upgrade Events to the newest version.

Blackthorn has adopted Salesforce’s managed package installer to simplify the installation process. The installer will confirm that the correct Base Package and Payments versions are installed before upgrading Events.

For step-by-step instructions, click here.

Important Definitions

Breaking Change

A breaking change is a significant change that requires a package upgrade to see the update.

Off-Cycle or Hotfix Release

A hotfix is a release that corrects a problem that impacted extensive functionality.

BT Salesforce Release

The following applies to a Salesforce release.

• Salesforce fixes REQUIRE a package upgrade to see and utilize the fixes/enhancements.
• Only users with a System Administrator profile or the ModifyAllData system permission can install packages.

Webapp Release

The following applies to a Webapp Release (previously referred to as a platform release).

• Webapp fixes/changes usually do not require updates to the Salesforce package.
• These updates automatically apply to all customers; you cannot opt-out.

If you have any questions or need help with testing, please contact Blackthorn Support.