November 2024 - Version 4.40

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

Table of Contents

• BT Salesforce Release

• Webapp Release

• Field/Layout Updates

• Upgrade Instructions

• Important Definitions

Off-Cycle Release

November 20, 2024 - Social Sharing Update

The Event Settings Enable Social Sharing checkbox allows Event Organizers to show or hide the Share button on an Event webpage.

• Object: Event Settings

• Field Label: Enable Social Sharing

• API Name: conference360__Enable_Social_Sharing__c

• Data Type: Checkbox

  • Default: Unchecked (hide button by default)

  • When enabled (checked), potential Attendees will see the Share button across all user interfaces.

  • When disabled (unchecked), potential Attendees will not see the Share button.

If you don’t want Attendees to see the Share button, no additional action is needed.

To use the Enable Social Sharing checkbox, click here for setup steps.

Bug Fixes

• Send Email Component: The confirmation question that appears when using the Send Email component on an Event or Attendee record was updated. It now says, “Are you sure?” (Known Issue: 000003751)

• Reports: Attendee summary counts from an Event and those in the Event’s reports will match. Previously, Person Accounts were handled incorrectly in the EventRegistrationBatchProcess batch job, generating error logs. (Known Issue: 000003952)

• Event Record: The Donations and Products tabs on the Event record’s page were updated to include their own Related List with Line Items. This ensures that purchased Donation and Product Line Items related to the Event appear on their respective tab. Previously, each one’s List View was blank. (Known Issue: 000003159)

• Mapping: The logic for the Blackthorn | Events Settings custom setting Disable Attendee/Contact/Lead Fields was updated so the following occurs. Previously, when an Attendee registered for an Event, the Contact’s Email field was updated when the Blackthorn | Events Settings custom setting Disable Attendee/Contact/Lead Fields was set to “True” (checked). (Known Issue: 000003955)

  • Now, when the Blackthorn | Events Settings custom setting Disable Attendee/Contact/Lead Fields is set to “True” (checked), only the Attendee’s First Name and Salutation fields will be mapped to the Attendee, Contact, or Lead record if the corresponding fields are blank.

  • When the Blackthorn | Events Settings custom setting Disable Attendee/Contact/Lead Fields is set to “False” (not checked), the Attendee’s First Name, Email, Phone, and Salutation fields will be mapped to the Attendee, Contact, or Lead record if the corresponding fields are blank.

• Event Items: An Event Item’s Quantity Available and Quantity Remaining will be correctly calculated when sharing logic is set to private for partner users and partner users register new Attendees. Previously, the Attendee rollup logic incorrectly calculated those quantities. (Known Issue: 000003959)

• Capacity: When processing multiple Event registrations in a short period of time, the configured capacity will limit the number of accepted registrations. Previously, the number of registrations could exceed the capacity limit by one.

• Event Settings: The Event Settings Show Expired Tickets field default setting is now “True” (checked). By default, expired Tickets will be visible on Events. To hide expired Tickets, set Show Expired Tickets = “False” (unchecked).

• Campaigns: Users can relate one Campaign to only one Event. If a user tries to relate a second Event to the same Campaign, they will receive an error message letting them know that the Campaign is already associated with an Event. Previously, when users tried to relate one Campaign to two Events simultaneously using the Add Attendees component, incomplete Attendee lists were created. (Known Issue: 000004038)

• Accounts: When creating an Event with a new Venue Account in the Event Builder, users must select the Account record Type before launching the New Venue Account edit page. Previously, users received the following error when selecting a value in the Account record Type  field. "RecordTypeId is not a valid lookup field." (Known Issue: 000003868)

• Guest Registration: When a primary Attendee registers a guest without a name for an Event and sets the Relationship Settings’ Relationship Rule to “Create New Record If No Match,” the following will occur. Previously, a Blackthorn Log was generated with the error "REQUIRED_FIELD_MISSING: Required fields are missing: [LastName]" (Known Issue: 000004086)

  • The Guest Attendee’s Last Name will be the primary Attendee’s Last Name + Guest [Number].

  • If an email is not provided for the guest, the primary Attendee’s Email will be used.

