Please review the updates below and follow the upgrade instructions to upgrade your Events application.
Table of Contents
BT Salesforce Release
(Release Date: April 8, 2026)
Bug Fixes
Invoices and Fees: When an Attendee completes checkout with a total that includes a Payment Processing Fee, the Invoice now correctly marks the Payment Processing Fee as paid and displays a Payment Status of "Paid." Previously, the Payment Processing Fee was included in the checkout total and paid successfully, but the Invoice flagged it as outstanding with a Payment Status of "Partially Paid."
Event Registration Submission (ERS): ERS now process correctly when the Event has a Remaining Capacity of one or the Event Item has a Quantity Remaining of one. Previously, when an Event's Remaining Capacity or an Event Item's Quantity Remaining equaled one, the ERS failed with a "Sold Out" error even though capacity was still available. This prevented the Attendee record from being created and the confirmation email from being sent. (Known Issue: 000005281)
Campaign Members: Campaign Member records are now correctly created for all Attendees who register, even when multiple Attendees related to the same Lead or Contact register for multiple Events in rapid succession. Previously, when a single Attendee registered for multiple Events in quick succession, the Campaign Member creation job did not create enough Campaign Member records.
Form Element: The Character Length field on Form Elements with Type set to "Text" and "Text (30,000)" now has a default value of 255 or 30,000, respectively. The webapp enforces the maximum character count based on this value, preventing Attendees from entering text that exceeds the field limit. Previously, the Character Length field had no default value, allowing Attendees to enter text exceeding 255 characters. This caused the Event Registration Submission (ERS) record to fail, and no Attendee record was created. (Known Issue: 000005006)
Waitlist Registrations: Attendees can now successfully register for an Event's waitlist when a Ticket is sold out. Previously, Attendees attempting to register for a waitlisted Ticket received a "Warning: Checkout failed, please try again later." error.
Enhancements
Event Builder: The Event Item's Require At Least One Session checkbox is now visible in the Event Builder's ticket creation section. Event Organizers can configure whether Attendees must select at least one Session to complete registration without having to navigate to the Event Item record. The field's default is unchecked, and the field only appears for Ticket-type Event Items (not Donations or Products).
Attendee Registration Component: Event Organizers can successfully register guests (Event Item Type = “Guest”) for an Event using the Attendee Registration Component. Previously, Event Organizers encountered an error. Please remember that guest registrations should always be associated with an Attendee with an Event Item Type = “Main event ticket.”
Custom Settings > Blackthorn | Base Settings: The Blackthorn | Base Settings custom setting has a new field: Enable PersonAccount Trigger. The new field only applies to orgs with PersonAccounts enabled. * When Enable PersonAccount Trigger is checked (enabled), changes to PersonAccount records will trigger Advanced Visibility (AV) rule recalculations. Previously, AV rule recalculations were only triggered by Contact record changes. Because PersonAccounts function as both Account and Contact records, changes to PersonAccount fields referenced in AV rule conditions now automatically trigger a recalculation.
Custom Setting: Blackthorn | Base Settings
Field Label: Enable PersonAccount Trigger
API Name: Enable_PersonAccount_Trigger__c
Data Type: Checkbox
Default Value: false (unchecked)
Help Text: Enables the Account trigger for PersonAccount records to trigger Advanced Visibility rule recalculation. Only applicable in orgs with PersonAccounts enabled.
Attendee Visibility Rules — PersonAccounts: For orgs with PersonAccounts enabled, Attendee Visibility (AV) rules now recalculate when a PersonAccount record is inserted, updated, or deleted. The eligibility and visibility results are then sent to the Events webapp. The trigger is controlled by the Blackthorn | Base Settings custom setting, Enable PersonAccount Trigger, and is disabled by default. Previously, updates to PersonAccount records did not trigger AV rule recalculation, even when the related Contact's AV Contact trigger was enabled. Important Prerequisites: Enable the following: Caching 2.0, Advanced Visibility, and PersonAccounts in your Salesforce org. You must also contact Blackthorn Support to enable this feature.
Webapp Release
(Release Date: April 8, 2026)
Bug Fixes
Custom Content/Navigator: Custom Content with a Display Location set to "Navigator" now only appears in the Navigator app and no longer appears on the Event webpage. The Event Settings Custom Tabs field acts as a master control: when set to "Always," each piece of Custom Content displays only where its individual Display Location specifies ("Navigator," "Webapp," "Both," or "None"). Previously, setting the Display Location to "Navigator" caused the Custom Content to appear in both the Event's webpage and the Navigator app.
Event Settings: If an Event has more than 10,000 Attendees, Event Organizers can now save the related Event Settings record when the Remove URL from Attendee Links field is enabled. Previously, attempts to save the Event Settings record failed because the query exceeded query limits, and the user saw the "conference360.Event_Trigger: System.LimitException: conference360:Too many DML rows: 10001" error message. (Known Issue: 000005277)
Registration Confirmation: When an Attendee with the Registration Status set to "Invited" or "Pending" registers for an Event using the Simple UI from their AttendeeLink, the registration confirmation message displays correctly. Previously, the confirmation message was not visible, causing confusion for the Attendee.
Image Rendering: Images on Event webpages (such as Event banners, Speaker photos, and Session images) now consistently render at full quality. Previously, images could intermittently appear blurry or pixelated because the webpage occasionally finished loading the image before it had determined the correct display size, causing the image to render at a smaller resolution than intended.
Data Dictionary
If an Event's Post Event Questions Form includes a Data Dictionary Group with a Data Dictionary Entry that has the Key set to "MSG_SURVEY_TITLE" and the Value contains a "single space character," then the title on the post-Event survey will be blank. Previously, Attendees saw the title instead of a blank space. (Known Issue: 000005201)
If the text in the Data Dictionary Entry's Value field is extra-long, the resulting text will wrap correctly within the Event Item container on mobile devices. Previously, if the Key was set to "MSG_MAX_ITEMS_SELECTED" and the Value field contained extra-long text, the resulting text overflowed the container, breaking the page layout on mobile devices. (Known Issue: 000005037)
The debug feature that highlights Keys in a URL now works correctly for an Event with a Post-Registration Form. Previously, using the debug feature with an AttendeeLink URL caused the Post-Registration Form either not to load or to display an error. (Known Issue: 000005144)
Form Elements
Big List Group: For Events where the UI Experience is set to "Dynamic" and the registration Form includes a "Big List Group" Form Element, the Attendee now sees the "Please select an option from the list" error message below the field when they type a value that does not match a predefined option. Previously, the Form displayed a generic "Please correct errors in your information" error, or in some cases, no field-level error message appeared. (Known Issue: 000005222)
UTM Parameter: When an Attendee registers for an Event with a Form that includes a UTM Parameter Form Element, the UTM parameter values are correctly captured and saved to the Form Submission Answer and Event Registration Submission (ERS) records. Additionally, if those Events are part of an Event Group with a URL containing UTM parameters, the Events' banners no longer flicker or become unclickable. Previously, UTM parameter values from the URL were not saved to Form Submission Answer or ERS records, and Event Group pages with UTM parameters in the URL caused Event banners to flicker and become unclickable. (Known Issue: 000005265)
Smart Scheduler
Attendees who register for an Event after an initial email is scheduled in Smart Scheduler will now receive the scheduled email. Previously, the Smart Scheduler did not add newly registered Attendees to the email list after the email was scheduled, so those Attendees did not receive it.
If an Event meets the criteria defined in an email schedule created in the Smart Scheduler, emails related to the Event will be sent to Attendees. Previously, not all Events that met the criteria were identified, so emails for those Events were not sent.
Enhancements
Accessibility: When Caching 2.0 is enabled, and infinite scroll is active, Attendees on an Event Group or Event webpage can use keyboard navigation to jump to the cookie consent banner by clicking the Skip to Consent Banner button. Previously, Attendees using keyboard navigation had to tab through all page content before reaching the consent banner, and on pages with infinite scroll, dynamically loaded Event Items could prevent them from reaching the banner.
Translations: The Event webpage's Language Selector now includes the following additional languages available for Translation: Belarusian, Croatian, Norwegian Bokmål, Portuguese (Brazil), Slovenian, Spanish (Mexico), and Ukrainian.
Sessions: An Event using either the Dynamic or Tabbed UI offers at least one Ticket with several related Sessions. When an Attendee registers a group of Attendees for the same Ticket type and adds a Session related to the Ticket, the Copy Session Selection to all [Ticket Name] button will appear below the selected Session. Clicking the button copies the first Attendee's Session selection to all other Attendees with the same Ticket type. If copying a Session selection exceeds the Session's capacity, an error will appear. Note: The registrant can still adjust the Session selections for the other Attendees in the group after clicking the Copy Session Selection to all [Ticket Name] button.
Event Groups: When an Event Group's UI Experience is set to "Aspen" or "Maple," then an Event Item's Public Item Name (title) on an Event Group webpage will display up to six lines of text. Previously, titles were limited to three lines and could be cut off, even at 100% browser zoom.
Invite-only Events
When an Invite-only Event has the Event Settings Invitee Verification Method field set to "Attendee Email Match," Attendees cannot re-register after completing their initial registration. This prevents duplicate registrations after an Attendee clicks Done or revisits the Event webpage. It also blocks unauthorized registrations if an Attendee shares their AttendeeLink with another individual. Previously, Attendees could complete additional registrations by re-accessing the Event webpage or using a forwarded AttendeeLink.
If an Invite-only Event has multiple Ticket types (General Admission, VIP, etc.), and the Event Settings Invitee Verification Method field is set to "Attendee Email Match," Attendees cannot modify their Ticket type selection after initial verification. This prevents unauthorized Ticket additions when an Event Organizer forwards an AttendeeLink to an Attendee, ensuring that invited Attendees can register only for their designated Ticket. It also blocks unauthorized registrations if an Attendee shares their AttendeeLink with another individual and that individual tries to change the Ticket type.
Field/Layout Updates
New
Custom Setting: Blackthorn | Base Settings
Field Label: Enable PersonAccount Trigger
API Name: Enable_PersonAccount_Trigger__c
Data Type: Checkbox
Default Value: false (unchecked)
Help Text: Enables the Account trigger for PersonAccount records to trigger Advanced Visibility rule recalculation. Only applicable in orgs with PersonAccounts enabled.
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.