Please review the updates below and follow the upgrade instructions to upgrade your Events application.
Table of Contents
Breaking Change
June 11, 2025
The May 2025 Events Webapp release functionality has been restored and updated to ensure all users can register for Events in either of the following scenarios.
Users can register for an Event regardless of the Event’s UI Experience. Previously, when the Events app was used with an earlier version with the Tabbed or Simple UI, the checkout process failed on the frontend without creating a Blackthorn Log entry, even though the registration could be processed on the backend.
Users cannot complete the registration process if they leave a required field on the registration form blank. Previously, Tabbed UI registrations succeeded even though required form fields were not filled out, which resulted in a failure at the ERS step since Salesforce could not process the registration.
Off-Cycle Release
June 2, 2025
Attendees can click the Register button to register successfully for an Event. Previously, the checkout process failed on the frontend without creating a Blackthorn Log entry, but the registration could be processed on the backend without an error. (Known Issue: 000004852)
BT Salesforce Release
(Release Date: July 1, 2025)
Bug Fixes
Schedule Jobs: If a user clicks the Schedule Recommended Event Jobs button on the Blackthorn | Events Admin tab’s Schedule Jobs tab, the Blackthorn | Batch Event Registration Submission job is processed as expected, and the related ERS job is listed in the Scheduled Jobs list. Previously, there was an intermittent issue after upgrading the Events app via the Candy Shop, where the ERS job was not scheduled after clicking the Schedule Recommended Event Jobs button. (Known Issue: 000004705)
Visibility Control: When a Contact with Visibility Control set to “Member” registers via an authenticated iframe for an Event Item and Session that also have Visibility Control set to “Member,” Salesforce creates an Attendee record with the same Visibility Control value as the Contact record. The Contact/Attendee can then use their AttendeeLink to view the Sessions they registered for. Previously, the newly created Attendee record was created without a value in the Visibility Control field, preventing the Attendee from seeing the Sessions they registered for in their AttendeeLink. (Known Issue: 000004738)
Opportunities on Checkout: After an Attendee purchases a paid Ticket, the related Transaction record will appear in the Opportunity’s Transaction Related List. Also, the Invoice’s Opportunity lookup field and the Transaction’s Opportunity lookup field are populated with the related Opportunity. Previously, the Invoice’s Opportunity field was blank, and the Opportunity record didn’t include the Transaction in the Opportunity’s Transaction Related List. (Known Issue: 000004744)
Attendee Record: If an Attendee’s Registration Status is updated from “Invited” to "Waitlisted - Pending," the Contact and Account lookup fields will remain populated with the original Contact and Account records. Previously, the Contact and Account lookup fields were cleared when the Attendee’s Registration Status was updated to Waitlisted – Pending." (Known Issue: 000004787)
Campaign Sync: If an Attendee registers for an Event and the related Campaign Member’s Status is changed to a custom value (ex., from "Registered" to "Registration Review"), the Campaign Sync feature will sync the Attendee record, and the Attendee’s Registration Status will remain unchanged. Previously, when a Campaign had Campaign Members with custom Status picklist values, the related Attendees’ Registration Status field changed to “To Invite” after changing the related Campaign Member’s Status. (Known Issue: 000004618)
Fees: Event Items will be excluded from tax calculations during checkout if an Event Item has Type = “Other,” Tax-Exempt= “True,” and a Fee with Type = “Tax” and Tax Display Setting = “Calculated at Checkout.” Also, the resulting Invoice’s Line Item will have Tax set to “0” for the “Other” Event Item. Previously, the tax was applied to Event Items with Type = “Other” and Tax-Exempt = “True,” and included on the related Invoice and Line Item. (000004698)
Codes: Discount and access-promo Codes work with Products (Event Item Type = “Other”). Previously, neither type of Code worked with Products.
Event Builder
When an Event Organizer deletes an existing banner (Image URL) or thumbnail image (Thumbnail and Mobile Image URL) from the Event Builder and saves the Event, the Event will save as expected. Previously, when the Event Organizer tried to save the Event, they received an error because the information in the corresponding Thumbnail Image Name and Image Name fields was not automatically deleted. The error will only occur if a user adds a new image and doesn’t add the corresponding alternative text.
Event Admins can change the visibility of the FAQ and Event Content tabs in the Event Builder from the Custom Metadata Types “Event Builder Configuration” section in Salesforce. Previously, Event Admins could not make the FAQ and Event Content tabs visible, which created issues for Event Organizers.
Forms
Users can edit existing Forms with Form Elements using the new Form UI. Previously, clicking the Edit button on an existing Form Element caused a pop-up with the following error. "Error notification: Failed to load object fields. You don't have access to this record. Ask your administrator for help or to request access." (Known Issue: 000004697)
When a user creates a Form Element with Type set to “Parameter,” they will see and be able to set both the Maps To (Object) and Maps To (Field) fields. Previously, users creating a new Form with Form Element Type = “Parameter” in the new Form UI could not see the Maps To (Field) field on the page layout. (Known Issue: 000004740)
Enhancements
Event Settings: The Event Settings’ new Disable Auto-Add to Default Event Group field allows Event Organizers to determine whether an Event should automatically be added to the Event Group marked as the default Event Group.
If Disable Auto-Add to Default Event Group is unchecked, the new Event will be added automatically to the default Event Group.
If Disable Auto-Add to Default Event Group is checked (enabled), the new Event will not be automatically added to the default Event Group.
Object: Event Settings
Field Label: Disable Auto-Add to Default Event Group
API Name: conference360__Disable_Auto_Add_to_Default_Event_Group__c
Data Type: Checkbox
Default Value: Unchecked
Help Text/Description: When enabled, events are not automatically added to the Default Event Group.
Attendee Record: The Attendee record’s Personal Attendee Mobile App Link (Personal_Attendee_Mobile_App_Link__c) field was deprecated and replaced by the Personal Navigator App Link field.
Object: Attendee
Field Label: Personal Navigator App Link
API Name: conference360__Personal_Navigator_App_Link__c
Data Type: Formula URL - e.g. https://app.navigator.blackthorn.io/?orgId={orgId}&email={attendeeEmail}
Description: This personal invitation link is generated for each registered attendee when the Navigator app is enabled for the event. Email is used as a unique identifier.
Help Text: This personal invitation link is generated for each registered attendee when the Navigator app is enabled for the event.
Event Builder
If an Event Organizer enters a search term in a lookup in the Event Builder but does not select a corresponding record, they will see an error message reminding them to choose an option or remove the search term. They will also be unable to save the record. (Global save buttons such as Save and Publish Later and Save and Publish Now still work as expected.)
The Event Builder now includes a Translation option in the navigation on the left side. Event Organizers can navigate to the “Translations” tab and add/create/clone Translation records related to Events, Event items, Speakers, Sessions, Sponsors, and more from within the Builder. Any Translation record created in Event Builder will be visible on the corresponding object’s record.
Flows
The “Blackthorn | Events ERS Failed” workflow rule was deprecated and replaced with the “Blackthorn | Events ERS Failed” (Blackthorn_Events_ERS_Failed) flow. The new flow is set to active by default. When you upgrade Events to Version x.x, the deprecated workflow rule will be active (unless you have previously deactivated it), AND the new flow will also be active. This occurs because Blackthorn cannot update the state/status of an existing workflow rule on a customer’s org. Your Admin must deactivate the workflow rule; otherwise, Salesforce will send two emails to the Admin with information about the ERS error.
The following workflow rules were converted to flows:
Send Blackthorn | Event confirmation email (Send_Blackthorn_Event_confirmation_email)
Send Blackthorn | Event invite email (Send_Blackthorn_Event_invite_email)
Send Blackthorn | Event Reminder email (Send_Blackthorn_Event_Reminder_email)
Send Cancelled Registration Email (Send_Cancelled_Registration_Email)
Send the Waitlisted Email (Send_the_Waitlisted_Email)
Send the removed from the Waitlist Email (Send_the_removed_from_the_Waitlist_Email)
Required Sessions Feature
Required Prerequisites
Event Organizers must manually confirm that the configuration of the Event Item and Session capacities includes the required Sessions. Salesforce will not automatically validate those numbers. If a Session is required but is sold out, the associated Event Item will be marked as sold out on the Event’s website.
To use the Required Sessions feature, your org must be set to Events versions 5.4 and higher.
Event Organizers can make Sessions mandatory on an Event Item so that Attendees are more likely to attend essential Sessions. Mandatory Sessions are pre-selected, and Attendees cannot unselect them or register for the Event without them.
If an Attendee selects an Event Item with a mandatory Session (Event Item Session Required (conference360__Required__c) = “True” (checked)), the Session will be added automatically to the cart with the related Event Item.
The Attendee will see the “Added” text in the selector button. They cannot remove the non-elective Session from their cart. However, if they remove the Event Item from the cart, the Session will also be removed.
If a Session is required (Event Item Session Required = “True” (checked)) and the Session is sold out, the associated Event Item will also be marked as sold out.
Click here for more information about how to use the Required Sessions feature.
Webapp Release
(Release Date: July 1, 2025)
Bug Fixes
Codes: If a free Event has a Code marked as required, Attendees can successfully register for the Event. Previously, the registration failed, and the Attendee received a “Warning: Please apply a valid code to continue” error. A BT Log was also created with the following error: “Access Promo Code Required: Full day program. Please provide the right promo code or remove it from your cart to complete registration.” (Known Issue: 000004772)
Event Settings: When an Event Settings record has the Disable Auto-Add to Default Event Groupfield enabled (checked), then Events associated with the Event Settings record but without an assigned primary Event Group will not be added automatically to the Event Group with the Default' field set to “True” (checked). This change allows Event Organizers to have standalone Events that aren’t assigned to an Event Group, while still using the default Event Group for non-standalone Events. Previously, once Caching 2.0 was enabled, Events without an Event Group were automatically associated with the default Event Group, causing the Event Group’s Event Settings to override the Event’s own Event Settings and change how the Event’s webpage appears. (Known Issue: 000004666)
AttendeeLink: The Add to Calendar button on an Attendee’s AttendeeLink appears as expected for multi-day Events when the present date is during the Event. Previously, the Add to Calendar button on the AttendeeLink was missing if the Event was already in progress. (Known Issue: 000002719)
Accessibility: Screen readers navigating the Events app will only announce an element as clickable if it is interactive (e.g., buttons, links, or elements with a click event). Previously, the screen reader incorrectly announced that non-clickable parts of Sessions and Product Names (Session Name, session thumbnail (Image URL), product name (Public Item Name), and product thumbnail (Image URL) were clickable.
Anonymous Checkout: If an Event has the Attendee Form fields hidden on the Event Item, Attendees can register anonymously. Previously, the Register button was disabled, and the fields were marked as required on the Attendee Form, preventing Attendees from registering.
Checkout Process
An Attendee can successfully register for an Event via their AttendeeLink when the Event has an Event Item using the Maximum Quantity feature, and the Attendee object uses custom statuses for the Registration Status field. Previously, Attendees could see the Sessions but could not add them to their cart unless they refreshed the page. (Known Issue: 000004596)
If the Event Settings One Unique Attendee Email Per Event field is enabled (checked) and a duplicate email is entered during checkout, an error message will be displayed. Previously, the error message wasn’t displayed, but the Register button was disabled and grayed out, even after a unique email was entered.
If the waitlist is enabled at the Event level and the capacity is set on the Event Item, Attendees can join the waitlist using the ticket quantity selector when the Event Item reaches full capacity. Previously, the ticket quantity selector was disabled, preventing Attendees from joining the waitlist. (Known Issue: 000004748)
Translations
If an Attendee selects a language other than English with the language selector on an Event Group webpage, the Event Group’s categories and keywords will be translated correctly. Previously, after Caching 2.0 was enabled, the following occurred.
An Event Group’s categories were not translated, even if a related Translation record for the Event Group categories or Google translations was used. (Known Issue: 000004685)
An Event Group’s keywords were not translated, even if a related Translation record for the Event Group keyword was used. (Known Issue: 000004645)
Enhancements
Google Analytics: Event Organizers who use Google Analytics for tracking can now use a third-party platform to collect cookie consent instead of using the Blackthorn cookie consent banner. If you are using a 3rd party tool, you can set Blackthorn to automatically start tracking without a consent banner. However, if you turn off Blackthorn’s cookie consent banner, we expect you will use a third-party tool. We do not endorse skipping the consent banner. Please contact Blackthorn Support to deactivate and hide the Blackthorn consent banner.
Accessibility
Event images on an Event’s webpage with the Simple UI now include alt-text attributes. When an Attendee views an Event webpage with a screen reader, they will hear the Alternative Text for Visual Impairment text for the Event’s image (Image URL). Previously, the screen reader skipped over the image entirely, making it inaccessible to visually impaired users.
If an Attendee uses a screen reader to navigate an Event’s webpage, the screen reader will read the Register button, whether active or disabled. When the button is disabled, the reader will announce it and explain that completing the CAPTCHA is required to enable it.
When an Attendee uses a screen reader to register multiple Attendees for an Event with the Dynamic UI, the screen reader will announce the field labels and input instructions for the other Attendees’ form fields (First Name, Last Name, and Email). Previously, the screen reader only read the fields for the first Attendee.
When an Attendee uses a screen reader to navigate an Event webpage in the Dynamic UI, the screen reader correctly announces the Add Ticket Quantity button.
The screen reader will read “Add Ticket Quantity” plus the ticket type. For example, “Add Ticket Quantity, Main Ticket” or “Add Ticket Quantity, Guest Ticket”
After the Attendee clicks the Add Ticket Quantity button and selects one or more tickets, the screen reader will announce the updated number of tickets selected. For example, “1 Main Ticket selected” or “2 Guest Tickets selected”
Field/Layout Updates
New
Object: Event Settings
Field Label: Disable Auto-Add to Default Event Group
API Name: conference360__Disable_Auto_Add_to_Default_Event_Group__c
Data Type: Checkbox
Help Text/Description: When enabled, events are not automatically added to the Default Event Group.
Object: Attendee
Field Label: Personal Navigator App Link
API Name: conference360__Personal_Navigator_App_Link__c
Data Type: Formula URL - e.g. https://app.navigator.blackthorn.io/?orgId={orgId}&email={attendeeEmail}
Description: This personal invitation link is generated for each registered attendee when the Navigator app is enabled for the event. Email is used as a unique identifier.
Help Text: This personal invitation link is generated for each registered attendee when the Navigator app is enabled for the event.
Old
Object: Attendee
Field Label: Personal Attendee Mobile App Link
API Name: conference360__Personal_Attendee_Mobile_App_Link__c
Data Type: URL
Description: Note that this link relies on email as a unique identifier.
Help Text: This personal invitation link is generated for each registered attendee when the attendee mobile app is enabled for the 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.