October 2022 - Version 3.78
  • 24 Oct 2022
  • 5 Minutes to read
  • Dark

October 2022 - Version 3.78

  • Dark

If you have any questions about the release note, please don't hesitate to reach out to Blackthorn Support.

REQUIRED: The Candy Shop link must be used to upgrade the [MONTH] release for Events.

The Candy Shop is open! This is your one-stop shop for installs and upgrades. To visit the Blackthorn Candy Shop page, go here.

Off-Cycle Release

Version 3.76.2

(September 20, 2022)

  • Scanning a QR Code that was received via email with the Mobile Check-in app no longer errors and will now prompt the Attendee to complete the registration process.
  • To prevent an error from occurring when using a QR Code to check in an Attendee on the Mobile Check-in app, update the email template with the following code.


<img src="[http://api.qrserver.com/v1/create-qr-code/?size=150x150&data={!conference360__Attendee__c.conference360__CASESAFEID__c}" alt="QR"/>


<img src="{!conference360__Attendee__c.conference360__QR_Code__c}" alt="QR"/>


Front End

  • A new field, Form Element Default Value, is now available on the Translation object.
    • Field Label: Form Element Default Value
    • API Name: conference360__Form_Element_Default_Value__c

Back End

  • A System Admin cannot deactivate the current Blackthorn Events authorized user until a new authorized user is configured. The System Admin can then delete the original authorized user.

Bug Fixes

Front End

  • Attendees are not able to register for an Event if the Event only offers an Event Item with Type = “Guest”.
  • The text for a Session’s Description will display in the preselected color when an Attendee registers for an Event.
  • If the UI Experience = “Simple”, the AttendeeLink’s browser’s tab will correctly reflect the Attendee’s Registration Status.
  • The Track Name in the drop-down filter on an Event’s Sessions page will now be translated into the selected language.
  • Attendees with an AttendeeLink can successfully register for an Event with Sessions.
  • When the UI Experience = “Full-Width” and an Attendee is registering for an Event, the Attendee will only be able to tab between the elements or fields in the Checkout modal.
  • All Form Elements will be visible regardless of the conditions applied and the languages translated.
  • When the UI Experience = “List”, Events in an Event Group will be sorted the same regardless of the web browser that is used.
  • After registering for an Event, Attendees will now be redirected to TouchNet to complete the payment process.
  • Discount Codes will now be applied correctly to Events/Event Items during checkout.

Back End

  • Users can now successfully send an Email from the Event record regardless of subject line length.
  • After Contacts with Member Status of “Sent” or “Registered” status are added to a Campaign that is related to an Event, the Event’s Invited and Registered fields will update accordingly.
  • Clicking the Clone button on an Event record will allow the user to clone the Event without any errors.
  • Creating Form Elements one after another without refreshing the screen will no longer override the most recently created Form Element.
  • Users can successfully edit a Company Info record when Use for All Events = “True”.
  • Clicking the Create Test Records button on the Blackthorn | Events Admin tab will result in the creation of seven sample Events.
  • If an Attendee’s Email contains an apostrophe, their Event registration will now process successfully.
  • The buttons on the Form Element page will perform the following tasks.
    • Save button: The Form Element will be saved, and the user will remain on the Form Element page.
    • Save and close button: The Form Element will be saved, and the Form Element page will be closed.
    • Back button: If the user clicks Yes on the Back to Form window, the Form Element will be saved. If the user clicks No on the Back to Form window, the Form Element will not be saved.
  • When an Attendee’s Registration Status changes from “Waitlisted - Pending” to “Pending” and the Event’s Event Setting field One Unique Attendee Email Per Event = “True”, the Attendee will be able to successfully register for the Event.
  • If an Attendee is created with Visibility Control = “Member” and the AttendeeLink is used to register the Attendee for an Event, the Attendee record will update correctly and the registration process will proceed as expected.
  • To ensure upcoming Events can display an AttendeeLink banner, Event names can now include the following strings: Cart, Overview, Checkout, and Precheckout. Previously, a validation in our codebase caused URL Parameters, which include Event names with those strings, to hide the AttendeeLink banner.
  • The color of the Event Item Description text on the Event page will now match the color chosen in the Event Item record.

Mobile Check-in App


  • If a Mobile Check-in app user tries to log in but is missing the correct permissions, they will receive the following message. “User is missing permissions to log in, please contact an administrator.”

Bug Fixes

  • The correct timezone for an Event will be used in the Mobile Check-in App, ensuring the Event is located in the correct tab.
  • After updating incorrect Attendee information in Salesforce, the updated Attendee information will now be available in the Mobile Check-in app.

Field/Layout Updates


  • A new field, Form Element Default Value, is now available on the Translation object.
    • Field Label: Form Element Default Value
    • API Name: conference360__Form_Element_Default_Value__c

Admin Upgrade Instructions

To upgrade Events to the newest version, go to the Blackthorn Candy Shop.

Blackthorn has adopted Salesforce’s managed package installer to simplify the installation process.

Since Payments is already installed, the installer will install Base Package and make sure the correct version of Payments is installed before installing Events.

For step-by-step instructions, click here.


From now until 10/11/22, the directions below will teach you how to test the new front-end features, enhancements, and bug fixes until they are automatically pushed to the front end.

To Do

You will need to replace the Event Page and AttendeeLink URLs, events.blackthorn.io' domain, to a test domain.

TEST DOMAIN: https://preview.events.blackthorn.io/

For example, when you create your attendee, an AttendeeLink URL is generated with the "events.blackthorn.io" domain like this one:


You'll then click on the attendee URL so it opens up in a new page. Remove "events.blackthorn.io" and replace it with "preview.events.blackthorn.io" so it looks like this:


If you have any questions about this or need help with testing, please don't hesitate to reach out to Blackthorn Support.