- 20 Sep 2022
- 6 Minutes to read
- Print
- DarkLight
September 2022 - Version 3.76.1
- Updated on 20 Sep 2022
- 6 Minutes to read
- Print
- DarkLight
If you have any questions about the release note, please don't hesitate to reach out to Blackthorn Support.
The Candy Shop is open! This is your one-stop shop for installs and upgrades. To visit the Blackthorn Candy Shop page, go here.
Breaking Changes and/or Critical Updates
The new field,
BT External ID
, was added to the Contact record. This field is used by the Blackthorn Mobile Check-In app to identify Contacts with a matching ID found in a non-Blackthorn QR Code. New installations will include permissions forBT External ID
. Existing users will need to update their permission sets.An individual is not registered for an Event that they want to attend, but they have a QR Code generated from their
BT External ID
value. At the Event, the Mobile Check-in app will scan the QR Code, redirect the Mobile Check-in app user to the Add Attendee page, and pre-populate the contact information. A new Attendee record will be created in Salesforce with the following fields pre-populated:First Name
Last Name
Email
Registration Status
= “Registered”Attendance Status
= “Attended”
If the Attendee already exists, the user will be able to check in the Attendee.
If an Attendee leaves the Country field on the Attendee Form blank when registering for an Event, the corresponding
Country
field in Salesforce will now be left blank, instead of populating with the location (country) of the IP address. If you rely on the Country field on the Attendee Form being automatically populated and the Country field is hidden, you will need to expose the field.
Off-Cycle Releases
Version 3.73
(August 2, 2022 at 9:35 a.m. EST (UTC-4))
- When creating a Form with a Form Element condition, conditional questions can not be created with identical parent and child elements.
August HotFix 3:
(August 9, 2022 at 9:30 a.m. EST (UTC-4))
- The permissions section on the Platform status page will show “success” when the orgs in question have the correct permissions.
Version 3.76
(August 23, 2022 at 2:40 p.m. EST (UTC-4))
- An Attendee/registrant will only be added once to a Zoom Webinar, avoiding an error. Clicking the Register Attendees for Webinars button will register Attendees who are not registered for a Webinar that is associated with an Event.
Version 3.76.1
(August 30, 2022 at 1:10 p.m. EST (UTC-4))
- 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.
Enhancements
Front End
When a user views an Event with Product and Donation Event Items in Dark Mode, the titles will now be in white.
When an individual sends an email from the Contact Us form of the Event page and the
UI Experience
= “Full-Width”, the subject line on the email received by the Event Planner will include both the Event name and the Subject from the Contact Us form. (“Event Name” - “Subject Entered on Contact Form”)When using Spreedly as the Payment Gateway and checking out for a paid Event, users will see an updated order of the address fields (
Street
,Country
,City
,State/Region
, andPostal Code
) in the Payment Information section. The update was made to create a consistent user experience during the checkout process.When a registrant accesses their AttendeeLink, the custom questions (Forms and Form Elements) will be populated with the registrant’s data from their Contact, Lead, Account, or Attendee record(s). Any changes made to the registrant’s information via the AttendeeLink will be updated automatically in the org. This functionality will work for any standard/custom field on the Account, Contact, Lead, or Attendee records.
The new AttendeeLink - Custom Questions mapping enhancement is feature flagged. To use it, you must contact Blackthorn Support with your Org ID to have it turned on.
Back End
- The new field, BT External ID, was added to the Contact record. This field is used by the Blackthorn Mobile Check-In app to identify Contacts with a matching ID found in a non-Blackthorn QR Code. New installations will include permissions for BT External ID. Existing users will need to update their permission sets.
Bug Fixes
Front End
A discount code will be applied correctly during checkout, independent of the Event Items that are added/removed from the cart.
On the Registration Form, the labels for standard fields and custom questions will now be placed above the text box.
After changing an in-person Event to an online Event and creating a new Webinar/Meeting for the Event, the registered Attendee's AttendeeLink will reflect the changes, showing the Join Video Stream instead of the QR code.
The font size of the text in the Event’s description on the
Event Page URL
will match the font size of the text in the Event record’sDescription
field.The
Cancel Registration
button will no longer be visible after an Attendee completes the checkout process for a paid Event.The default values on a Form with Form Elements will appear as expected when registering an Attendee via the Attendee Registration Component.
After an Attendee cancels their Event registration, they will now see the custom cancelation message from the
Ticket cancelation message
field on their AttendeeLink.If the Salesforce Nonprofit Success Pack (NPSP) package is installed and an Attendee enters a company’s name in the (optional) Company field on the Checkout Form, the Invoice will show the provided company name under
Account (Bill To)
andAccount Name (Bill To)
.Text entered with specific formatting (uppercase/lowercase) on the Attendee Form will appear as entered in the dropdown on the Contact Information screen.
Back End
When an Attendee registers for an Event using the "Pay Later" option, the
Contact
andAccount
fields on the Transaction and Payment Method records will be populated after the Attendee pays via their DocumentLink/Invoice.If a Code Eligibility is assigned at the Event level, the Code’s
Discount Amount
orDiscount Percentage
will be applied at the Event level or can only be used once per checkout.If a Code Eligibility is assigned at the Event Item level, the Code’s
Discount Amount
orDiscount Percentage
will be applied at the Event Item level or can be used once per each Event Item in the cart.When cloning an Event from the Event record, the Clone pop-up window will contain one y-navigation scroll bar.
The
Display Name
field was added to the Session page layout to ensure the Session’s name on theEvent Page URL
is updated after the Session’sSession Name
is changed on the Session record.If an Attendee does not have any related records, an error will no longer occur.
Field/Layout Updates
New
The new field,
BT External ID
, was added to the Contact record. This field is used by the Blackthorn Mobile Check-In app to identify Contacts with a matching ID found in a non-Blackthorn QR Code. New installations will include permissions forBT External ID
. Existing users will need to update their permission sets.After an Attendee cancels their Event registration, they will now see the custom cancelation message from the
Ticket cancelation message
field on their AttendeeLink.
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.
Testing
From now until 09/14/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.