Please review the updates below and follow the upgrade instructions to upgrade your Events application.
Table of Contents
Breaking Changes
Salesforce Connected App Changes
Salesforce recently announced a change to its security policy around Connected Apps, effective August 28th. As a result, Blackthorn recommends verifying that these Connected Apps are installed in your Salesforce orgs.
Blackthorn | Connected App - required to use Blackthorn Events and Blackthorn Payments
Mobile Check-in App - required for using Blackthorn Mobile Check-in
Blackthorn | Mobile Connected App - required for using Blackthorn Mobile Payments
Blackthorn Message - required for using Blackthorn Messaging
Please review the attached pdf for instructions to check that the required Connected Apps are installed and connected correctly.
August 26, 2025 - Webapp Release Rollback
The August 2025 Webapp Release has been reverted to a previous version. 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.
Email Template Builder Warning
To continue using the Email Template Builder, upgrade Events to Version 5.16. Users who do not update Events to this version or above will lose access to the Email Template Builder.
The Email Template Builder uses the BeeFree SDK. This update includes changing the builder’s authentication logic as BeeFree deprecated the previous authentication mechanism. For more information, please click here.
BT Salesforce Release
(Release Date: 8/26/2025)
Bug Fixes
Split Payments: The following will occur when an Event has Split Payments enabled and an Authorize.net Payment Gateway. If a user registers for a free Ticket, Session, or Product and adds a Donation for an amount greater than zero, then the Donation will use the Donation Payment Gateway, and a Transaction will not be created or sent to the Payment Gateway. Previously, a Transaction for the free Ticket, Session, or Product was sent to the Payment Gateway, causing an error during checkout. (Known Issue: 000004892)
Event Records: Event Organizers and non-admin users can open an Event record without seeing an error message. Previously, if an org’s language was set to a language other than English or the user couldn’t view Profile records, they saw the following error message: “List has no rows for assignment to SObject.” (Known Issue: 000004926)
Event Builder
If a user edits an FAQ record from the Event Builder and either makes changes and saves the record or clicks Cancel, the value in the Category field will be removed. Previously, the Category field value was not cleared as expected.
The Smart Scheduler will now load in the Event Builder as expected.
If an Event Organizer creates and saves the first Translation record for an Event, reopens the record, and clicks Save (with or without making changes), the record will be saved as expected. Previously, a duplicate Translation record was created instead of updating the original one.
Event Financial Summary Fields
The following updates were made to ensure the rollup fields in the Event record’s financial summary are based on the logic of the related Invoice. (Known Issue: 000004741)
The “Blackthorn Pay - Trigger Settings” custom setting now includes the Include refunds in rollup calculations (Include_Refunds_in_Rollup_Calculations__c) field, which is unchecked (disabled) by default.
If an Event Organizer checks the Include refunds in rollup calculations field and processes a full refund, the refunded Transactions will be reflected on the Invoice (bt_stripe__Sales_Document__c) record, and the Event’s Balance Paid field will be updated to “Transaction Paid - Refund."
For partial refunds, the refunded Transactions are reflected on the Invoice record, the related Event’s Balance Paid field is updated to "Transaction Paid - Refund," and the Gross, Net, and Total fields are updated.
Previously, when an Attendee registered for an Event and received a full or partial refund, the Event’s Balance Paid, Gross, Net, and Total fields were not updated.
The help text for the following Event object fields was updated to reflect that partial refunds are included in calculations.
Balance Paid
Gross
Net
Total
Click here for more information and examples for the updated rollup fields.
Waitlisting
If an Event has waitlisting set at the Event level, Attendees with Registration Status set to “Waitlisted - Pending” can register for the Event from their AttendeeLink when their Registration Status is changed to “Pending.” Previously, Attendees whose Registration Status changed from “Waitlisted – Pending” to “Pending” could not register from their AttendeeLink. (Known Issue: 000004688)
If an Event has an automatic waitlist and no Tickets are currently available, then the next Attendee in line will be unable to register if another waitlisted Attendee cancels their waitlisted Ticket. Previously, when a waitlisted Attendee removed themselves from the waitlist, the waitlist incorrectly made a Ticket available to the next person in line, even though there was no capacity. (Known Issue: 000004769)
Enhancement
AttendeeLink: Add to Apple Wallet
Event Organizers can 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
To add a QR code to their Apple Wallet, registered Attendees with iOS devices must open their AttendeeLink and click the Add to Apple Wallet button. They can now check in quickly at an Event without needing to search for their AttendeeLink in their email. The Apple Wallet ticket will show the {{variable.Field_ETEvent_EventName}} and the QR code from the AttendeeLink.
Important Functionality:
The Add to Apple Wallet button is enabled by default.
At this time, Android and desktop users cannot see the button.
Click here for more information about the Add to Apple Wallet feature.
Forms for Sessions
The Forms for Sessions feature allows Event Organizers to tie questions, or a Form, to a single Session. This is especially helpful if you require specific information from session attendees, such as selecting an entree for a dinner. Click here for more information about Forms for Sessions.
Webapp Release
(Release Date: 8/26/2025)
Bug Fixes
Custom CSS: Custom CSS logic was updated to flow from the Event Group level down to the Event level, reducing the number of required files. For example, if the Event Settings Custom CSS Url field is blank but the primary Event Group record’s Custom CSS Url field contains a CSS file that includes Event-specific styling, then the Event Organizer will see the changes at the Event level. Previously, adding Event-level code to the Event Group level CSS file had no impact on the Event’s appearance. Only adding a CSS file to the Event Settings record impacted the Event. (Known Issue: 000004688)
Caching 2.0: If an org has Caching 2.0 enabled and an Attendee’s Registration Status changes from “Waitlisted” to “Waitlist-Pending,” they can immediately register for the available Ticket. Previously, the Ticket was marked as “Sold Out,” and the Attendee could not register until the cache updated. (Known Issue: 000004688)
Express Registration: If an Event has Express Registration enabled and a user selects a Contact with a contactId from the picklist and adds them on the Contact Information screen during checkout, then that Contact’s contactId is included in the “contactBillto” section of the ERS payload. All payment records, such as Invoice and Payment Gateway Customer, will be linked to the relevant Contact. Previously, the contactId was not included in the “contactBillto” section of the ERS payload, preventing the Contact from being associated with the related Invoice.
Iframes: When an Attendee registers for an Event with either Donations, Sessions, or both via an iframe, the Attendee can select Sessions and/or Donations and complete the checkout process. Previously, the Attendee was shown a blank screen after selecting the Session or Donation and could not complete checkout. (Known Issue: 000004925)
Translations: If an Event Organizer adds an apostrophe to an Event’s name, description, Session(s), Speaker(s), etc., and an Attendee translates the Event webpage into another language, the apostrophe will appear as expected. Previously, the apostrophe appeared as “'”. (Known Issue: 000004626)
Enhancements
Checkout Process: When a promo Code is required to register for an Event and an Attendee uses portrait view on a mobile device to check out, the cart summary automatically expands so the Attendee can see the promo Code field. Previously, users had to manually expand the Cart/Order Summary to see the promo Code field, but often missed the field, causing checkout errors.
Accessibility
When an Attendee uses a screen reader to complete a survey Form with a required checkbox, the screen reader will not announce the asterisk if it has already communicated the field’s required status. Previously, the screen reader also read the asterisk as “star.”
When an Attendee uses a screen reader to move through the different Ticket types on the Ticket selection page of an Event with the Tabbed UI, the screen reader will announce the names of the Donation and/or Product Tickets as well as the Ticket selector.
During checkout, if an Attendee using a screen reader enters an incorrect promo Code for an Event with the Tabbed UI, the screen reader will announce the error message. Previously, the screen reader did not announce the error message, leaving the Attendee unaware of the error.
An Attendee using a screen reader on an Event with the Dynamic UI will correctly hear "Count + [Ticket Type] Name + Selected" when they hover over a Ticket on the Ticket selection page. The screen reader will also correctly announce Tickets in the following scenarios:
An Attendee loads the Ticket section page for the first time.
An Attendee moves through selected Tickets after they have added the Tickets to the cart.
The following will occur when an Attendee uses a screen reader to move through different elements of a date-type question on a Form.
When the user navigates to a date-type question using the TAB key, the screen reader announces the question text first. The date picker opens automatically, and the screen reader announces the selected date.
If the date-type question includes supplemental information, the screen reader announces the question label and the supplemental information.
When the user opens the date picker, they can navigate between dates using the arrow keys, and the screen reader announces the selected date correctly.
When a user submits a survey Form, the screen reader announces the "Submitting..." message to communicate that the page is being processed. Previously, the screen reader was quiet, which left users unaware of the submission process.
When an Attendee views an Event Group using the Maple UI, the screen reader will announce whether a category is selected or deselected when it is selected or deselected.
A screen reader will announce the "Your Order Is Complete" confirmation message that is displayed after an Attendee completes the checkout process.
Field/Layout Updates
New
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.
Mobile Check-in App
Bug Fixes
Users will see all of the Events in the relevant list when viewing a list of upcoming Events, past Events, or Events with “no date” in the Mobile Check-in app.
While Blackthorn doesn’t officially support SSO, users can log into the Mobile Check-in app on an iPhone using Microsoft Entra ID single sign-on, and the app will be redirected as expected. Previously, the Mobile Check-in app intercepted redirects, preventing the app from going to the correct screen following login.
The following updates were made to the Mobile Check-in app to improve the user experience.
Updated the logic to handle data changes more efficiently, resulting in faster load times for Salesforce orgs with a high number of Events.
Corrected freezing issues when switching between screens.
Improved the performance when scrolling large Attendee lists.
The Events list (including upcoming, past, and no date Events) in the Mobile Check-in app will load with a limit of 4000 Attendees. Previously, the Events list did not load as expected due to a payload discrepancy.
The CSS in the Mobile Check-in app was updated to prevent a horizontal scroll bar from appearing when viewing the Events list. Previously, long Event names exceeded the screen width, causing the horizontal scroll bar to appear.
Enhancements
Filtering Attendees
Mobile Check-in app users can filter Attendees using additional criteria to create better optimized results.
Example: A large Event is in progress. The Mobile Check-in user needs to filter the Attendee list by specific criteria quickly and without using too many API calls.
To start, the user can set the “Last Modified Date” to a specific Day/Month/Year so only Attendee records that were modified after that date appear in the results.
The user can then use the qualifiers “and” and/or “or" and select from the Attendee object’s fields to further narrow the results.
Finally, the user can set a value to limit the number of Attendee records in the results. For example, if 5000 is entered, the results will include up to 5000 records. If a value is not specified, the default value of 3000 records will be used.
If all the filter criteria are left blank, the user will see all the Attendee records in the results.
Swift Mode Feature
The Swift Mode feature makes the Event check-in experience faster and more reliable, especially for large Events or when internet connectivity is limited.
Swift Mode saves all check-ins locally on your device. When you're ready to sync, these check-ins are grouped and sent to the server in a single batch. The batching process reduces the number of API calls made to the server, speeding up the check-in process and helping prevent slowdowns and errors when handling thousands of Attendees. Click here for more information about using Swift Mode.
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 impacts extensive functionality.
BT Salesforce Release
The following applies to a Salesforce release.
Salesforce fixes REQUIRES 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.