February 2025 - Webapp Release

Please review the updates below and follow the upgrade instructions to upgrade your Events application.

Table of Contents

• Webapp Release

• Upgrade Instructions

• Important Definitions

Webapp Release

Bug Fixes

• Express Registration: When using Express Registration, a user can select a new Contact in the same Account, and the address will reflect the information in the new Contact record even if the address on that record is blank. Previously, when a user selected a new Contact record with blank address fields, the address information from the first Contact record remained.

• Keywords: Attendees can search an Event Group webpage using the search-by-keyword functionality. Previously, the search results did not display results even if a Keyword was assigned to an Event. (Known Issue: 000004319)

• Checkout: If an Attendee enters a phone number with an alphabetic character, such as “A,” when the Event’s UI Experience is set to “Dynamic,” they will receive the following error. "Please enter numbers only, no special characters, except for the plus sign." Previously, Attendees received an incorrect “This is required” error.

• Events: Text on an Event’s webpage will appear as formatted in the corresponding rich-text fields on the Event record. Previously, Attendees saw extra white spaces between paragraphs in the Event’s Description, which did not match how the text was formatted in the Event record. (Known Issue: 000004264)

• Time Zones: Events in the European Central time zone will display CET during winter daylight saving time. Previously, Events incorrectly displayed CEST during winter daylight saving time. (Known Issue: 000004320)

• Event Groups: Attendees can view images stored in the Event Group’s Description rich-text field on an Event Group’s webpage. Previously, images added to the Event Group’s Description field were broken on the Event Group’s webpage. (Known Issue: 000004035)

• Capacity Management: The following updates were made to Event-level capacity management. (Known Issue: 000004283)

  • If an Attendee selects a Ticket with Type = “Main event ticket,” the number of available Tickets with Type = “Guest” or “Other” will not be impacted. Previously, when an Attendee selected a main Ticket, the number of available Guest Tickets decreased by the number of main Tickets selected.

  • If an Event Item has a value in the Maximum Quantity field, Attendees can only add up to that number of Tickets to the cart. Previously, Attendees could add more Tickets than the number in the Maximum Quantity field to the cart.

• Mobile Devices: If an Attendee views an Event with the UI Experience set to “Dynamic” on a mobile browser, they can scroll to the bottom of the Speakers’ bios and see all the content. Previously, the content at the bottom of the bio was out of view.

• Speakers: If a Speaker’s Status = “Confirmed” and Speaker Visibility = “Hidden,” the Speaker will not be visible on the Event webpage’s Speaker list. Previously, the Speaker was visible even though Speaker Visibility was set to “Hidden.”

• Translations: Translations will be applied to picklist values when an Attendee selects a value to answer a question in a Form Element. Previously, translations were not applied because the picklist values were cached before the translations were applied. (Known Issue: 000004380)

• User Interface: If an Attendee with Registration Status = “Invited” views an Event with UI Experience set to “Dynamic,” they will see the full RSVP/Redeem Ticket banner at the top of the webpage. Previously, the banner was cut off. (Known Issue: 000003418)

• Accessibility: When using the screen reader to move between items in the toggle menu on an Event Group with the UI Experience set to “Maple” or “Aspen,” the user’s selection will be kept, and the screen reader will remain focused on that item in the list. Previously, the selection was kept, but the screen reader’s focus returned to the first item in the list.

Event Registration

• If a user opens multiple tabs in a browser, each with the same Event, the user can register different Attendees in each tab. Previously, the user got a “Checkout failed, please try again later” error because the browser’s local storage was shared amongst the different tabs. Each tab’s data is now stored in its own session. (Known Issue: 000004156)

• If an Attendee registers for an Event with a high volume of registrations and the Event’s Pending Capacity is greater than “10,” they will see the following message on the confirmation page, “Thank you for your registration! Due to a high volume of sign-ups, it may take a little longer for your confirmation email to arrive. We appreciate your patience and are working to process all registrations as quickly as possible.” Previously, it took some time for Attendees to receive their confirmation email, causing uncertainty about whether their registration was successful. (Known Issue: 000004151)

Enhancements

• User Interface: Attendees can successfully view and scroll through an Event Group webpage at high zoom levels without titles and website content being cut off.

• Social Sharing: From an Event webpage, Attendees can open the Share feature and click the Email icon to share the Event via email. Their configured email app will open a new email with the Event title in the Subject and a sharable URL in the body.

• Translations: The picklist Translation feature now allows users to set translated values on the Translation object using the format “<Original picklist value>:<Translated picklist value>” or “Apple:Manzana”. When a user selects a translated picklist value, the original picklist value will be stored in Salesforce to ensure accurate Form mapping and reporting. Please review our documentation to learn more about this feature.

Accessibility

• When an Attendee uses a screen reader and keyboard navigation to open a webpage with a cookie dialogue, the user can disregard or tab out of the dialogue without making a selection.

• When an Attendee uses a keyboard to navigate an Event Group webpage with UI Experience set to “Calendar,” they can either tab from the All Categories picklist to the Calendar icon without listening to the picklist values or click Return to navigate through and listen to the picklist options.

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.