• Accessibility: The Attendee Registration/Form modal was modified to improve accessibility for users who use screen readers. (Known Issue: 000003430)

  • When using the tab key or down arrow key to navigate through the modal, screen readers will read the input field labels for custom questions.

  • Users can click Select on an Event Item to open the Attendee Form modal and tab through the form fields if there are multiple Event Items. The modal will stay in focus while a user selects an Event Item.

  • Screen readers can read the Event Item  Public Item Name when a user navigates through the Event.

  • After registering a guest for an Event, the screen reader can read the Registration Completed message.

BT Email Configuration Component

• Users with the Blackthorn | Events (Organizer) permission set can now use the BT Email Configuration component as expected and send emails. We reverted a recent change that prevented Event Organizers from sending emails because the change enforced system permissions on Org Wide Email addresses. (Known Issue: 000004202)

• Emails sent to a newly registered Attendee will be sent from the org-wide email address selected in the Send Emails From field in the BT Email Configuration component. Previously, emails were sent from the email address of the user who last modified the Event record.

Event Builder

• The labels for the Event Builder field sets on the Event object have been updated to the following. Previously, the labels referenced V2 Event Wizard.

  • Blackthorn | Event Builder Event Details Section (conference360__Blackthorn_V2_Event_Wizard_Category_Sect)

  • Blackthorn | Event Builder Main Section (conference360__Blackthorn_V2_Event_Wizard_Main_Section)

  • Blackthorn | Event Builder Organizer Section (conference360__Blackthorn_V2_Event_Wizard_Extra_Section)

  • Blackthorn | Event Builder Venue Section (conference360__Blackthorn_V2_Event_Wizard_Venue_Section)

  • Blackthorn | Event Builder Virtual Section (conference360__Blackthorn_V2_Event_Wizard_Virtual_Secti)

• The Event object’s Free checkbox field is now available in the Blackthorn | V2 Event Wizard Event Details Section (Blackthorn | Event Builder Event Details Section) field set, making the Free checkbox available in the Event Builder. Previously, the Free checkbox was not available in the Event Builder. Note: To use the Free field in the Event Builder, you must add the Free field to the “In Field Set” column. Go to the Object Manager > Event (conference360__Event__c) > Field Sets tab > Blackthorn | V2 Event Wizard Event Details Section (Blackthorn | Event Builder Event Details Section) and add the Free field to the “In Field Set” column. (Known Issue: 000003768)

Enhancements

• Event Settings: The help text on the Event Settings Show Expired Tickets field was updated to the following. “When true, tickets with Sale End Date in the past will be visible for as long as the event is visible. However, they will not be selectable. When false, tickets with Sale End Date in the past will be hidden.”

• Event Builder: The Event Organizer (Contact) field is now available in the Event Builder’s field set. Users can select the field and add it to the Blackthorn | V2 Event Wizard Organizer’s “In the Field Set” column to use in the Event Builder.

• Session Attendees: If a user adds or removes a Form from a Session, the existing Session Attendees’ records will be updated automatically. For example, if a post-registration Form lookup field is updated, the Form URL will be updated on the existing Session Attendees’ records.

• Event Deep Clone Layout: The Event Deep Clone layout field set now includes the Event’s Event Location field.

• Donations: Predefined Donation amounts can now include decimal points, allowing users to set more precise donation options, which can be important for branding, special campaigns, or user preferences.

• Form Mapping: To improve Form mapping functionality, error handling was added for restricted picklist values. When a restricted picklist value is mapped incorrectly, BT Error logs are created, and the Form Submission Answer record will contain an error message in the Mapping Error field.

• Zoom: The new Include Zoom URL In Calendar Description field was added to the Event object to allow users to show/hide Zoom links in the invite’s Calendar Description field after an Attendee clicks the Add to Calendar button. If Include Zoom URL In Calendar Description = “True” (checked), the Calendar’s description will include text similar to “To join the meeting directly, click here: https://zoom.com/url/to/meeting.”

  • Object: Event

    • Field Label: Include Zoom URL In Calendar Description

    • API Name: Include_Zoom_URL_In_Calendar_Description__c

    • Data Type: Checkbox

    • Default value: unchecked

    • Description/Help text: When enabled, the Zoom URL will be included in the invite’s Calendar Description field.

  • NOTE: Attendees who join via the direct Zoom link will NOT have their Attendance Status updated in Salesforce. However, Attendees who join the Zoom meeting/webinar via their AttendeeLink WILL have their Attendance Status updated.

