Please review the updates below and follow the upgrade instructions to upgrade your Events application.
Table of Contents
Breaking Changes
June 4, 2025
The May 2025 webapp release has been reverted to the April 2025 webapp release.
This is due to the following issues:
Tabbed or Simple UI registrations were processed successfully on the backend, even though the checkout process failed on the frontend without creating a Blackthorn Log entry.
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.
We are working to discover the issue and fix the problem. This is our top priority, and we are moving on it as quickly as possible. Thank you for your patience.
March 5, 2025
As of the March 5, 2025 Salesforce release, Caching 2.0 will be installed with the upgrade. Please follow the steps below to complete the process.
Install the Events app upgrade using the Candy Shop. (If you believe you need to use a direct link, please contact Blackthorn Support. They can provide you with the script and instructions for performing the process manually.)
Contact Blackthorn Support to request that the Caching 2.0 installation process be completed. Please include the Org ID for the environment where you want Caching 2.0 enabled.
Event Group Filters Update: If Caching 2.0 is enabled and Event Group URLs have keywords/filters, both the legacy (pre-Caching 2.0) format ((?keywords=CategoryName:KeywordName) and the new format (?keywords=KeywordName) work as expected. This change ensures that Event Group URLs with keywords shared with potential Attendees before upgrading to Caching 2.0 work as expected. Previously, legacy Event Group URL keywords included both the keyword category and keyword in the URL filters, but using them with Caching 2.0 caused empty Event Groups.
Off-Cycle Releases
May 7, 2025
The April 2025 update to the Stripe checkout logic was reversed so additional work can be completed. The original fix caused issues for those Payment Methods that don’t follow the “authorize first and charge later” process and prevented payments from being accepted. Until then, if a user closes their browser while a payment is processing, the payment will be charged, skipping the authorization step, and the ERS process will fail.
March 25, 2025
If a Form Element contains a picklist value with a colon ( : ), Attendees will see the entire picklist value when selecting an answer. Previously, Attendees only saw the text after the colon. Ex. “Colors: Yellow and Blue” vs. “Yellow and Blue” (Known Issue: 000004540)
BT Salesforce Release
(Release Date: April 22, 2025)
Bug Fixes
Form Elements: When an Attendee enters an answer for a Form Element with Type = “Text,” the answer can only be 255 characters or less. Previously, Attendees could enter more than 255 characters, causing errors when the Form answers were mapped to an object/field. (Known Issue: 000003765)
Mapping: Form mapping will occur as expected if a customer’s org uses the same field names as Blackthorn’s packaged objects' field names. Previously, Forms were not mapped, and users did not see an error message, causing confusion. (Known Issue: 000004420)
Attendee Registration Component: When searching for a Contact/Lead/Person Account in an Event’s Attendee Registration Component, the user will see the person’s name and email address. Previously, only the person’s name appeared in the search results. (Known Issue: 000004224)
Waitlists: If a waitlist is enabled at the Event level and either the Event Organizer increases the Event’s Total Capacity or a registered Attendee cancels their registration, the first Attendee on the waitlist will have their Registration Status updated from “Waitlist – Pending” to “Pending.” Previously, the waitlisted Attendee’s Registration Status remained the same even though space was available. (Known Issue: 000004547)
Advanced Visibility: Advanced Visibility will work if an org has only Customer Community licenses, only Partner Community licenses, or both. Previously, both license types were required to use Advanced Visibility. (Known Issue: 000004457)
Email Template Builder: Event Organizers can edit existing Email Templates in the Email Template Builder. Previously, loading an Email Template displayed a blank screen. (Known Issue: 000004652) For those who can’t get the Salesforce package update, we recommend using one of the following workarounds.
Use a classic Email Template or a Firefox browser.
For Chrome users, clear the cache and hard refresh the page if the Email Template Builder loads with a blank screen.
Campaign to Event Sync
If an Event has matching rules set to block duplicate Attendees from being created and a Campaign has Event Auto Sync set to sync Campaign Members with existing Attendees, the Campaign to Event sync process will occur as expected. Previously, Campaign Members failed to sync with existing Attendees, and a “DUPLICATES_DETECTED, Duplicate Attendee records were found” Blackthorn Log was created. (Known Issue: 000004421)
When Campaign Members are added to multiple Campaigns within a 30-minute auto-sync window, all Campaigns with newly added Campaign Members will have Attendees created as expected. Previously, the batch job only processed the first Campaign/Event pair, causing all other Event/Campaign combinations not to have new Attendees created. (Known Issue: 000003080)
Event Builder
Event Organizers can edit an existing Event in the Event Builder whether the Lightning Web Security (LWS) is enabled or disabled. Previously, the Event Builder became unresponsive because a “Cannot read properties of undefined (reading ‘inlineHelpText’)” error occurred.
If an Event Organizer uses the Event Builder to publish an Event without an Event Item and the Event Setting’s Require At Least One Ticket To Publish field is set to “Yes,” the Event will not be published. Previously, the Event was published even though an Event Item was required.
Permission Sets
The Blackthorn | Events (Community Guest User) permission set was updated to include Read permissions for the following objects and related fields. (Known Issue: 000004457)
Fee (bt_stripe__Fee__c)
BT Rule (bt_base__Rule__c)
Schedule (bt_base__SCH_Schedule__c)
The Fee’s Type field was removed from the Blackthorn Events | Limited Access and Blackthorn Events | Lite User permission sets to prevent errors when upgrading the Events and Payments packages. Previously, installing Events version 4.42+ with Payments 6.20+ caused errors.
Enhancements
Matching: An Attendee’s Last Name will be included in matching logic only if the Event Item’s Full Name field is set to “Required.” This will allow use cases where matching logic identifies matches based on other available fields, such as matching only by email address. Previously, when an Event Item did not require a last name (Event Item Full Name = “Hide”), matching logic failed because the logic tried to include a last name in the matching conditions.
Authorize Events: If an Events user’s profile does not include the Salesforce Administrator profile, the user will see the following message on the Blackthorn | Events Admin tab instead of the Authorize the App button. “Admin Profile Required - You need to have the System Admin Profile to authorize the application.” Only users with the System Administrator profile can authorize the app.
Event Settings: The new Event Settings' Countries To Include field allows users to overwrite the Countries To Exclude multi-select picklist, which allows up to 100 options. Attendees will see only the countries included in the Countries To Include field as available options in the Attendee Info Form’s Country picklist.
Object: Event Settings
Field Label: Countries To Include
API Name: conference360__Countries_To_Include__c
Data Type: Long text
Help Text: Add country values from the Countries to Exclude picklist here, separated by commas. If there are any values in this text field, the 'Countries To Exclude' field is ignored, and only countries showing in this text box will be shown as available picklist values.
Sessions: When a Session’s Quantity Available field is blank, the Session will no longer appear as “Sold out” on the Event webpage. Previously, Event Organizers had to add a value to the Quantity Available field so the Session didn’t appear as “Sold out” to potential Attendees.
Zoom: If an Event Organizer sets the Webinar Account’s new Disable Zoom PMI field to “True” (checked), after enabling their Zoom account’s Personal Meeting ID (PMI), registered Attendees will be synced from Events to Zoom for meetings with unique Meeting IDs. Previously, when the PMI was enabled on the Zoom dashboard and registrations were required in Blackthorn Events, registered Attendees were not synced to the Zoom dashboard.
Object: Webinar Account
Field Label: Disable Zoom PMI
API Name: conference360__Disable_Zoom_PMI__c
Data Type: Checkbox
Help text: When the "Enable Personal Meeting ID" setting is turned on in your Zoom account, enabling this option ensures that each meeting generates a unique Meeting ID instead of using the Personal Meeting ID.
Event Builder
Event Organizers can change the maximum height and width of the Event Description (Event.Description) field when working in the Event Builder.
If an Event Organizer uses custom CSS on the Event, Event Settings, or Event Group record and edits the Event in the Event Builder, they will see the following message at the top of the Event Builder. “Custom CSS is applied to this event but is not fully reflected in the Builder's inline preview. For accurate styling, review the preview or live event page.”
The default Event Builder fields and the fields available in the related Field Sets were updated to add the missing help text.
The Event Item screen in the Event Builder was updated, so the note at the bottom appears as follows.
User with the Blackthorn | Events (Admin) permission set: “To customize the fields on this screen, click here.”
User without the Blackthorn | Events (Admin) permission set: “Contact your admin to change the available fields on this page. Admins will have the Blackthorn | Events (Admin) permission set assigned.”
The Emails tab in the Event Builder now matches the UX style used on the other Event Builder pages (padding, style for help text, and title).
Webapp Release
(Release Date: April 22, 2025)
Bug Fixes
Event Settings: If an Event Organizer changes the Event Settings’ Font and goes to the related Event Group’s Event Group URL, they will see the updated font on the initial page load. Previously, the Event Organizer had to refresh the Event Group URL page to see the updated font.
Time Zones: If an Event’s Time Zone is set to “Asia/Jakarta,” the time zone abbreviation will be displayed as “WIB” on the Event webpage. Previously, the abbreviation was incorrectly displayed as “WIT.” (Known Issue: 000003528)
Express Registration: When an Express Registration user registers another individual for an Event and includes a Product or Donation in their cart, the registration will process as expected, and the Product/Donation will be added to the Transaction/Invoice records. Previously, the Product/Donation did not appear on the Transaction/Invoice records. (Known Issue: 000004485)
Checkout: If an Event’s UI Experience is set to “Full-Width” and the Event has a free Event Item with a related free Session, Attendees will see the available Session during checkout. Previously, Attendees were directed to a checkout experience that hid the available Session.
Forms: When an Attendee registers for an Event that includes a Form Element with Type = “Date” and a related Form Element Condition with the Condition Operator = “Equals” and Condition Value = “a full date with a day, month, and year,” the Attendee will see the Form display the following Form Element when the date matches the condition logic when they are registering for the Event. Previously, the Form did not display the next Form Element when a date matched the condition logic.
Fees: If an Event with Sessions has an attached Fee with Type = “Tax” and Tax Display Setting = “Tax-Inclusive Pricing,” Attendees will see the Session prices displayed as the “Event Item Session Price + tax” in the Add for $ button and in the checkout summary. Previously, some Session prices were incorrectly displayed as “non-tax-inclusive” prices.
Enhancements
Data Dictionary: The Data Dictionary includes the new Key “LBL_MAIN_EVENT_TICKET,” which was created for the Description of Event Items with Type = “Main event ticket.” The text for this Key is located under the Event Item's Public Item Name on the Ticket selection page and works similarly to the “LBL_DONATION” and “LBL_PRODUCT” Data Dictionary keys.
Checkout
If the Event Settings’ Countries To Exclude and Countries To Include fields both contain values, Attendees will only see the values in the Countries To Include field in the Attendee Info Form’s Country picklist.
Attendees who register for a free Event or select the “Pay Later” option will see the new “Registration processing…” message. Attendees who submit a payment will see the “Payment processing…” message. Previously, everyone saw the “Payment processing…” message, regardless of whether a payment was being processed.
Dynamic UI
Extra padding was removed from above the checkout stepper/progress component on the Dynamic UI.
If an Event has the UI Experience set to “Dynamic” and the related Event Settings record has Attendees set to “Always,” Attendees will see the Attendee tab on the Event Page URL.
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.
Required/Mandatory Sessions: If an Event Item has a related Session and the new Event Item Session’s Required field is set to “True” (checked), Attendees must add the Session to the cart if they add the related Event Item.
Object: Event Item Session
Field Label: Required
API Name: conference360__Required__c
Data Type: Checkbox
Default: False (unchecked)
Description: Specifies whether this Session is mandatory for the associated Event Item.
Help text: If checked, this Session will always be required by the ticket type. This is unchecked by default.
Event Builder: When creating an Event in the Event Builder, Event Organizers can use the Form field to add a Form (questionnaire) to a Session.
Field/Layout Updates
New
Object: Event Item Session
Field Label: Required
API Name: conference360__Required__c
Data Type: Checkbox
Description: Specifies whether this Session is mandatory for the associated Event Item.
Help text: If checked, this Session will always be required by the ticket type. This is unchecked by default.
Object: Event Settings
Field Label: Countries To Include
API Name: conference360__Countries_To_Include__c
Data Type: Long text
Help Text: Add country values from the Countries to Exclude picklist here, separated by commas. If there are any values in this text field, the 'Countries To Exclude' field is ignored, and only countries showing in this text box will be shown as available picklist values.
Object: Webinar Account
Field Label: Disable Zoom PMI
API Name: conference360__Disable_Zoom_PMI__c
Data Type: Checkbox
Help text: When the "Enable Personal Meeting ID" setting is turned on in your Zoom account, enabling this option ensures that each meeting generates a unique Meeting ID instead of using the Personal Meeting ID.
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.