Please review the updates below and follow the upgrade instructions to upgrade your Events application.
Table of Contents
Breaking Change
Blackthorn | Events (Lite User) Permission Set Update
The Blackthorn | Events (Lite User) permission set now only includes Read access for the Event object. Previously, the Blackthorn | Events (Lite User) permission set had Edit access to the Event object.
BT Salesforce Release
(Release Date: November 19, 2025)
Bug Fixes
Event Builder: Users will no longer see the Email tab in the Event Builder if they switch from "Clone an Event" to "Begin from Scratch" without closing the Builder.
Event Records: Event Organizers can edit an Event’s Event Start Date and Event End Date fields without causing an error if the Event has more than 200+ Sessions. Previously, Event Organizers were unable to edit the Event’s Event Start Date and Event End Date fields. (Known Issue: 000004882)
Form Elements: If a checkbox field exists on the Attendee, Contact, Lead, or Account object, and a Form Element has Type = “Hidden” and Maps To (Object) = “Attendee,” “Contact,” “Lead,” or “Account,” then the checkbox will be an option in the Maps To (Field) field dropdown. Previously, the checkbox field wasn’t visible when using hidden Form Elements. (Known Issue: 000004991)
Permission Sets: The Blackthorn | Events (Lite User) permission set now only includes Read access for the Event object. Previously, the Blackthorn | Events (Lite User) permission set had Edit access to the Event object.
Advanced Visibility: When an Event Organizer previews the list of Contacts that match eligibility/visibility rules, they will see a maximum of 10 Contacts. Previously, more than 10 Contacts were shown.
Experience Cloud: When a community user accesses a registration page to sign up for a customer portal account and register for an Event, the new customer portal account and Contact record are created. Previously, the community user was unable to create a customer portal account for Events with over 200 Sessions, which also prevented the creation of a Contact record. (Known Issue: 000005092)
Smart Scheduler: When using the Smart Scheduler to send an email, the Event Admin can enter an email in the To Email field and save the email as a draft. Previously, the Event Admin was unable to save the value in the To Email field after clicking Save Draft when trying to schedule an email. (Known Issue: 000004416)
Import Attendee Records
Attendee records imported via the Add Attendees component on an Event will have the Registration Status set to "To Invite" when the related Campaign only includes custom Campaign Member Status values. The exception to this is if the Campaign has a different value in the Attendee "To Invite" Status field. Previously, the imported Attendee records had a blank Registration Status field. (Known Issue: 000004984)
The value in an Event record’s Invited field will equal the number of Attendees with Registration Status set to “Invited” when an Event Organizer imports Attendees using the Event Builder and sends an invite using the Send Invite button on the Event record page. Previously, the Invited field did not update. (Known Issue: 000003578)
Enhancements
Events App: The Blackthorn Events Lightning app name was updated to include the “Blackthorn |” prefix.
Events (Planner) > Blackthorn | Events (Planner)
Events (Admin) > Blackthorn | Events (Admin)
Waitlists: When an Attendee joins an Event’s waitlist, the entered email will be saved in the Attendee’s Primary Email field. Previously, the field remained blank until the Attendee was registered and taken off the waitlist.
Email Templates: When a user saves an Email Template after editing it from a related Event record, they will be redirected back to the Event record. If the user opens the Email Template from the Related List on the Event record, they will be returned to the Related List.
Advanced Visibility: If an authenticated user creates an Experience Cloud Contact via self-registration, the Advanced Visibility Contact will trigger an update to the visibility on related Event Items. The updated visibility will also be extended across the related Bucket Account.
Event Settings: When an Admin checks the Event Settings Auto Redirect Users to Confirmation Page field, authenticated users (EC users, authenticated iframe, AttendeeLink users) will be automatically redirected to their AttendeeLink when re-visiting the (non-AttendeeLink) Events URL.
Object: Event Settings
Field Label: Auto Redirect Users to Confirmation Page
API Name: conference360__ Auto_Redirect_Users_to_Confirmation_Page__c
Data Type: Checkbox
Default: unchecked
Description/Help Text: When enabled, authenticated users (EC users, authenticated iframe, AttendeeLink users) are automatically redirected to their confirmation page when previously registered.
Updated Permission Sets
READ/EDIT
Blackthorn | Events (Organizer)
Blackthorn | Events (Admin)
Blackthorn | Events (Community Platform User)
READ Only
Blackthorn | Events (Limited Access)
Blackthorn | Events (Lite User)
Blackthorn | Events (Read Only)
BT Forms: The following objects in the Base package were previously used by a legacy app and have been deprecated. This change does not impact the Form functionality in the Events package.
BT Form (bt_base__Form_c)
BT Form Big List Group (bt_base__Form_Big_List_Group__c)
BT Form Big List Option (bt_base__Form_Big_List_Option__c)
BT Form Element (bt_base__Form_Element__c)
BT Form Element Condition (bt_base__Form_Element_Condition__c)
BT Form Submission (bt_base__Form_Submission__c)
BT Form Submission Answer (bt_base__Form_Submission_Answer__c)
Permission Sets: The Blackthorn | Events (Lite User) permission set was updated to include core functionality related to the Mobile Check-in app.
Read-only permissions were added for the following objects: Account, Contact, and Badge Printing Configuration (conference360__Badge_Printing_Configuration__c).
Read-only permissions were added for the following fields:
Object: Badge Printing Configuration
Length Unit (conference360__Length_Unit__c)
Orientation (conference360__Orientation__c)
Page Height (conference360__Page_Height__c)
Page Width (conference360__Page_Width__c)
Object: Contact
Email (Email)
Additional permissions were added to the Mobile Check In Submission (conference360__Mobile_Check_In_Submission__c) object and fields.
Create and edit permissions were added for the Mobile Check In Submission object.
The following fields now have edit permissions:
Attendees JSON (conference360__Attendees_JSON__c)
Errors (conference360__Errors__c)
Status (conference360__Status__c)
Invite-only Events
Event Organizers can use the new Event Settings Invitee Verification Method field to designate whether all Events related to the Event Settings record are invite-only.
Object: Event Settings
Field Label: Invitee Verification Method
API Name: conference360__ Invitee_Verification_Method__c
Data Type: Picklist
Values: “Attendee Email Match”, “None (default)”
Description: Prevents access to the event registration page until the invitee’s access is verified.
Help text: Verification required for non-authenticated users to register for an event.
Updated Permission Sets:
READ/EDIT
Blackthorn | Events (Admin)
Blackthorn | Events (Organizer)
Blackthorn | Events (Community/Platform User)
READ ONLY
Blackthorn | Events (Lite User)
Blackthorn | Events (Limited Access)
Blackthorn | Events (Read Only)
An email entered by an invitee will be compared against Attendee records related to an Event to determine if they can register for the Event. If an email is found, they will be redirected to their AttendeeLink.
Scenario 1: If a potential Attendee enters an email that matches the Email (conference360__Email2__c) on one Attendee record related to the Event, then Events will redirect the registrant to their AttendeeLink so they can register for the Event.
Scenario 2: If a potential Attendee enters an email that matches an Email (conference360__Email2__c) on two or more Attendee records related to the Event, then Events will use the data in the first match when redirecting the registrant to their AttendeeLink.
Scenario 3: If a potential Attendee enters an email address that doesn’t match the Email (conference360__Email2__c) on an Attendee record, then Salesforce will display an error message.
Webapp Release
(Release Date: November 19, 2025)
Bug Fixes
Event Settings: Registrants can see a Form question’s text when the Event’s UI Experience is set to “Tabbed” and the related Event Settings Card Color Theme is set to “Dark.” Previously, the registrant could not see the text as the font color was the same as the background color. (Known Issue: 000004863)
Time Zones: An Attendee will see the time zone “SGT” when an Event has the Time Zone set to “Asia/Singapore.” Previously, Attendees saw “SST” (Samoa Standard Time) instead of “SGT” (Singapore Standard Time). (Known Issue: 000004904)
Form Elements: If an Event with UI Experience = “Simple” includes a Form that has a Form Element with Type = “Picklist” and Hint = blank, then the registrant won’t see any text in the picklist question field. Previously, the registrant saw “question.hint” even though the Hint field was blank. (Known Issue: 000004941)
Advanced Visibility: If a Contact matches the visibility requirement for a Session but not the eligibility requirement and tries to register for the Session manually, they will see a grayed-out Add Session button. Eligible Contacts within the household account can register as expected.
Add to Calendar: An Attendee who registers for an Event with Sessions from an Experience Cloud or an iframed Event can click the Add to Calendar and Google (connect to app) buttons to add the Event and Sessions to their Google Calendar. Previously, the Attendee got an error when trying to add the Event and Sessions to their Google Calendar.
Forms for Sessions: Logic related to Conditional Questions/Form Elements and Sessions was updated to ensure the Attendee sees the default answer in the following scenarios. Previously, the Attendee had to refresh the page to see the default answer.
If a Conditional Question doesn’t include a default answer but does include a hint, then the Attendee will see only the hint.
If a Conditional Question includes a default answer but no hint, then the Attendee will see only the default answer.
If a Conditional Question includes a default answer and a hint, then the Attendee will see both the default answer and the hint.
Authenticated Users: After an authenticated user (Contact) registers for an Event via an Experience Cloud/Community or iframed webpage, they will be redirected to their AttendeeLink. Previously, the registered Attendee was returned to the registration page, causing confusion. (Known Issue: 000003369)
Enhancements
Session Keywords: When registering for an Event (UI Experience = “Dynamic”) that has Sessions, Attendees can filter the Sessions by keywords during the registration process. The keywords an Attendee uses to filter Sessions come from Session Keyword (conference360__Session_Keyword__c) objects. A Session Keyword object links a Keyword (conference360__Keyword__c) to a Session.
Event Groups: When selecting an Event from an Event Group with UI Experience set to “Calendar,” a user can open the Event by pressing the Enter key. The updated functionality matches the List UI. Previously, the browser’s focus jumped to the corresponding Event on the list underneath the calendar.
Form Elements - Big List Groups: To ensure that the Big List Group options load when a user clicks into the dropdown, the process for retrieving the options has been updated to load each list independently. The system also double-checks for data before returning an empty dropdown list. Previously, when an invitee tried to select an option in a Big List Group, the dropdown options would not display unless all lists were loaded within the time limit.
Accessibility
If a registrant views an Event Group in a smaller viewport and uses the filter component (a side panel) to filter the Events, they can click the “ESC” (escape) key on their keyboard to exit the side panel. Previously, they had to use their mouse to close the side panel, making the filters less accessible.
The following accessibility-related updates were made to the Social Share modal, ensuring users have access to the information.
Icons: The screen reader will announce each social media icon as a descriptive button, e.g., "Share on Twitter button" or "Share via Email link."
Close (X) Button: Users can focus on the Close (X) button using keyboard navigation. The screen reader will announce the button as "Close dialog button." Users can clone the dialog box by clicking the Escape key.
Copy Icon: The screen reader will announce the Copy icon as “Copy link button.” Users can interact with the Copy icon via the keyboard and screen reader.
Share Prompt: Users can access the share prompt via keyboard navigation.
Descriptive Labels: The screen reader will announce a descriptive label such as “Event share link, read-only” or “This is the link to share the event.” The explanatory text will help users determine if the field contains a URL intended for sharing.
Event-only Invites
When the invite-only feature is enabled, an Attendee must enter their email and click Verify Email to confirm they are eligible to register for the Event. If the Attendee enters an email that isn’t eligible, they will see the following error. “This email is not recognized. Please contact the event organizer."
If an Attendee goes to the cart page without first verifying their email, they will be redirected to the Event Overview page, where they will be asked to verify their email.
If an Attendee views an Event webpage on a mobile device and the invite-only feature is enabled, they won’t see the Get Tickets button until they have verified their email address.
reCAPTCHA
If the reCAPTCHA flag is enabled (Event Settings Enable Captcha = checked), Attendees will complete the following steps: enter a valid email address, complete the reCAPTCHA challenge, and click Verify Email.
If the reCAPTCHA flag is disabled (Event Settings Enable Captcha = unchecked), Attendees will complete the following steps: enter a valid email address and click the Verify Email button.
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.
The Event object now includes the Post Event Survey Expiration Date field, which allows Event Organizers to define how many days after the Event’s Event End Date the post-event survey (Form) should be available to Attendees. The minimum value is 0 days, and the maximum value is 30 days. “0” means the post-event survey will go offline on the same date as the Event’s Event End Date.
Object: Event
Field Label: Post Event Survey Expiration Date
API Name: conference360__Post_Event_Survey_Expiration_Date__c
Data Type: Number
Default: 14
Description/Help text: This field defines how many days after the Event End Date the post-event survey should be available for users. It defaults to 14 days, meaning the post-event survey will be online for 14 calendar days after the Event End Date. The minimum value is 0 days (The post-event survey is not available on the Event End Date). The maximum value is 30 days.
Permission Sets Updates
READ/EDIT
Blackthorn | Events (Admin)
Blackthorn | Events (Organizer)
Blackthorn | Events (Community/Platform User)
Blackthorn | Events (Limited Access)
READ ONLY
Blackthorn | Events (Lite User)
Blackthorn | Events (Read Only)
The Post Event Survey Expiration Date field was also added to the Event’s “Blackthorn | Event Builder Event Details Section” field set for use in the Event Builder.
When an Event Organizer enables the Show as ‘Venue Map’ on Navigator App field, and the Event Content record’s Category field is set to “Map,” the Event Content record will be identified as venue-map related and displayed in the “Venue Map” section in the Navigator app.
Object: Event Content
Field Label: Show as ‘Venue Map’ on Navigator App
API Name: conference360__Show_As_Venue_Map_On_Navigator__c
Data Type: Checkbox
Description/help text: When enabled, this Event Content record is surfaced under the ‘Venue Map’ section of Navigator and will not be shown under the ‘Event Content’ tab. Enable this setting if this document shows a map of the venue.
Permission Set Updates
READ/EDIT
Blackthorn | Events (Admin)
Blackthorn | Events (Organizer)
Blackthorn | Events (Community/Platform User)
READ ONLY
Blackthorn | Events (Events Lite)
Blackthorn | Events (Read Only)
Blackthorn | Events (Limited Access)
Upcoming Deprecation of the Full-Width UI
We’re continuing to modernize the Events' user experience and will be deprecating the Full-Width UI. Additional information about the upcoming changes will be provided for those currently using the Full-Width UI.
Going forward, we recommend not selecting the Full-Width UI for future Events.
Field/Layout Updates
New
Object: Event Settings
Field Label: Auto Redirect Users to Confirmation Page
API Name: conference360__ Auto_Redirect_Users_to_Confirmation_Page__c
Data Type: Checkbox
Description/Help Text: When enabled, authenticated users (EC users, authenticated iframe, AttendeeLink users) are automatically redirected to their confirmation page when previously registered.
Object: Event Settings
Field Label: Invitee Verification Method
API Name: conference360__ Invitee_Verification_Method__c
Data Type: Picklist
Description: Prevents access to the event registration page until the invitee’s access is verified.
Help text: Verification required for non-authenticated users to register for an event.
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.