December 2024 - Version 4.42

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

Table of Contents

• Off-Cycle Release

• 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.

No additional action is needed if you want to hide the Share button from Attendees.

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

BT Salesforce Release

Bug Fixes

• Permission Sets: Users with the Blackthorn | Events (Lite User) or Blackthorn | Events (Limited Access) permission set can successfully create, read, and edit Attendee records. Previously, those users received the "Insufficient permissions: secure query included inaccessible field" error message when trying to create Attendee records using a flow. (Known Issue: 000003892)

• Email Templates: If a user creates or clones an Email Template, the Email Template Name length must be 80 characters or less, including the developer’s name (the unique date/time that is added to the end of the email template API name). Previously, when users created an Email Template Name, they had to use specific validation for developer names, causing Email Templates not to be saved and BT Logs to be created. (Known Issue: 000004143)

• Attendance Summaries: A flag was implemented in the "Attendee Cancel Registration" process to manage asynchronous job execution, ensuring that attendance summaries update correctly after Session Attendees cancel their registration. Previously, the sequence of jobs caused the Event’s attendance counts and Attendance Summaries fields, such as Attended, Canceled, or No Show, to update incorrectly when an Attendee with a Session registration canceled their Event registration. (Known Issue: 000003993)

• Recurring Events: The value in the Total Capacity field on a Recurring Event will accurately reflect the value in the original Event’s Total Capacity field. Previously, when creating Recurring Events and refreshing the summary page of a Recurring Event, the Total Capacity was recalculated incorrectly. (Known Issue: 000003552)

• Confirmation Emails: Confirmation emails will be sent to Attendees as expected when registration criteria are met, ensuring they receive notifications promptly. Previously, confirmation emails failed intermittently, causing errors and preventing Attendees from receiving notifications and registration confirmations. (Known Issue: 000003985)

• Pending Capacity: A Session’s Pending Capacity will be updated automatically when the Pending Capacity on the associated Event Item changes. This ensures the Session record accurately reflects the number of available Event Items (Tickets) and the number of registered Attendees. Previously, the capacity logic did not include reducing Sessions that were related to an Event Item via the Event Item Session junction object. (Known Issue: 000004061)

Event Builder

• When using the Event Builder, users can successfully save an Event after uploading a Session’s image and accompanying text in the Alternative Text for Visual Impairment field. Previously, the Event would not save, and the user received an error about missing text in the Alternative Text for Visual Impairment field even though the text had previously been entered.

• Event Builder users can add Keywords to a Session from the Add Keyword lookup feature. Previously, the Add Keyword lookup field did not display Keywords related to the current Session in the search results. (Known Issue: 000003558)

Zoom

• Zoom webinar links will be regenerated only when the following fields on the Event or Session records are changed. A new Zoom link will not be created when any other fields are modified. Previously, multiple identical Zoom links were generated for an Event when users made edits from the Event Builder. (Known Issue: 000004085)

  • Event

    • Webinar/Meeting Account

    • Event Start Date

    • Event End Date

    • Event Start Time

    • Event End Time

  • Session

    • Webinar/Meeting Account

    • Start Date

    • End Date

    • Start Time

    • End Time

• If a Zoom meeting/webinar is created at the Session level, the Session Attendee’s Webinar/Meeting Join URL field will be populated with the join URL, and the Session Attendee will be added to the Zoom meeting or webinar. The Session Attendee will also sync to Zoom and appear as a registrant. Previously, the Session Attendee’s Webinar/Meeting Join URL and Approval Status fields were not populated when the Session record had Zoom Registration Approval Type = "Automatically approve registration." (Known Issue: 000004111)

Enhancements

• Data Dictionary Group: If a user clones a Data Dictionary Group that contains Data Dictionary Entries, the cloned Data Dictionary Group will contain the cloned Data Dictionary Entries. Previously, the related Data Dictionary Entries were not included in the cloning process. (Known Issue: 000003335)

• Event Builder: When scrolling through the Landing Page in the Event Builder, each section title in the navigation bar will be bolded as the user views that section.

• Attendee Record: Logic was updated on the Attendee record’s Source field, allowing users to track where the Attendee record was created. The new picklist options for the Source field are “Attendee Tab,” “Event Builder,” “Report,” and “Campaign Sync.” The update improves users’ ability to track the source of Attendees’ records and ensure accurate billing.

  • Example 1: Attendee Tab

    • A user creates an Attendee from Events, Accounts, Contacts, or Leads records via the "Add Attendee" component on the Event Detail page. The Attendee’s Source field will be set to “Attendee Tab.”

  • Example 2: Event Builder

    • A user creates an Attendee from Events, Accounts, Contacts, or Leads records via the "Add Attendee" component in the Event Builder or Event Wizard. The Attendee’s Source field will be set to “Event Builder.”

  • Example 3: Report

    • A user creates an Attendee via the "Add Attendee" component from Reports. The Attendee’s Source field will be set to “Report.”

  • Example 4: Campaign Sync

    • A user creates an Attendee from a Campaign record via the "Add Attendee" component on a Campaign record. The Attendee’s Source field will be set to “Campaign Sync.”

