June 2023 - Version 3.102

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

Labeling Updates

To simplify the release note process, we have relabeled the different sections in the Release Notes. Going forward, each bullet point will be listed under either BT Salesforce Release or Webapp Release (previously referred to as a platform release). The BT Salesforce Release typically occurs the week before the Webapp Release.

• For more information about the new terminology, please review Important Definitions.
• To review the dates for each release type, please see the Blackthorn 2023 Release Dates.

Off-Cycle Release

June 29, 2023

• Performing a hard refresh on an Event Group URL will no longer cause some of the Events in an Event Group to disappear. Previously, if a user queried more Events than the query limit, only recurring Events from the last request remained. (Known Issues: 000002900 and 000002915)

June 22, 2023

• June’s Webapp release contained a version conflict for the social media fields on the Speaker object. This conflict prevented Event websites from loading if the Event included Speakers. (Known Issue: 000002896)

May 17, 2023

• Event organizers can now edit an Event with existing custom field values using the Event Wizard. Previously, custom field values were not displayed in the Event Wizard. which resulted in overwriting custom field values with blanks. (Known Issue: 000002738)
• Inactive and deleted Events that were part of an Event Group will no longer appear in their Event Group. Previously, a hard refresh to the Event Group page was required to remove inactive and deleted Events. (Known Issue: 000002683)
• Big List Groups will now load correctly without needing to perform a hard refresh. A bug introduced by the May 3, 2023 release caused an intermittent issue where a hard refresh was required to load a Big List Group.
• An Attendee, who was previously on the waitlist but now has Registration Status = “Pending”, will no longer see the “Sold Out” banner on the Event landing page after clicking their AttendeeLink. Previously, the pending Attendee could see the banner, which incorrectly indicated that they could not redeem their ticket.

BT Salesforce Release

Bug Fixes

• The automation that processes Form submission answers has been updated, so that a high volume of records is less likely to fail, and Form submission answers map correctly. (Known Issue: 000002715)
• An Event organizer can now use the Event Wizard to clone an Event with multiple Sessions and update the new Sessions in the Wizard. Previously, updating or deleting a single Session modified multiple Sessions. Also, deleting and re-adding a Session created duplicates. (Known Issue: 000002575)
• A Payment Gateway that is used for both past and future Events can now be updated, including changes made to the Default checkbox, without causing an error. Previously, this type of update would fail if the Payment Gateway was used for a significant number of past Events. (Known Issue: 000002764)
• Users can pre-fill Attendee data from existing Contacts that use a two-line street address. Authenticated Experience Cloud users can also register themselves using their pre-filled two-line street address value. Previously, two-line street addresses caused registrations to fail. (Known Issue: 000002705)
• The Blackthorn | Events (Limited Access) permission set now includes the CREATE permission in the Form Submission Answer and Blackthorn Events Form Submission objects. An Events user with the Blackthorn | Events (Limited Access) permission set can successfully register Attendees using the Attendee Registration Lightning Web Component for Events with pre-registration Forms. Previously, limited access to Forms prevented successful registration. (Known Issue: 000002710)
• An Attendee who completes the registration process from an AttendeeLink will see their Attendee Status update to "Registered" once the process is complete. Previously, the Attendee Status update would intermittently fail. (Known Issue: 000002744)
• Attendees will now see an update to the Event Group when any of the following fields are updated. This change extends the existing list of fields that trigger an update to the Event Group webpage.
  • Event object
    • UI Experience
    • Description
    • Custom CSS URL
    • Event Settings
  • Event Group object
    • Event Settings
  • Event Settings object
    • Primary Color
    • Data Dictionary Group

Webapp Release

Bug Fixes