Event Items Default Quantity

Event Organizers can use the new Event Item’s Default Quantity Selection field to define the default quantity for Tickets, Guest Tickets, or Products that are automatically added to the cart when an Attendee reaches the ticket selection step.

• Object: Event Item

• Field Label: Default Quantity Selection

• API Name: conference360__Default_Quantity_Selection__c

• Data Type: Number

• Description/Help Text: This number designates a default quantity of items in the registrant’s cart. The registrant can add or remove items to override the default selection.

• Default value: 0

• Validation

  • The Default Quantity Selection value must be between the Event Item’s Minimum Quantity and Maximum Quantity.

  • The Default Quantity Selection value must be 0 or greater.

  • The Default Quantity Selection value must be a whole number (no decimals).

When an organizer enters a value in the Event Item’s Default Quantity Selection field, and the Event Item isn’t sold out, the default quantity is automatically added to the cart the first time an Attendee reaches the ticket selection screen.

If the Attendee changes the number of tickets in their cart, they can move around the Event’s webpage, and no changes will be made to their cart based on the default quantity.

If the number of remaining tickets is greater than 0 but less than the Default Quantity Selection, all remaining tickets will be added to the cart. For example, if the number of remaining tickets is 3, but the Default Quantity Selection is “5,” then 3 tickets will be added to the cart.

IMPORTANT NOTE: If a potential Attendee receives an invitation with an AttendeeLink and goes to the Event webpage from the AttendeeLink to purchase Tickets, Guest Tickets, or Products, the current behavior will occur. The new Default Quantity Selection functionality will not be applied, and the Default Quantity Selection value will not be added to the cart.

Webapp Release

Bug Fixes

• AttendeeLink: The AttendeeLink will pre-fill an Attendee’s Phone and Country fields based on their location. Previously, neither field was populated correctly.

• Accessibility: Users can navigate to and select a Category using the Tab key when viewing an Event Group. Previously, users couldn’t use the Tab key to select a Category.

• Forms: Cloning a Form with the Clone button will no longer cause a 2006 error on the Form URL. Previously, using the Clone button caused a 2006 error, which caused a 2004 error on connected Events. (Known Issue: 000003717)

• Translations: If an Attendee accesses an Event via an iframe or community, the Event’s webpages will translate according to the language selected on the host’s website. The Language Selector is also no longer available on the Event’s overview page and post-registration Forms. Previously, using Translations caused an error on the Event’s overview and post-registration pages when used with an iframe. (Known Issue: 000004096)

• Events: Text in the Event’s Description field will render consistently across the different UIs and appear as in the Salesforce rich text Description field. Previously, the text’s appearance was different for each UI Experience. (Known Issue: 000004012)

• Waitlisting: The logic for waitlisted Events was updated so that when an Event is sold out, and the waitlist is enabled, Attendees trying to register will receive the following message. “Warning: Some items are sold out, but you can register to the waitlist. Please try registering again to join the waitlist.” Previously, concurrent registrations caused Attendees to receive an error message stating that the Event was sold out instead of waitlisted. (Known Issue: 000003845)

Checkout Process

• The Ticket Selection screen will load during checkout for all UIs even after local storage is cleared using a browser’s developer tools. Previously, the Ticket Selection screen failed to load after clearing the local storage.

• If an Event uses an Authorize.net Payment Gateway, and an Attendee enters an incorrect zip code, they will see one of the following error messages. Previously, Attendees saw the “Warning: Checkout failed, please try again later” error message, which did not clearly explain the problem.

  • "The Transaction failed. Error: This Transaction has been declined."

  • "Transaction declined due to a billing address mismatch. Please ensure the entered details match those on file with the card provider."

• CSS styles were updated to ensure the Back navigation button and Event Name appear as expected when an Event’s UI Experience is set to “Dynamic” and an Attendee decreases the Event webpage’s screen size to 90 percent. Previously, the Back navigation button and Event Name overlapped on the Tickets/Attendee/Payments page.