Display Donations & Products Separately

Create a customized checkout experience by separating the Donations and Products sections from the Tickets and placing them on their own pages. Separating everything helps Attendees find what they need. The Donations page offers an intuitive and focused interface, while the Products page highlights products to ensure they are visible to Attendees.

To place the Donations and Products sections on their own pages during checkout, set the new Event Settings field Display Donations & Products separately to “Yes” (checked). Note: If a Form is related to a Donation or Product record, the Form will be displayed on the page with the Donation or Product.

• Object: Event Settings

• Field Label: Display Donations & Products separately

• API Name: conference360__Display_Donations_Products_Separately__c

• Data Type: Checkbox

  • If the field is set to “Yes” (checked), Attendees will see the Donations and Products sections on their own pages, separate from Tickets.

  • If the field is set to “No” (unchecked), Attendees will see the Donations, Products, and Tickets sections on the same page. (currently functionality)

• Help Text: When enabled, the web application will render the "Donations" and "Products" sections on separate pages.

Event Images for Event Groups

An Event’s Thumbnail and Mobile Image URL field contains the default Event image used for Event Groups. The thumbnail image stored in this field can be used in three ways: to prevent the Event’s image from distorting when the Event has UI Experience set to “Dynamic” and is part of an Event Group; as the Event banner for a mobile device; or if a user wants to use a different thumbnail than the Event banner. (Known Issue: 000003917)

• Object: Event

  • Field Label: Thumbnail and Mobile Image URL

    • API Name: conference360__Thumbnail_and_Mobile_Image_URL__c

    • Data Type: URL(255)

    • Description: Optional URL used in the Event thumbnail image in Event Groups and as an event banner for mobile devices. The recommended aspect ratio is 2:1

  • Field Label: Thumbnail Image Name

    • API Name: conference360__Thumbnail_Image_Name__c

    • Data Type: Text(100)

• Note: The Thumbnail and Mobile Image URL field was added to the Event page layout and the Deep Clone Layout field set. Users can also add an image to the Thumbnail and Mobile Image URL field in the Event Builder.

• The logic works as follows:

  • If there's a value in the Event’s Thumbnail and Mobile Image URL field and a value in the Event’s Image URL field, then when an Attendee views an Event Group, they will see the image in the Thumbnail and Mobile Image URL field instead of the Event's Image URL.

  • If the Thumbnail and Mobile Image URL field is blank, but the Image URL field has a value, Attendees will see the Image URL when viewing the Event Group.

  • If both fields are blank, the Attendee will see a blank image.

Important Note

Contrary to the newsletter sent on December 19, 2024, the ability to add or remove the contact information/payment details page for free Events is not included in the December release. The new field (Remove Info Page for Free Events) is not yet functional. This enhancement is expected in the January release. We apologize for the confusion.

Webapp Release

Bug Fixes

• Event Webpage: If an Event has the UI Experience set to “Dynamic,” and an Attendee zooms in on the Event webpage so the screen size exceeds 100%, they will see the entire Event Name. Previously, the Event Name was cut off, causing the Attendee to see only part of it.

• Navigation: If an Event has the UI Experience set to “Tabbed” or “Dynamic,” an Attendee can use the browser’s back or forward button to move through the registration process. Previously, when an Attendee used the browser’s navigation buttons, the checkout forms were cleared, and clicking the Register button did not work.

• AttendeeLink: The Cancel Registration button on the AttendeeLink will be visible if today’s date is before the Event’s Cancel Before Date/Cancel Before Time. Previously, the Cancel Registration button disappeared when the Event Item’s Sales End Date and Sales End Time values were in the past, ignoring the values in the Event’s Cancel Before Date/Cancel Before Time fields. (Known Issue: 000004091)

• Iframes: If an iframed Event has an Event Item with an Address set to “Required,” Attendees can enter an international address and complete the registration process. This update ensures that the behavior for iframes Events is identical to regular Event webpages. Previously, the same scenario for an iframed Event resulted in an Event Registration Submission (ERS) error with the following error message. “The Attendee street and city and state attributes are required.” (Known Issue: 000004094)

• Event Builder: If a user creates an Event with UI Experience = “Dynamic” in the Event Builder, the Speakers will be listed on the Event webpage based on the value in the Speaker Visibility field. Speakers with Speaker Visibility set to “Featured” will be shown first. Previously, the featured Speaker wasn’t listed first. (Known Issue: 000003355)

