Please review the updates below and follow the upgrade instructions to upgrade your Events application.
Table of Contents
Breaking Changes
June 11, 2025
The May 2025 Events Webapp release functionality has been restored and updated to ensure all users can register for Events in either of the following scenarios.
Users can register for an Event regardless of the Event’s UI Experience. Previously, when the Events app was used with an earlier version with the Tabbed or Simple UI, the checkout process failed on the frontend without creating a Blackthorn Log entry, even though the registration could be processed on the backend.
Users cannot complete the registration process if they leave a required field on the registration form blank. Previously, Tabbed UI registrations succeeded even though required form fields were not filled out, which resulted in a failure at the ERS step since Salesforce could not process the registration.
June 4, 2025
The May 2025 webapp release has been reverted to the April 2025 webapp release.
This is due to the following issues:
Tabbed or Simple UI registrations were processed successfully on the backend, even though the checkout process failed on the frontend without creating a Blackthorn Log entry.
Tabbed UI registrations succeeded even though required form fields were not filled out, which resulted in a failure at the ERS step since Salesforce could not process the registration.
We are working to discover the issue and fix the problem. This is our top priority, and we are moving on it as quickly as possible. Thank you for your patience.
June 2, 2025
The May 2025 Events Webapp release has been updated to ensure all users can register for an Event regardless of the Event’s UI Experience. Previously, the checkout process failed on the frontend without creating a Blackthorn Log entry, but the registration could be processed on the backend without an error.
May 29, 2025
The May 2025 Webapp Release has been reverted to a previous version because of issues related to a subset of users who are using an earlier version of the Events app with the Tabbed or Simple UI.
We have identified the underlying cause and are working to fix the problem. This is our top priority, and we are moving on it as quickly as possible.
May 28, 2025
As of May 28, 2025, the installation process for Caching 2.0 has been updated. Any new installations or upgrades to a new version of Events will automatically turn on Caching 2.0.
Off-Cycle Release
June 2, 2025
Attendees can click the Register button to register successfully for an Event. Previously, the checkout process failed on the frontend without creating a Blackthorn Log entry, but the registration could be processed on the backend without an error. (Known Issue: 000004852)
BT Salesforce Release
(Release Date: May 28, 2025)
Bug Fixes
Permission Sets: The “Enable Navigator Attendee Mobile App” (conference360__Enable_Attendee_Passport_App__c) was added to the Blackthorn | Events (Limited Access permission set in the Event’s object settings with Read, Edit permissions to ensure Event Organizers with a permission set other than Blackthorn | Events (Admin) can register Contacts for an Event. Previously, those Event Organizers could not register Attendees in the BT Events Attendee Registration component. (Known Issue: 000004605)
Attendee Groups: A primary Attendee in an Attendee Group will receive one confirmation email and the guest Attendee’s Email field will be blank if an Event has at least two Event Items with at least one with Type = “Guest” with Email = “Hide”, and the primary Attendee registers an Attendee Group with at least one Guest Ticket. Previously, the guest’s Attendee record’s Email field contained the primary Attendee’s Email, and the primary Attendee received two confirmation emails. (Known Issue: 000004527)
Zoom: If an Event Organizer edits an Event’s Event Start Date or Event Start Time in the Event Wizard or Builder, the saved changes will update accordingly on the Zoom dashboard. Previously, duplicate Zoom meetings were created. (Known Issue: 000004591)
Forms: If an Event Organizer deletes a conditional question from a Form Element with multiple conditional questions, they can accurately preview the parent question and remaining conditional questions in the Form Preview. Previously, they got the following error message when using the Form Preview: “This page has an error. You might just need to refresh it. First, would you give us some details? (We're reporting this as error ID: 1071447354).”
Events App: New installations of the Events app will occur as expected. Previously, users received an error if their org used Shield encryption for specific fields. (Known Issue: 000004835)
Event Builder
When an Event Organizer clones an Event in the Event Builder, the Builder will also clone any related Email Templates.
An Event Organizer can save new information in a Speaker’s Bio field after using the Event Builder to clone an Event with a Speaker with details in the Bio field and paste a new hyperlink and image in the Bio field. Previously, they got the following error: "This page has an error. You might just need to refresh it. First, would you give us some details? (We're reporting this as error ID: 60827494)" (Known Issue: 000004273)
Event Organizers will only see a red asterisk next to required fields when using the Event Builder. Previously, fields that were not required were marked with a red asterisk.
Enhancements
Email Component: The Email component’s Send Emails From field includes a new picklist value. The “Created By User” picklist option allows Event Organizers to set the FROM: email address to the user who created the Event, regardless of who triggers the email. Please note that the email of the user who created the Event must be configured as an organization-wide email address. (Known Issue: 000004163)
ERS: The max character limit for the Event Registration Submission Form JSON field was increased to 131,000 characters. Previously, the limit was 32,000 characters, which caused errors when long Forms (one or more Forms with many Form Elements) were submitted.
Scheduled Jobs: Event Organizers can set the chunk size for the AttendeeRollupToParent batch job by using the Batch Chunk Size field on the Scheduled Jobs tab in the Blackthorn | Events Admin tab and clicking the Schedule Attendee Parent Rollup Job button. This allows users to set the batch size to a smaller number to avoid a heap size limit exceeded error.
Add Attendee Component: The Add Attendee component's permission management has been updated. Campaign and Campaign Member object access is no longer a prerequisite for using this component. The following functionality now applies.
Users who have read permissions to one or more of the Account, Contact, Lead, Campaign, and Report objects can search the object(s) and add Attendees.
Users who can access the Account, Contact, Lead, Campaign, and Report objects will see Attendee records from these objects.
Users will only see Attendee records from the Account, Contact, Lead, Campaign, and/or Report objects they can access.
Users who don’t have access to the Account, Contact, Lead, Campaign, and/or Report objects will not see any Attendee suggestions as they cannot retrieve records related to those objects.
If a user who doesn’t have access to the Campaign object tries to load an Attendee who has already been added to the Event from the Campaign object, the user will see the Attendee, but they will not be able to see any Campaign-specific information they don’t have access to.
Guest Tickets: If an Event Organizer wants to leverage group waitlisting by including Guest Tickets in the group’s waitlist, even though some of those Tickets do not require an email address, they can use the Event Settings’ new Disable Email Check For Waitlisted Guest field to allow waitlisted Guest Tickets without an email.
If Disable Email Check For Waitlisted Guest is checked (enabled), an email will be optional for waitlisted Guest Tickets as long as the Guest Event Item’s Email field is marked as “Optional” or “Hidden.”
If Disable Email Check For Waitlisted Guest is not checked (disabled), an email will be required. (existing functionality)
Note: Waitlists for Guest Tickets without emails only work at the Event Item level, not at the Event level.
Object: Event Settings
Field Label: Disable Email Check For Waitlisted Guest
API Name: conference360__Disable_Email_Check_For_WaitlistedGuest__c
Data Type: Checkbox
Default: unchecked/disabled
Help Text/Description: When checked, waitlisted guest tickets do not require emails (make sure to mark the Email field visibility as ‘Optional’/’Hidden' on the Guest Event Item).
Updated Permission Sets:
READ/EDIT: Admin, Organizer, and Community/Platform User
READ: Lite User, Limited Access, and Read Only
Event Builder
Custom Metadata Types now includes the “Event Builder Configuration” metadata type with the following records: Emails, Sessions, FAQs, Speaker, Sponsor, Attendees, and Event Content. Event Organizers can simplify the Event Builder experience by setting the Event Builder Configuration custom metadata types to hide optional sections. The Tickets page cannot be hidden, and the Landing Page is visible by default and cannot be hidden. If the Visible field is not checked, the corresponding page will be hidden. If a record’s Visible field is checked, the corresponding page in the Event Builder will be visible.
When an Event Organizer opens the Event Builder to create or clone an Event with at least one Event Item with Type = “Main event ticket,” they will see the following message at the top of the Landing Page. ‘'To publish, please create at least one ticket. (Donations and Guest event items must accompany Main Event Ticket and Custom Ticket.)'' Closing the message will prevent it from reappearing while the user is logged in.
The field sets listed below were updated to include the following fields in each field set’s “Available Fields” section. Event Organizers can now add these fields to the Event Wizard/Event Builder page layouts.
Blackthorn | V2 Event Wizard Venue Section
Calendar Location (Event.Calendar_Location__c)
Calendar Description (Event.Calendar_Description__c)
Blackthorn | Events Wizard Ticket Fields
Default Quantity Selection (Event_Item.Default_Quantity_Selection__c)
Minimum Quantity (Event_Item.conference360_Minimum_Quantity__c)
Maximum Quantity (Event_Item.conference360_Maximum_Quantity__c)
Blackthorn | Events Wizard Event Fields
Free (Event.Free__c)
Post Registration (Event.After_Submission__c)
Redirect URL (Event.Registration_Redirect_URL__c)
Registration Success Message (Event.Success_Message__c)
Automated Email From Address (Event.Automated_Email_From_Address__c)
Confirmation Email (Event.Confirmation_Email__c)
Waitlisted Email (Event.Waitlisted_Email__c)
Waitlisted Pending Email (Event.Waitlisted_Pending_Email__c)
Organizer (Contact) (Event.Organizer_Contact__c)
Zoom Registration Approval Type (Event.Zoom_Registration_Approval_Type__c)
Include Zoom URL In Calendar Description (Event.Include_Zoom_URL_In_Calendar_Description__c)
Zoom Email Notifications (Event.Zoom_Email_Notifications__c)
Zoom Personal Meeting ID Enabled (Event.Zoom_Personal_Meeting_ID_Enabled__c)
Webinar/Meeting ID (Event.Webinar_ID__c)
Calendar Location (Event.Calendar_Location__c)
Calendar Description (Event.Calendar_Description__c)
Waitlists
Salesforce will now track when an Attendee registers for an Event’s waitlist. This new information will be used when an Event Organizer manually creates an Attendee record and invites the Attendee, but the Attendee joins the waitlist later. Previously, Attendees with Attendee records created at an earlier date could skip ahead of others in the waitlist queue based on their Attendee record creation date and time. The waitlist sequence is now determined by the waitlist join date and time.
If an Attendee with Registration Status = “Registered” cancels their registration after an Event ends, the next person on the Event’s waitlist will not receive an email stating they can complete their registration.
Webapp Release
(Release Date: June 11, 2025)
Bug Fixes
Checkout Process
When an Attendee redeems an Event Item from their AttendeeLink and then adds a Donation to their cart during checkout, their Attendee information will remain. Previously, the Attendee information was deleted after the Donation was added, even though the fields were locked.
During checkout, the total amount due will recalculate correctly after an Attendee applies and removes a discount Code when the Event has a Payment Processing Fee and either a “Calculated at Checkout” or “Tax-Inclusive Pricing” Tax. Previously, removing the discount Code did not trigger the recalculations, causing an incorrect amount to be shown in the Summary.
If an Event has an associated Fee, the Attendee will see the Fee amount in the Summary section and the amount due after adding Event Items and Sessions, if included, to the cart.
When a single Attendee completes the Event checkout process, a single Event Registration Submission (ERS) record will be created. Previously, multiple ERS records were incorrectly generated.
Enhancement
Custom Content: Event Organizers can now add Custom Content (rich text, images, embedded YouTube video, etc.) to Events with the UI Experience set to “Dynamic.”
Coming Soon
This section covers fields, and sometimes functionality, that are part of a new or updated feature but aren’t quite ready to be used yet.
Event Organizers will be able to use the new Event Settings Enable Add to Wallet from AttendeeLink field to show or hide the Add to Apple Wallet button on an AttendeeLink. If Enable Add to Wallet from AttendeeLink = “Show,” Attendees can add their Ticket and QR code to their mobile wallet by clicking the Add to Apple Wallet button on their AttendeeLink.
Object: Event Settings
Field Label: Enable Add to Wallet from AttendeeLink
API Name: conference360__Enable_Add_to_Wallet_from_AttendeeLink__c
Data Type: Dropdown
Options: Show/Hide
Default: Show
Description/Help Text: When set to “Show,” users can add their ticket and QR code from AttendeeLink to their mobile wallet.
Updated Permission Sets
READ/EDIT: Admin, Organizer, and Community/Platform User
READ: Lite User, Read Only, and Limited Access
Event Organizers will be able to use the Event Default Display Density field to change how an Event with UI Experience = “Dynamic” appears on the Event’s webpage.
Object: Event
Field Label: Default Display Density
API Name: conference360__Default_Display_Density__c
Data Type: Picklist
Default: Hide
Help Text: Determines the initial UI display density when the UI Experience is set to “Dynamic.”
Hide (Default): Hides the toggle button on the UI.
Comfy: Loads the UI to Comfy mode by default.
Compact: Loads the UI to Compact mode by default.
Permission Set Updates
READ/EDIT: Admin, Organizer, Limited Access
READ: Lite
Field/Layout Updates
New
Object: Event Settings
Field Label: Disable Email Check For Waitlisted Guest
API Name: conference360__Disable_Email_Check_For_WaitlistedGuest__c
Data Type: Checkbox
Help Text/Description: When checked, waitlisted guest tickets do not require emails (make sure to mark the Email field visibility as ‘Optional’/’Hidden' on the Guest Event Item).
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.