• The picklist option “Debug” is now hidden from the Event Page URL Language picklist. Users can still access the debug mode by modifying the Event’s URL. To view component labels, replace the language code. For example, replace “en” (for English) with “debug”.
• An Attendee can now access a post-registration Form by clicking their AttendeeLink. Previously, a bug prevented the Form from loading. (Known Issues: 000002687 and 000002767)
• When an Attendee registers for the last available Session before the waitlist, they will see the Select button change to the Registered button. Previously, the last Attendee’s registration would process successfully, but the Select button would incorrectly change to Waitlisted.
• Attendees who are waitlisted for multiple Sessions can now remove themselves from a Session’s waitlist without also removing themselves from the other Sessions’ waitlists. Previously, this caused an Attendee to be removed from all Sessions’ waitlists and created duplicate waitlist registrations when the Attendee tried to re-register. (Known Issue: 000002757)
• The mobile phone value on an Attendee record that was collected during an Event’s registration will NOT include a space between the country code and the phone number. Users are now able to initiate a phone call from their computer telephony integration (CTI) tool.
  NOTE: This fix only applies to registrations processed after the package update is installed. Affected customers are responsible for cleansing historical data.
• Attendees registering for an Event on a desktop computer can now click on a Session, scroll up and down, and see the list of Sessions on the page. Previously, clicking on a Session would freeze the page and prevent scrolling. (Known Issue: 000002727)
• Attendees registering for an Event via an AttendeeLink cannot see a Session if Hide on Event Page = "True". Previously, Sessions with Hide on Event Page = "True" were hidden from the public but not from those registering via an AttendeeLink. (Known Issue: 000002768)
• If an Event’s Event Settings include Spanish as a Supported Language, the back navigation arrow’s label will now be correctly translated into Spanish.
• Attendees will now see the proper currency symbol for the Discount Amount field as dictated by the Event's Currency field. Previously, the US dollar symbol was displayed for Discount Amount regardless of Currency value. (Known Issue: 000002742)
• An Event will show “Sold Out” when all main event tickets (Event Item Type = “Main event ticket”) are sold out even if guest tickets (Event Item Type = “Guest”) are still available. Previously, an Event appeared to have tickets available when only guest tickets remained, despite the restriction that a guest ticket cannot be purchased without a main event ticket. (Known Issue: 000002338)
• Attendees whose billing address is in Germany, Austria, and Switzerland will now see the Postal code field and are required to enter a value to process their payment.

Mobile Check-in App

Bug Fix

• When using a BT External ID QR code with the Mobile Check-in app to create a new Attendee, users no longer need to remove the parentheses from the prefilled phone number before saving the Attendee record. (Known Issue: 000002696)
• Mobile Check-in app users can now enter a non-US phone number when creating a new Attendee. Previously, a country code picklist wasn’t available and a 10-digit phone number was required, making the Add Attendee Phone field exclusive to US phone numbers.
• Users can now create new Attendees using the Mobile Check-in app while in Offline Mode (Airplane mode). The Attendee will be created in Salesforce when the Offline Mode is turned off. Previously, new Attendee creation failed when the app was in Offline Mode. (Known Issue: 000002784)
• The First Name, Last Name, Title, and Company on an Attendee badge will wrap to a second line. Previously, long entries were cut off. Note: A Mobile Check-in app user can change the font size to further accommodate a very long name. (Known Issue: 000002438)

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 make sure the correct versions of Base Package and Payments are installed before installing Events.

For step-by-step instructions, click here.

Testing

From now until 06/13/23, 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 Webapp.

1. Replace the Event Page and AttendeeLink URLs, events.blackthorn.io' domain, with 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:
https://events.blackthorn.io/2E12oua7/attendee/ty2W6t9awokrDMaLWi8Mf4sLMedhdrWSBHw6HS7kqVnJ0kKmCK63yl0IxWpbAUBo

2. Click the attendee URL so it opens in a new page. Then replace "events.blackthorn.io" with "preview.events.blackthorn.io". It will look like this:

https://preview.events.blackthorn.io/2E12oua7/attendee/ty2W6t9awokrDMaLWi8Mf4sLMedhdrWSBHw6HS7kqVnJ0kKmCK63yl0IxWpbAUBo

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