Please review the updates below and follow the upgrade instructions to upgrade your Events application.
Table of Contents
Breaking Changes
Event Settings/Mobile Check-in App
Previously, Event Staff could always accept walk-up registrations at an Event. Now, the Event Settings Allow Walk Up Registrations field allows Event Organizers to determine if Event Staff can accept walk-up registrations on the Mobile Check-in app.
If Allow Walk Up Registrations is “unchecked” (default setting), then Event Staff can only check in pre-registered Attendees.
If Allow Walk Up Registrations is “checked,” then Event Staff can accept walk-up registrations on the Mobile Check-in app.
Object: Event Settings
Field Label: Allow Walk Up Registrations - Note: This field is available in the standard Mobile Check-in app. It will be available for Kiosk Mode in the future.
API Name: conference360__Allow_Walk_Up_Registrations__c
Data Type: Checkbox
Default: unchecked
Description/Help Text: Accept walk-up registrations through the mobile check-in app (standard or Kiosk Mode). Uncheck to only allow pre-registered attendees to check in.
Exception: If Salesforce is using an older version (prior to 5.32), the Mobile Check-in app will default to allowing walk-up registrations.
Note: This feature will be available in Kiosk Mode when the Kiosk Mode feature is available in the Mobile Check-in app.
Off-Cycle Release
March 18, 2026
The following off-cycle release is part of the updated February Payments release.
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."
February 27, 2026
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.”
BT Salesforce Release
(Release Date: February 18, 2026)
Bug Fixes
GoToWebinar: The Blackthorn | Event Webinar Account Refresh (WebinarAccountAuthRefresh) scheduled job now refreshes tokens expiring within the next 14 days, keeping them valid before they expire. Refresh errors are now logged as Blackthorn Logs for visibility. Previously, the job only checked tokens expiring on the current day, so already-expired tokens were never refreshed — causing an "invalid_request" error when adding Attendees to webinars and requiring manual reauthorization. (Known Issue:000005143)
Apex Jobs: Several Apex classes were updated to a current Salesforce API version to resolve compatibility errors in orgs using newer standard fields. Previously, users experienced errors such as "Missing dependent object: Field: Contact.Pronouns." (Known Issue: 000005107)
Seats: If an Attendee has registered for multiple Sessions and therefore has multiple Session Attendee records, an Event Organizer can assign the Attendee a Seat for each Session. Previously, when the Event Organizer tried to assign Seats for more than one Session to a single Attendee, they got the following error: “This attendee already has a seat assigned (Table: N/A, Seat Number: X). An attendee can have only one seat.” (Known Issue: 000005068)
Fees: When registering for an Event with a waitlisted main ticket and adding Donations or Products to your cart, tax and processing fees are now calculated correctly. Previously, tax was not applied to taxable Products and processing fees were skipped for both Donations and Products when the main ticket was waitlisted.
Person Accounts: When registering additional attendees through Experience sites in PersonAccount-enabled organizations, the newly created PersonAccount and Attendee records will no longer inherit address field values from the logged-in user when address fields are not collected during the registration process. Address fields will now only be populated when address data is specifically collected during checkout. This fix ensures accurate data integrity for attendee registration scenarios where users register accompanying persons through Experience sites. When address fields are not visible or required during the registration form, the system will leave address fields blank on new PersonAccount and Attendee records instead of copying the primary registrant's address information.
Donations and Waitlisted Tickets
When an Attendee registers for a waitlisted “Main event item” Event Item/Ticket and a Product or Donation Event Item, the registration and payment are processed successfully. The related Line Items, Invoice, and Transaction records for the Product/Donation are created, and the Attendee record’s Donated and/or Purchased Products fields are updated accordingly. Previously, the following occurred:
No related Line Item, Invoice, and Transaction records were created.
Since the Transaction record wasn’t created, the Product/Donation’s Quantity Remaining field was not updated.
Finally, the Attendee record’s Donated and/or Purchased Products fields were not updated.
Updated the Fees calculation logic to ensure taxes and payment processing fees are calculated only on billable Event Items during checkout. Waitlisted Event Items are excluded from Fee calculations when a billable Product (Event Item Type = “Other”) is included. The taxes and/or payment processing fees for a waitlisted Event Item will be calculated when/if the Event Item becomes available for purchase.
An Event’s Tax Fee field links a Fee record with Type = “Tax” to the Event. When an Attendee adds an available and a waitlisted Ticket to the cart, the tax will only be calculated and applied for the available Ticket. Previously, the tax was also added for the waitlisted Ticket.
An Attendee can add a Donation and a waitlisted Ticket to their cart and successfully register for an Event.
If an Attendee registers for the last non-waitlisted Ticket for an Event that has capacity and waitlisting enabled at the Event level, the following will occur.
The invoice will display Line Items for the purchased Ticket.
The Invoice’s Payment Status will be set to “Paid."
A Transaction record will be created.
Previously, the Line Items on the Invoice were missing, and the Invoice’s Payment Status was incorrectly displayed as "Overpaid" when both capacity limits and waitlist functionality were enabled at the Event level.
Enhancements
The “Webapp” picklist value for the Custom Content record’s Display Location field is now called “Event Landing Page.” The change provides better user understanding and consistency across the platform and makes it easier to identify where Custom Content will appear in your Event experience. The Display Location field’s picklist values are now: "Event Landing Page," "Navigator," and "Both."
Webapp Release
(Release Date: February 18, 2026)
Bug Fixes
Required Sessions/Experience Cloud: When logged into the Experience Cloud, a user cannot register for a Ticket if the associated Session is sold out and required (Event Item Session Required = “True” (checked). Previously, the Ticket wasn’t labeled as “sold out,” and the user could still register for it even though the Session was sold out. (Known Issue: 000005125)
Event Items: If an Event Item’s Account Postal Code is set to “Required,” but the Address field is set to “Hide” or “Optional,” then a registrant will not be able to complete the registration process. Previously, a registrant could complete the registration process on the front end, but it failed on the back end due to an error in the ERS submission. (Known Issue: 000005072)
Invite-only Events: The Get Tickets button no longer appears in the navigation menu bar for invite-only Events. Invitees access tickets through the invite-only verification flow instead. Previously, the button was visible to anyone before email verification.
Google Tag Manager
The Google Tag Manager (GTM) ID stored at the Event Settings level takes priority over the GTM ID at the Company Info level. If an organization has a value in the Company Info Google Tag Manager Id field, and an Event has a related Event Settings record with a value in the GTM Container ID field, the value in the Event Settings GTM Container ID field is used. Previously, neither GTM ID was used when an Event webpage was loaded.
If the Company Info Google Tag Manager Id field contains the Google Tag Manager ID, then data collection for the Event Group webpage will occur only if the user has granted consent to tracking. If the user doesn’t accept tracking, then the related data will not be gathered.
Sessions
If an Event Item has multiple associated Sessions and only one is still available (Session Status Formula = “Active” or “Upcoming”), then the Event Item will be available. Previously, the Event Item was marked as “Sold Out” when at least one Session was no longer available (Session Status Formula = “Registration ended (Public)”). (Known Issue: 000005150)
When an Event's Hide Register Button is set to "Yes," registered Attendees can now view their Session information via their AttendeeLink. Previously, all Session information disappeared from the AttendeeLink.
Donations and Waitlisted Tickets
When an Event Item’s capacity is met, and the waitlist is enabled at the Event level, an Attendee can check out with only the waitlisted Event Item to their cart and be added to the waitlist. Previously, users saw the following error message and weren’t added to the waitlist. "Some items are sold out and not available for checkout, please try again later."
If an Event has a credit card fee and an Attendee adds a waitlisted “Main event item” Ticket and a Donation to their cart, they will see the calculated credit card fee on their donation amount in the Order Summary. Previously, the credit card fee wasn’t calculated.
If an Event with multiple Event Items has waitlisting enabled at the Event level, then Attendees will be able to register for the waitlisted Tickets. Previously, Attendees saw a “Sold Out” message even though waitlisting capacity was still available at the Event level.
If an Event has a Fee with Type = “Tax,” Tax Display Setting = "Calculated at Checkout," and paid waitlisted and available Event Items, users can remove Event Items from the cart and see the correct tax calculation. Previously, users had to refresh the page to see the correct tax calculation.
If an Event has a Fee with Type = “Tax,” Tax Display Setting = "Tax-Inclusive Pricing," and paid waitlisted and available Event Items are in the cart, then the tax will not be applied to paid waitlisted Tickets during the registration process. Attendees will only see the tax for the available paid Tickets. Previously, users saw tax applied to the paid waitlisted Event Item on the Ticket Selection and Attendee Details pages, even though the tax was not applied on the Payment page.
Enhancement
Require at Least One Session: You can now require attendees to select at least one session when registering for specific Event Items. When you enable the Require At Least One Session field on an Event Item, the webapp displays visual indicators during registration to notify attendees that session selection is mandatory for that ticket type.
The registration process includes validation logic that prevents attendees from completing registration without selecting at least one session for Event Items marked with this requirement. This enhancement allows event organizers to ensure complete registrations for multi-session events where session attendance is required. You can now guarantee that attendees select sessions during registration and provide clear visual guidance about session selection requirements.
To use this feature, enable the Require At Least One Session field on the specific Event Item records where session selection should be mandatory. This applies on a per-ticket basis - different Event Items can have different session requirements. Click here for more information about this feature.
Translations and Post Event Forms: Picklist value translations uploaded for Post Event Forms will now display correctly when the form language is switched. When you use the language selector to change the form language, both the form labels and picklist values will properly display in the selected language. This improvement ensures that multilingual post-event surveys function as expected, allowing you to provide a consistent experience for attendees regardless of their language preference. Previously, while the language selector updated form labels correctly, picklist values continued to display in English instead of the selected language.
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 following new field is part of the upcoming Mobile Check-in Kiosk Mode feature.
Object: Event Settings
Field Label: Mobile Check-in Kiosk Mode Logo
API Name: conference360__Mobile_Check_in_Kiosk_Mode_Logo__c
Data Type: URL
Description: Logo image displayed in the Mobile Check-in application when running in Kiosk Mode on tablets
Help Text: Upload logo for tablet kiosks. Recommended: 256x256px (or proportional rectangular), max 800KB, PNG or JPG format
The following new fields are part of the upcoming Next Gen Capacity Management (NGCM) feature.
Object: Event Settings
Field Label: Cart Timer (Minutes)
API Name: conference360__Cart_Timer_Minutes__c
Type: Number (Integer)
Default Value: 15
Description: Default cart expiration timer in minutes for events using this Event Settings record. This value will be used if no event-level override is specified.
Help Text: "Set the default cart expiration time in minutes. Individual events can override this value."
Object: Event
Field Label: Cart Timer Override (Minutes)
API Name: conference360__Cart_Timer_Minutes__c
Type: Number (Integer)
Default Value: null (empty)
Description: Event-specific cart expiration timer in minutes. If set, this value overrides the Event Settings default. If null/not set, the Event Settings value is used.
Help Text: "Use this value to override the default cart timer from Event Settings. Leave blank to use Event Settings default."
Known Issues
Events Salesforce – Issue with Processing Fees and the Invoice: Although a user has paid the full amount due and the checkout process is complete, the related Invoice shows a Balance Due of the amount in the Fee Amount field, while the Status field is set to “Ready To Bill,” and the Payment Status field is set to “Partially Paid.”
PayLink - Accessibility Issue: Users cannot switch between the Card and Bank (ACH) tabs when navigating with the Space and Enter keys on a keyboard. This will be fixed in the April 2026 PayLink Webapp release.
Mobile Check-in app - Swift Mode Check-in Issue: When the Mobile Check-in app’s Swift Mode Check-in feature is enabled on an Android device, the New Attendee and Scanner icons overlap in Swift Mode Check-in.
Mobile Check-in app - Partner Community Users: A Partner Community User cannot check out a Session Attendee from the Mobile Check-in app. After clicking the Sync button, synchronization does not occur. The Sync button remains yellow, and the Attendee’s status is not updated.
Field/Layout Updates
New
Object: Event
Field Label: Cart Timer Override (Minutes)
API Name: conference360__Cart_Timer_Minutes__c
Type: Number (Integer)
Default Value: null (empty)
Description: Event-specific cart expiration timer in minutes. If set, this value overrides the Event Settings default. If null/not set, the Event Settings value is used.
Help Text: "Use this value to override the default cart timer from Event Settings. Leave blank to use Event Settings default."
Object: Event Settings
Field Label: Allow Walk Up Registrations
API Name: conference360__Allow_Walk_Up_Registrations__c
Data Type: Checkbox
Default: unchecked
Description/Help Text: Accept walk-up registrations through the mobile check-in app (standard or Kiosk Mode). Uncheck to only allow pre-registered attendees to check in.
Field Label: Mobile Check-in Kiosk Mode Logo
API Name: conference360__Mobile_Check_in_Kiosk_Mode_Logo__c
Data Type: URL
Description: Logo image displayed in the Mobile Check-in application when running in Kiosk Mode on tablets
Help Text: Upload logo for tablet kiosks. Recommended: 256x256px (or proportional rectangular), max 800KB, PNG or JPG format
Field Label: Cart Timer (Minutes)
API Name: conference360__Cart_Timer_Minutes__c
Type: Number (Integer)
Default Value: 15
Description: Default cart expiration timer in minutes for events using this Event Settings record. This value will be used if no event-level override is specified.
Help Text: "Set the default cart expiration time in minutes. Individual events can override this value."
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.