Please review the updates below and follow the upgrade instructions to upgrade your Events application.
Table of Contents
BT Salesforce Release
(Release Date: July 16, 2025)
Bug Fixes
Email Component: Event Organizers can send emails with merge tags in the email subject and body from an Attendee record. Previously, the user got the following error: “Send Email failed. Only aggregate expressions use field aliasing” (Known Issue: 000004845)
Blackthorn | Events Admin Tab: Users working in a Salesforce sandbox can click the Create Test Records and Create Email Templates buttons on the Configuration tab in Blackthorn | Events Admin to create test records and Email Templates. Previously, no test records or Email Templates were created in the sandbox. (Known Issue: 000004768)
Time Zones: If an Event Organizer uses the Event Wizard to change an Event’s Time Zone (conference360__Time_Zone__c), the related Session’s Start Date/Time (conference360__Start_Date_Time_GMT__c) and End Date/Time (conference360__End_Date_Time_GMT__c) fields will be updated to reflect the new time zone. Previously, the Session’s GMT time zone values were not updated. (Known Issue: 000004867)
Smart Scheduler: A user using an org with many objects (e.g., 600+ objects) can use the Smart Scheduler Admin in the Events app to schedule new messages. Previously, the user got an “Apex heap size too large: 6106827” error and could not select an object.
ERS Records: Processing ERS records will occur as expected. Previously, processing an ERS record that included approximately 23 Attendees caused the following error: “conference360.EventRegistrationSubmission: System.LimitException: Apex CPU time limit exceeded.” (Known Issue: 000004811)
BT Rule Component
When using the BT Rule component to add BT Rule Conditions to a BT Rule, the user can change the Field selection in a saved BT Rule Condition from one picklist field to another. Previously, changing the picklist fields caused an error.
An Admin whose org has a large amount of data can use the BT Rules Component (Advanced Visibility) to create new BT Rules and preview eligible Contacts. Previously, the user ran into an internal server error. (Known Issue: 000004832)
Users can create a BT Rule Condition referencing a picklist value that includes standard Salesforce picklist characters, including apostrophes. Previously, the user got an error when saving a BT Rule Condition with a picklist value that included an apostrophe. (Known Issue: 000004788)
Table Manager
When an Event Organizer uses the Table Manager to assign Attendees to a Table, but the Event has more than 100 Attendees, they will see the following message instead of the list of Attendees. “This event has over 100 attendees. Use search to find specific attendees, since loading the full list could impact performance.” If the Event has fewer than 100 Attendees, the Event Organizer will see the list of Attendees. Previously, when an Event had more than 50,000 Attendees and an Event Organizer tried to create a Table and assign Attendees, they received the “conference360:Too many query rows: 50001” error message. (Known Issue: 000004410)
If an Event Organizer uses the Table Manager to move an Attendee from a full Table to another Table, they can add a second Attendee to the first Table. Previously, when the Event Organizer tried to add the second Attendee to the first Table, they could not save the changes. (Known Issue: 000004802)
Enhancements
Event Builder
Speakers
When an Event Organizer uses the Event Builder to edit, clone, or create a new Event with no Speakers and navigates to the Speakers tab, they will see the New Speaker screen that allows them to enter information. They will no longer see an empty preview screen.
If an Event Organizer edits or clones an Event that already has Speakers related to it, they will see a list of the Speakers.
Sessions
When an Event Organizer uses the Event Builder to edit, clone, or create a new Event with no Sessions and navigates to the Sessions tab, they will see the New Session screen that allows them to enter information. They will no longer see an empty preview screen.
If an Event Organizer edits or clones an Event that already has Sessions related to it, they will see a list of the Sessions.
Sponsors
When an Event Organizer uses the Event Builder to edit, clone, or create a new Event with no Sponsors and navigates to the Sponsors tab, they will see the New Sponsor screen that allows them to enter information. They will no longer see an empty preview screen.
If an Event Organizer edits or clones an Event that already has Sponsors related to it, they will see a list of the Sponsors.
Webapp Release
(Release Date: July 16, 2025)
Bug Fixes
Registered Sessions: If an Event Item has the Sales End Date in the past, and an Attendee is registered for one or more Sessions, they can see their registered Sessions under “My Agenda” on their AttendeeLink Previously, if the related Event Settings Show Expired Tickets was not checked, and the Event Item’s Sales End Date was in the past, Attendees could not view their registered Sessions on their AttendeeLink. Instead, they saw a "No sessions available" message. (Known Issue: 000004789)
Event Items: If the Event Item’s Minimum Quantity is set to “x”, and the Default Quantity Selection is set to “y”, then when the registrant clicks the Get Ticket or Buy Ticket button, the number of Tickets added to the cart will be “x” (minimum quantity) instead of “y” (default amount). The registrant can click the + button to add more Tickets to the cart. They can also click the – button to remove Tickets from the cart, but the number of Tickets in the cart will not go below the Minimum Quantity value. Previously, when an Event Item’s Minimum Quantity was set to a number greater than one, and a registrant clicked the Buy Ticket button, only one Ticket was added to the cart. Additionally, when the registrant clicked the + button to increase the number of Tickets, the value was reset to zero before adding Tickets. (Known Issue: 000004712)
Event Registration: When a registrant, who has multiple people in their group, adds Tickets and a Donation or Product to their cart using Express Registration, the Product/Donation dropdown will only list registrants with a “Main event item” Ticket. Additionally, there won’t be an information form for the Product or Donation. Previously, the registrant could choose from anyone in the group. (Known Issue: 000004800)
AttendeeLink: The maximum number of related records supported per Event has been updated from 2000 to 4000. However, we caution that Events with over 2000 related records may experience some sluggishness. Previously, Attendees accessing Events with over 2000 related records from their AttendeeLink could not see all related Sessions.
Enhancements
Accessibility
A screen reader’s announcement of the Cancel (x) button in the Order Summary will identify the button’s corresponding Ticket(s) in the cart. Previously, screen readers misread the Cancel (x) button for all ticket types in the Order Summary, confusing readers using assistive technologies.
Multiple Main/Guest Tickets and Products: When a screen reader navigates to a Cancel (x) button, it will announce the action and specific ticket, e.g., “Remove First [Ticket Name] [ticket type]” or “Remove Second [Ticket Name] [ticket type]”
Single Main/Guest Ticket and Products: When a screen reader navigates to a Cancel (x) button, it will announce the action and specific ticket, e.g., “Remove [Ticket Name] [ticket type]”
When an Attendee uses a screen reader to tab through a Form, the reader will announce the main question and any supplemental instructions associated with the picklist or multi-select picklist components, helping users to understand the question and its context.
In the Session selection step of the checkout process, screen readers will read the following buttons as such:
Add: “Add selected session.”
Add All: “Add all available sessions.”
Remove: “Remove selected session.”
Remove All: “Remove all added sessions.”
When an Event has the UI Experience set to “Tabbed” and an Attendee uses either a screen reader or a keyboard to move between the navigation tabs (Sessions, Speakers, Sponsors, etc.), then clicking a navigation tab will move the focus to the first focusable element on the new page’s primary content area.
When a registrant uses a screen reader on the Attendee Details page for an Event with the Dynamic, Tabbed, or Simple UI and the page includes dropdown or multi-select (Form) questions, the screen reader will announce the supplemental question or instructions related to that dropdown/multi-select question. The screen reader will read the information in the following order: question, extra information (if present), hint (if present), and options.
When a screen reader in browse mode moves through an Event Group with the UI Experience set to “Calendar,” the following will occur.
A user can select an Event, and the screen reader will only read its details instead of continuously reading the entire list of Events without landing on the selected Event’s details.
The screen reader will announce only relevant Event details instead of repeating “link” before each detail. The word "link" will only be used if the item is an interactive hyperlink.
Spreedly Gateway Updates for Iframes
Spreedly has updated its authentication requirements for iframes, resulting in changes to the Events app’s iframe checkout process. The following changes ensure the Events’ webapp correctly passes newly required values to the Spreedly gateway when Event registrations occur via an iframe.
Updated Spreedly Configuration
Complete the following steps to enable the new authentication method.
Navigate to Environment Settings in the Spreedly dashboard.
Enable the checkbox "Enable Secure Tokenization."
Select the option "iFrame or Spreedly Express."
Blackthorn Configuration
Confirm that the following fields are on the Payment Gateway page layout you use for your Spreedly gateway.
Spreedly Environment Key
Spreedly Configured Gateway
Spreedly Certificate Token
Spreedly Private Key
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.