Form Elements

• Images added to a Form Element’s rich text Supplemental Question Information field will now be public by default, ensuring they are visible on the Event’s webpage. Previously, images did not load correctly on a mobile device. (Known Issue: 000003975)

• When an Event has UI Experience set to “Simple” or “Dynamic” and a Form Element with Type set to “Divider,” users will see the Form Element as a divider block on the Event’s webpage. Previously, the divider block didn’t render as expected. (Known Issue: 000003743)

Enhancements

• Transact (CashNet): When an Attendee completes the checkout process for an Event with a credit card and on a Transact (CashNet) Payment Gateway, the gateway sends the payment data to Events. Salesforce then saves the data before the Attendee needs to sign out of Transact (CashNet). Clicking the Sign Out button will redirect the Attendee to the Event webpage.

• Accessibility: When an Attendee uses a screen reader during checkout, the screen reader will identify the different registration processing steps, including “Submitting,” “Processing,” and “Validating,” to help the user understand what is happening.

• Sessions: When an Event’s UI Experience = “Dynamic,” a Session’s start and end times will appear as follows.

  • If a Session’s Start Time and End Time fields are populated, Attendees will only see the Session’s start/end time range.

  • If a Session’s Start Date and Start Time fields are populated, Attendees will only see the start date and time.

  • If a Session’s Start Date field is populated, Attendees will only see the start date.

  • If a Session’s End Time field is populated but the Start Time field is blank, Attendees will not see a start/end time range.

• AttendeeLink: Users can create a personalized custom welcome message with a registered Attendee’s First Name and Last Name on the AttendeeLink with the Data Dictionary. For example, if the Key = “MSG_REGISTRATION_CONFIRMED” and the Value = “Thanks for registering {{Attendee.FirstName}} {{Attendee.LastName}}!”, the Attendee will see “Thanks for registering First Name Last Name!”

• Express Registration: Express Registration works for an Event with UI Experience = “Simple” and is not dependent on the number of Event Items related to the Event. Previously, Events with UI Experience = “Simple” with one Event Item did not appear in the Express Registration drop-down.

• Donations: Attendees can select predefined Donation amounts with up to two decimal points, such as $20.25 instead of $20.

• Zoom: If the Event’s Include Zoom URL In Calendar Description field is checked, Attendees will see that the Calendar’s description includes text similar to “To join the meeting directly, click here: https://zoom.com/url/to/meeting.”

• Data Dictionary: The Data Dictionary now includes an option to change/translate the time zone for the Event’s Event Start Date. The new Key is “LBL_DATE_TIMEZONE.” For example, if Key = “LBL_DATE_TIMEZONE” and Value = “Eastern Time Zone,” “Eastern Time Zone” will appear instead of “ET” on the Event webpage. The “LBL_DATE_TIMEZONE” Key only applies to the Event’s Event Start Date. It does not apply to other Event dates/times or Session dates/times.

Sharing on Social Media

Encourage Attendees to share your Event on social media. Click the Share button to generate a URL for Attendees to share Events on LinkedIn, X/Twitter, or Facebook. The shareable link includes metadata like OG tags to generate a URL preview for the image, title, and description.

Please note that the Share button is not available for Event Groups.

Clicking the Share button from an Event webpage, the Experience Cloud, or an unregistered Attendee’s AttendeeLink opens a window with a sharable link and buttons for each platform. When you click the LinkedIn, X/Twitter, or Facebook button, the following happens.

• LinkedIn: Enter a message to accompany the link and click Post.

• Twitter: Use the following message: “I am looking forward to attending [Event Name] - you can check it out here: [event social URL]") or edit it and click Post.

• Facebook: Enter a message to accompany the link and click Share. (Facebook will only correctly render images larger than 200x200px in Facebook posts.)

Field/Layout Updates

New

• Object: Event

  • Field Label: Include Zoom URL In Calendar Description

  • API Name: Include_Zoom_URL_In_Calendar_Description__c

  • Data Type: Checkbox

  • Default value: unchecked

  • Description/Help text: When enabled, the Zoom URL will be included in the invite’s Calendar Description  field.

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.