November 2026 - Version 6.2

(Release Date: Tuesday, November 10, 2026)

📋 At a glance

This month brings more dependable registration, drag-and-drop ordering for Session Rule groups, formatted venue map pin descriptions, Page Designer updates and a set of checkout fixes. If you use venue map pins, your own permission sets or Block Duplicate Registrations, read Possible breaking changes and Action required before you upgrade.

Update	What it does	For whom	Setup
✅ More dependable registration	Fewer duplicate, stalled and failed registrations	Everyone	📦 Events 6.2
🎟️ Session Rule group order	Drag and drop Session Rule groups, and the sessions in them, into the order registrants see	Organizers	📦 Events 6.2
🗺️ Richer venue map pins	Formatted pin descriptions, a pin size, and the option to hide pin names	Organizers, and attendees on Navigator 1.11	📦 Events 6.2
🎨 Page Designer	Access levels, an organization default theme, font sizes per device, invite-only pages and fixes	Organizers and admins	🌐 Webapp, automatic
🛒 Checkout fixes	No paying twice after returning from a payment page, no skipping ahead, no state required where there are none	Everyone	🌐 Webapp, automatic

Some changes ship in the Events 6.2 Salesforce package and need to be installed by an admin; others ship automatically in our November webapp release and are live for everyone as soon as it goes out. Each item below is tagged so you can tell which is which.

⚠️ Possible breaking changes

Two changes in this release can alter something you have already set up, without anyone editing it and without an error message. None of them affect every customer. Each one opens with the question that tells you whether it is you.

Use Navigator and the Venue Maps feature? Pin descriptions move to a new field, and attendees on older Navigator versions see them blank.

What changes: pin descriptions now live in a new Rich Description field on Map Pin, which supports formatting. Shortly after you upgrade to Events 6.2, each pin's Description text is copied into Rich Description and the old Description field is emptied. Description is now deprecated.
Who notices: attendees on Navigator 1.10 or older see blank pin descriptions until they update to 1.11. Any report, list view, Flow or integration that reads Description goes blank.
What does not change: the text itself is kept. Pin names, positions, colors and the maps are unchanged. Orgs that do not use pin descriptions see no difference.
What to do: ask attendees to update Navigator, and point reports, list views, Flows and integrations at Rich Description.
Check if you are affected: run this before you upgrade. SOQL cannot filter a long text field, so export the result; any row with a Description means you are affected.

SELECT Id, conference360__Venue_Map__c, conference360__Description__c
FROM conference360__Map_Pin__c

Is Block Duplicate Registrations turned on for any of your events? Expect some registrations to be marked Failed as duplicates. (Salesforce upgrade required)

What changes: the setting used to be checked only on the event page. It now also applies when a registration is finally submitted, including registrations processed in the background. A duplicate is now marked Failed, with the reason in Error Message, where before it could complete.
What does not change: an ordinary duplicate is still stopped at checkout with an error, so most registrants never reach this check. Events with the setting off are unaffected.
What to do: nothing. If you watch Failed registrations, expect some that cite a duplicate.
Check if you are affected: any result is an upcoming event with the setting on.

SELECT Id, Name FROM conference360__Event__c
WHERE conference360__Event_Settings__r.conference360__Block_Duplicate_Registrations__c = true
AND conference360__Event_Start_Date__c >= TODAY

🔧 Action required

Use your own profiles or permission sets instead of the Blackthorn ones? Give them access to six fields. (Salesforce upgrade required)

Why: without access, the Session Rules panel or the Venue Maps card can fail to load, and registrations can fail with an access error.
Who: anyone using a custom profile or permission set, including the user that processes registrations. The Blackthorn permission sets already include these fields.
What to do: give read access (edit for organizers) to the fields below.
If registrations already failed: check Process on each failed Event Registration Submission to run it again.

Object	Field
Session Rule	Sort Order
Session	Sort Order
Map Pin	Rich Description
Venue Map	Pin Size, Hide Pin Labels
Event Registration Submission	Processing Started

Find permission sets that need updating

Any result is a permission set or profile outside the Blackthorn ones that can read these objects and needs the field access above.

SELECT Parent.Name, Parent.Profile.Name, SobjectType FROM ObjectPermissions
WHERE SobjectType IN ('conference360__Session_Rule__c', 'conference360__Map_Pin__c',
  'conference360__Venue_Map__c', 'conference360__Event_Registration_Submission__c')
AND PermissionsRead = true AND Parent.NamespacePrefix != 'conference360'