• Forms: If an Event Organizer selects a value in a multi-select picklist Form Element as a default value, it will be marked as selected when an Attendee registers for the Event. Previously, when all values in a multi-select picklist Form Element were set as default options, all options but the first one was preselected. (Known Issue: 000002875)

• Accessibility: When Attendees use the Tab button to move through an Event Group with UI Experience = “Calendar,” they can click through the list of Keywords and select a single Keyword to filter a list of corresponding Events. Previously, clicking the Tab button did not shift the focus to the Keywords. However, if a Keyword was selected, it opened an individual Event instead of the list of related Events.

• Mobile Web Browser: When an Attendee registers for an Event from a mobile web browser, they will see the CAPTCHA and can easily complete the checkout process. Previously, Attendees had to expand the details to view the CAPTCHA verification, resulting in a confusing experience and preventing some Attendees from checking out. (Known Issue: 000004174)

Checkout

• If an Attendee enters the wrong CVC when completing the payment process for an Event with a Stripe Payment Gateway, they will get the following error. “Warning: Your card was declined.” Previously, the Attendee could complete checkout, and the transaction was successfully processed.

• The existing Stripe checkout process was updated to Stripe’s embedded checkout for Events. Users will see a warning message if they try to close the Stripe window before the payment is processed. Previously, the Event Registration Submission (ERS) record was left in draft status, which prevented necessary records from being created. (Known Issue: 000004148)

• If an Event’s UI Experience is set to “Simple” and the Phone field on the Attendee record has special characters (e.g., parenthesis and/or dashes), then when the Attendee registers for the Event via their AttendeeLink, the special characters will automatically be removed from the Phone field on the checkout page. Previously, the special characters in the Phone field remained, causing the following error. “Warning: Please correct errors in your information.” (Known Issue: 000004042)

• If an Event has both a paid and free Ticket and offers a discount amount, the Total amount due and the discount amount will be displayed correctly when the following occurs.

  1. Add the free Ticket to the cart.

  2. Add the discount/promo Code.

  3. Add the paid Ticket.

Enhancements

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

• Forms: When nesting questions (Form Elements) multiple levels deep, each Form Element appears under its parent question and in the correct sort order. Also, the Form Preview matches what the user sees when they click the Form URL. (Known Issue: 000003711)

• Iframes: A new iframe event listener, FORM_SUBMITTED, was added to the BT iframe to allow users to track results and gain insights from pre-registration form answers from within the iframe. When an Attendee submits a BT Form, the host page receives a FORM_SUBMITTED event with the following details from the pre-registration form.

  • path - form submission URL path

  • name - form name

  • data - form submission data

  • NOTE: Post-registration form answers will not trigger the event listener.

• Social Media: Images shared to social media platforms will display as expected since the image URL now points to Blackthorn's media content delivery network (CDN). Previously, images hosted on Salesforce sometimes appeared broken in the Facebook URL preview.

• Event Groups: Users can show secondary thumbnail/banner images for Events with the correct aspect ratio in an Event Group on a mobile device by using the Event’s Thumbnail and Mobile Image URL field. This is especially helpful for Events using the Dynamic UI since the Dynamic UI uses a different image ratio for Banners, which results in cropped thumbnails on the Event Group webpages. (Known Issue: 000003917)

  • Available Banner and Thumbnail Fields

    • Banner: Event’s Image URL (Image_URL__c) and Image Name (Image_Name__c)

    • Thumbnail: Event’s Thumbnail and Mobile Image URL (Thumbnail_and_Mobile_Image_URL__c) and Thumbnail Image Name (Thumbnail_Image_Name__c)

• 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)!”

Field/Layout Updates

New

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.

• Field Label: Display Donations & Products separately

  • API Name: conference360__Display_Donations_Products_Separately__c

  • Data Type: Checkbox

    • If the field is set to “Yes” (checked), Attendees will see the Donations and Products sections on their own pages, separate from Tickets.

    • If the field is set to “No” (unchecked), Attendees will see the Donations, Products, and Tickets sections on the same page. (currently functionality)

  • Help Text: When enabled, the web application will render the "Donations" and "Products" sections on separate pages.

Object: Event

• Field Label: Thumbnail and Mobile Image URL

  • API Name: conference360__Thumbnail_and_Mobile_Image_URL__c

  • Data Type: URL(255)

  • Description: Optional URL used in the Event thumbnail image in Event Groups. The recommended aspect ratio is 2:1

• Field Label: Thumbnail Image Name

  • API Name: conference360__Thumbnail_Image_Name__c

  • Data Type: Text(100)

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.