Use Page Designer? Review who has Limited Access and Read Only. (Salesforce upgrade required)

What changes: after the upgrade, users with the Blackthorn Events Limited Access or Read Only permission set can open Page Designer. By default they can view and preview pages but not change them.
What does not change: users with Blackthorn Events Admin or Blackthorn Event Organizer keep their access.
What to do: check who holds those permission sets, and set what each level can do in Page Designer under Site Settings > Permissions.

✨ What's new

Items tagged Salesforce upgrade required are part of the Events 6.2 package and need to be installed by an admin. Items without a tag are already live for everyone, because they shipped automatically in our November webapp release.

🎟️ Sessions & agenda

Set the order of Session Rule groups by drag and drop (Salesforce upgrade required)

You can now drag and drop Session Rule groups, and the sessions inside them, to set the order registrants see them in when choosing sessions at checkout.

Sessions keep their order within each day.
A session order set on the ticket itself still takes priority.
Groups you have not ordered follow, sorted by name.

🗺️ Venue maps

Formatted pin descriptions, pin sizes and hidden pin names (Salesforce upgrade required, plus Navigator 1.11)

Formatted descriptions: pin descriptions can now use bold text, lists and links.
Pin size: choose a size for each venue map's pins, from Small to Extra Large.
Hide pin names: show pins without their names on a venue map.
Editor: a new toolbar, a larger description window and a pin list you can collapse.
Attendees see these changes in Navigator 1.11. Existing pin descriptions move to the new formatted field on upgrade; see Possible breaking changes.

🎨 Page Designer

Access levels: choose what Organizers and Limited Permission users can do in Site Settings > Permissions. (Salesforce upgrade required)
Organization default theme: set one theme as the default, and templates and imports take on its colors and fonts.
Font size per device: set separate text sizes for desktop, tablet and mobile.
Invite-only events: guests verify their email before they can see the page and register.
Refresh from Salesforce: pull the latest speakers, sessions and FAQs into an event right away.
Sign out from the Page Designer toolbar, and an option to keep the full navigation visible on desktop.

🔄 Salesforce & admin

Security improvements across lookups, the Email Editor and admin actions. (Salesforce upgrade required)
The Chat button has been removed from the Events Admin page. (Salesforce upgrade required)

🚀 Now in early access: Next-Gen Capacity Management

Next-Gen Capacity Management is a new way to manage event capacity that reserves a registrant's spot while they check out and handles waitlist offers in the order people joined. It is in early access and needs Events 6.2. To join the early access list, reach out to Blackthorn Support or your Customer Success Manager.

🐛 What's fixed

Items tagged Salesforce upgrade required are part of the Events 6.2 package and need to be installed by an admin. Items without a tag are already live for everyone, because they shipped automatically in our November webapp release.

✅ Registration reliability

The next waves of our registration reliability work, with more in upcoming releases.

Registrations processed twice (Salesforce upgrade required): Previously, the same registration could be processed twice at the same time. Now only one run processes it.
Session registrations left with no status (Salesforce upgrade required): Previously, a session registration whose result couldn't be saved was left with no status. Now it is retried.
Duplicate session registrations on retry (Salesforce upgrade required): Previously, retrying a failed session checkout could create duplicate session registrations. Now it doesn't.
Large group registrations retried over and over (Salesforce upgrade required): Previously, very large group registrations could be retried repeatedly without finishing. Now they finish processing.
Completed registrations marked Failed (Salesforce upgrade required): Previously, reprocessing a registration that had already completed marked it Failed if the new attempt hit an error. Now it stays Completed.
Unclear error for a missing registration (Salesforce upgrade required): Previously, processing a registration that had been deleted, or that the user could not see, failed with a confusing system error. Now it gives a clear message.

You may rarely see a new Processing status on an Event Registration Submission while it is being worked on. It clears on its own, and a registration left in Processing is retried automatically after 30 minutes.

🛒 Registration & checkout

Paying twice after returning from a payment page: Previously, registrants who returned from an online payment page before their registration finished processing could still see a payable checkout and pay a second time. Now they see a status page while their registration completes.
Skipping ahead past the attendee step: Previously, registrants could click the checkout step headers to move on from the attendee step without the checks the Continue button runs. Now the same checks and messages appear either way.
State or region required where there is none: Previously, checkout required a state or region for countries that don't have one, such as Singapore. Now it is required only where it applies.
Same email in different capitalization showed success: Previously, with One Unique Attendee Email Per Event turned on, a group registration that entered the same email in different capitalization showed a success message although the registration did not go through. Now the form flags the duplicate before you continue, and the error clears once you correct the email.
Duplicate error for guests with no name or email (Salesforce upgrade required): Previously, checkout was blocked with a duplicate error when two or more guests on the same ticket had no name or email and your duplicate rule was set to block. Now those guests no longer count as duplicates of each other.
Sold out while seats were still available (Salesforce upgrade required): Previously, during heavy registration traffic, an event could show as sold out or send registrants to the waitlist while seats were still available. Now an event shows as sold out only when its seats are gone.
Lead mapping and follow-up processing skipped (Salesforce upgrade required): Previously, registration form answers mapped to Lead fields, and other follow-up processing after checkout, could be skipped when other automation in your org ran at the same time. Now that processing runs.
Preview registrations were real: Previously, completing a registration from an event preview link created a real registration and attendee and used up capacity. Now a preview registration saves nothing and takes no payment.

🎟️ Sessions & agenda

Incomplete session counter text: Previously, the session counter at checkout showed incomplete text for tickets with a minimum number of sessions. Now it shows how many sessions are selected toward the minimum.

🌐 Event pages

"Error: 2006" when previewing a new event: Previously, previewing a newly published event, or refreshing its registration page, showed an "Error: 2006" message and sent you to the event group page. Now the event loads.

🎨 Page Designer

Empty Speakers, Sessions, FAQ and Sponsors components: Previously, these components showed nothing when the event's Event Settings hid that section. Now a component you add in Page Designer shows its content.
Sponsors carousel not scrolling: Previously, the Infinite layout sat still with only a few sponsors. Now it always scrolls.
Ticket spacing and labels: You can now set the space between tickets and hide the ticket type label.
Blank published pages: Previously, one incomplete component could blank the whole page. Now the rest of the page shows.
Location Card in narrow columns: Previously, the card overflowed narrow columns and phone screens. Now it fits.
UTM values on simple checkout: Previously, UTM values were not captured on Page Designer's simple checkout. Now they are, as on other layouts.
Two structure panels: Previously, saving a template opened a second, floating Structure panel. Now only the Page Structure panel remains.

👥 Groups & block tickets

Block ticket guests needed an email (Salesforce upgrade required, plus the webapp release): Previously, block ticket guests could not be saved without an email address on the Manage Guest Seats page, even when the ticket's attendee form set Email to Optional or Hide. Now they can, on Events 6.1 or later. Guests saved without an email are not matched to or created as Contacts.
Overlapping table cards in Table Manager (Salesforce upgrade required): Previously, table cards in Table Manager overlapped when tables had many seats. Now large tables scroll within their card.

🔄 Salesforce & admin

Events could not be deleted (Salesforce upgrade required): Previously, events could not be deleted, even by an administrator, once the daily reporting snapshot job had saved a snapshot for them. Now they can, and deleting an event also removes its snapshots automatically.
Registration Processing job stayed with the old user (Salesforce upgrade required): Previously, after you re-authorized Events and scheduled the recommended jobs, the hourly Event Registration Processing job stayed assigned to the previously authorized user. Now it moves to the newly authorized user.
Recurring series started at midnight (Salesforce upgrade required): Previously, recurring event series with a preset schedule were generated from midnight instead of the series' First Event Start Time. Now they use the First Event Start Time.
Install failed with a custom fiscal year (Salesforce upgrade required): Previously, installing or upgrading Events could fail in orgs that use a custom fiscal year. Now it completes.

🧱 Blackthorn Base 1.69

These ship in the Blackthorn Base package, not the Events package. If you upgrade through the Blackthorn Candy Shop, Base is upgraded to 1.69 as part of your Events upgrade. If you install packages another way, upgrade Base to 1.69 to get them; Events itself still requires only Base 1.66.

Advanced Visibility rules never took effect with encrypted Contact names (Salesforce upgrade required): Previously, Advanced Visibility rules never took effect in orgs that encrypt Contact names with Salesforce Shield Platform Encryption. Now matching contacts see the events and tickets their rules allow. After upgrading Base, click Refresh Rules on the Events Admin page.
Smart Scheduler links ready for Winter '27 (Salesforce upgrade required): Smart Scheduler links that open a new browser tab are ready for the Salesforce Winter '27 security update.

🛠️ Technical reference

This section is intended for Salesforce admins. Field API names, permission set details, and configuration notes are grouped by the feature they relate to.

Session Rule group order (2 fields)

Session Rule · Sort Order (conference360__Session_Rule__c.conference360__Sort_Order__c), Number (3, 0), no default. The order this Session Rule group is presented in when an attendee selects sessions for this ticket. Lower numbers appear first; groups without a Sort Order follow, ordered by name. Set by dragging groups in the Session Rules panel.
Track · Sort Order (conference360__Track__c.conference360__Sort_Order__c), Number (3, 0), no default. The order this Track should be placed in.

The Session Rules panel now also reads the existing Session · Sort Order field (conference360__Session__c.conference360__Sort_Order__c) to order the sessions inside each group. Users of the panel need read access to it.

Venue maps (3 new fields, 2 changed)

Map Pin · Rich Description (conference360__Map_Pin__c.conference360__Rich_Description__c), Rich Text Area (32,768), no default. Formatted instructions or notes attendees see for this pin.
Venue Map · Pin Size (conference360__Venue_Map__c.conference360__Pin_Size__c), Picklist (restricted): Small, Medium, Large, Extra Large; default Medium. Size of this venue map's pins in the attendee app. An empty value is read as Medium.
Venue Map · Hide Pin Labels (conference360__Venue_Map__c.conference360__Hide_Pin_Labels__c), Checkbox, default unchecked (pin names shown). Check to hide the name labels of this venue map's pins from attendees.

Map Pin · Description (conference360__Description__c), Long Text Area (1,000), is now deprecated. Its help text reads Deprecated: emptied on upgrade, use Rich Description. On upgrade from a version below 6.1, its text is copied into Rich Description and the field is emptied.

Venue Map · Event (conference360__Event__c) is no longer required at the field level, and is cleared when its event is deleted instead of blocking the delete.

Registration processing (1 field, 1 picklist value)

Event Registration Submission · Processing Started (conference360__Event_Registration_Submission__c.conference360__Processing_Started__c), Date/Time, no default. When the current processing run claimed this submission. Used to detect and recover runs that were interrupted. Left set as an audit trail after the run finishes; a value here does not by itself mean a claim is still active, check Status for that. Registration processing reads this field, so the user that processes registrations needs read access.
Event Registration Submission · Status (conference360__Status__c) gains the value Processing, which is not the default. A registration normally moves from To Process straight to Completed or Failed; one left in Processing is picked up again after 30 minutes.

Event deletion

The Event lookup on Event Daily Snapshot (conference360__Event_Daily_Snapshot__c.conference360__Event__c) and on Venue Map no longer blocks an event from being deleted; it is cleared instead. Deleting an event then removes its daily snapshots automatically. Venue maps are kept, with their Event field cleared. Attendees and other related records are not deleted.

Other objects in this package

Events 6.2 also adds objects and fields used by the Navigator and Mobile Check-in apps. They are described in those apps' release notes.

Permission sets

Field-level security for the new fields above is added across the Events permission sets: read for Blackthorn_Events_Community_Platform_User, Blackthorn_Events_Limited_Access, Blackthorn_Events_Lite_User and Blackthorn_Events_ReadOnly, and edit where organizers set the value for Blackthorn_Event_Organizer and Blackthorn_Events_Admin. Blackthorn_Events_Community_Guest_User gains read on the three venue map fields. Blackthorn_Events_Limited_Access can now edit Attendee · Source (conference360__Source__c).

Two grants are removed: Blackthorn_Event_Organizer and Blackthorn_Events_Admin no longer grant View All or Modify All on Seat (conference360__Seat__c) and Table (conference360__Table__c). Both objects keep their Read/Write internal sharing default. See Possible breaking changes.

⬆️ How to upgrade

Go to the Blackthorn Candy Shop to upgrade Events to 6.2. Events 6.2 still requires Blackthorn Base 1.66 and Blackthorn Payments 6.59 or later, so if you are current on October you already meet both. We recommend upgrading Blackthorn Base to 1.69, Payments to 6.71 and Events to 6.2 together; the Candy Shop takes you through them in the standard upgrade path. See Action required above.

For step-by-step instructions, click here.

Webapp changes arrive with the November webapp release and need nothing from you to install. Navigator 1.11 and Mobile Check-in 1.4.8 arrive through the App Store and Google Play and are covered in their own release notes; the venue map changes need Navigator 1.11, and Mobile Check-in 1.4.8 requires iOS 18 or Android 12 or later.

Questions about anything here go to your CSM or Blackthorn Support.

November 2026 - Version 6.2