October 2024 - Version 4.36

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

Table of Contents

• Breaking Changes
• BT Salesforce Release
• Webapp Release
• Field/Layout Updates
• Upgrade Instructions
• Important Definitions

Breaking Changes

Pre-Checkout Details and Ticket Selection

This update is a potential breaking change for those using a workaround to solve this issue. Pre-checkout details will now appear during Ticket selection, and checkout details will appear on the Contact Information/Payment screen. Previously, pre-checkout details and checkout details were swapped, causing problems when completing the registration process. (Known Issue: 000003851)

Google Tag Manager Default Behavior

The August 2024 release changed the Google Tag Manager’s default behavior. By default, Google Analytics cookies will only be collected when the Cookies Consent Banner is enabled. Previously, analytics were collected when the banner was disabled. (Known Issue: 000003814) 

For customers who have not enabled the cookie consent banner, tracking was mistakenly disabled as of August 27th. 

If you wish to re-enable tracking, please contact Blackthorn Support. We will be happy to assist you by enabling the cookie consent banner. Please include your org ID and desired configuration. 

BT Salesforce Release

Important Note

Blackthorn customers will not be impacted by the most recent Authorize.net change. Recently, Authorize.net contacted many of their customers to let them know they are updating their SSL/TLS certificates. Based on information provided by Authorize.net, Blackthorn products will not be affected by this change.

Bug Fixes

• Attendee: When an Attendee registers for an Event from the Event Registration Page Form (Event Page URL), the Attendee’s Source field will be set to “Web App.” Previously, the Attendee Source field was left blank. (Known Issue: 000003921)
• Zoom Meetings: Users can now create Events with Zoom meetings without seeing unclear Blackthorn Log errors. Previously, the Event object’s new Zoom Registration Approval Type field triggered Blackthorn log errors, which led to potential disruptions in the Event setup process. (Known Issue: 000003777)
• Emails: Permissions for org-wide email addresses will be respected, ensuring users can only see the org-wide email addresses they have access to, and no one can see unverified email addresses. Previously, the following occurred.
  • Users could send emails from an unverified address.
  • Users could see all org-wide email addresses, including those they didn’t have access to.
  • No error was shown on the front end when users tried to send an email even though the email was blocked, and a Blackthorn Log was created. (Known Issue: 000002988)
• Relationship Settings: When an Attendee who doesn’t have an existing Account record registers for an Event, a single Lead record will be created and related to the Attendee record. Previously, when Relationship Settings had Relationship Rule = "Create a New Record if No Match" and Match Records = “Account,” duplicate Lead records were created. (Known Issue: 000003459)
• Smart Scheduler: When using the Smart Scheduler with an Event to send scheduled emails, the Smart Scheduler will send messages to Attendees whether the Publish checkbox is checked or the Publish button is clicked. Previously, users could only use the Publish checkbox to send emails. (Known Issue: 000003948)
• Experience Cloud: When using the Experience Cloud with the BT Events Listing component, users can set the Event Group’s UI Experience to “Aspen,” “Maple,” “List,” or “Calendar.” This update allows users to overwrite the Event Group record’s UI Experience and create multiple experiences for the same Event Group in the Experience Cloud. Previously, selecting “Aspen” or “Maple” in the Experience Cloud did not change the user interface.
• Table Manager: When using the Table Manager component, the Attendee cards will appear as follows, fixing alignment issues with the Attendee cards.
  • There will be consistent padding on the right and left sides.
  • The names on the Attendee card list will be aligned with the center.
  • The Attendee's name will be fully visible when the screen resolution changes.
• Waitlisting: Event Organizers can select waitlist-enabled Tickets and register Attendees for an Event using the Attendee Registration component. Previously, waitlist-enabled Tickets were grayed out even though waitlisting was enabled for the Event, preventing Attendees from being registered. (Known Issue: 000003794)
• Currency: When an Event Organizer uses the Event Wizard or Event Builder to change the currency for an Event, they will see the new currency in the Wizard/Builder, the Event preview, and the published Event. Previously, the user saw the original currency for Event Items with Type = “Donation” in the Builder/Wizard even though a new currency was selected. (Known Issue: 000003945)
• Event Settings: The Remove URL from Attendee Links field was added to the Event Settings object to allow users to show or hide the Join Video Stream button to Attendees on the AttendeeLink page when the value in the Event’s Webinar/Meeting ID or Webinar/Meeting Account field is removed. Previously, existing Attendees saw the Join Video Stream button on their AttendeeLink page even though the value in the Webinar/Meeting ID or Webinar/Meeting Account field was removed. (Known Issue: 000003867)
  • Object: Event Settings
  • Field Label: Remove URL from Attendee Links
  • Data Type: Picklist
    • "No": The existing behavior will continue.
    • "Yes": When the value in the Webinar/Meeting ID or Webinar/Meeting Account field is deleted, the information in the Attendee’s Webinar/Meeting Join URL field (Join Video Stream button) will be removed.
  • Help Text/Description: When enabled, the Attendee’s Webinar/Meeting Join URL field (Join Video Stream button) will be deleted when the Event’s Webinar/Meeting ID or Webinar/Meeting Account field is cleared.
• Attendee Duplicate Rule: If the Attendee Duplicate Rule’s Action on Create is set to “Block,” an Attendee can register multiple people at one time and can register via the Event Page URL instead of their AttendeeLink. Previously, Attendees couldn’t perform either action. (Known Issue: 000004041)

Clone Events

• Event Organizers can now clone an Event using the Clone button on an existing Event record. Previously, clicking Clone resulted in the following error. "Uncaught Action failed: conference360:EventDeepCloneselectAll [Cannot read properties of undefined (reading 'length')]" (Known Issue: 000003679)
• If a user clones a Parent Event with an Event Item selected but not the Session, the Child Event will only include the cloned Event Item. Previously, the newly created Event Item also had a new Event Item Session, and when Attendees tried to register for the Child Event, they saw the Parent Event's Sessions. (Known Issue: 000003469)

Event Builder

• The color of the help text next to the Save & Publish Later and Save & Publish Now buttons on the Event Builder has been changed to white to help meet accessibility guidelines. Previously, the help text was red with a dark blue background, making it difficult to read. (Known Issue: 000003775)
• In the Event Builder, several different links are attached to the sentence, “To customize fields in this section, click here.” When users click each link, the URL will take them to the associated field set on the corresponding object. Previously, users got a “Page doesn’t exist” error. (Known Issue: 000002805)

Event Items

• If picklists for address fields are enabled in Setup > State and Country/Territory Picklists and a user creates an Event Item with Address = “Required” and Country = “Hidden,” the user will see the updated error message. “Country is a required field when state and country picklists (Setup > State and Country/Territory Picklists) are enabled.” Previously, the error message did not clearly explain the problem. (Known Issue: 000003879)
• The Pending Capacity field was added to the Event Item object and the Quantity Remainingcalculation to improve the accuracy of the Event Item’s available capacity.
  • The new formula is Quantity Remaining = Quantity Available - (Registered + Pending Capacity). (The previous formula was Quantity Remaining = Quantity Available - Registered.)
  • Object: Event Item
    • Field Label: Pending Capacity
    • API Name: conference360__Pending_Capacity__c
    • Data Type: Number
    • Description: This field stores the pending capacity of Event Items. This is automatically calculated. Do not update the field manually.

Enhancements

• Event Items: The Default Quantity Selection field was added to the Event Item object. Event Organizers will be able to use the new Default Quantity Selectionfield to set a Ticket’s default quantity. This update is related to the foundational development of the feature and is not functional.
  • 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.
• Email Components: The CSS styles were updated to ensure the spacing between the input fields in the Send Email component matches the spacing of fields in the Email Configuration component.
• Experience Cloud: Replaced the existing New Form Element (New_FE_Beta) and Form Preview (Form_Preview) buttons in the Experience Cloud with new LWC buttons, Form Preview (Form_Preview_Aura) and New Form Element (New_Form_Element_Aura), to prevent duplicate headers from being created after a user updates the Form Element record. (Known Issue: 000003682)
• Accessibility: Default values were added to the Sponsor’s Alternative Text for Visual Impairment and Speaker’s Alternative Text for Visual Impairmentfields to save time during Event creation. Note: Default values can be overwritten.
  • Sponsor: Alternative Text for Visual Impairment = “[Sponsor Display Name] logo"
  • Speaker: Alternative Text for Visual Impairment = "Portrait of [Contact First Name] [Contact Last Name]"
• Event Object: 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. This field is not yet functional.
  • 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: conference360__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.
• Event Settings: When an Attendee registers a group, they can now click the Copy related info to all the responses button to copy their Form responses to all Attendees in the group if the new Allow Form Responses for Attendee Groupfield is set to "Yes." The new field removes the repeated copy-paste step and decreases the time it takes to register everyone.
  • Setting the Allow Form Responses for Attendee Group field to “Yes” makes the Copy info to all responses button visible when filling out a Form for an Attendee Group.
  • Object_ Event Settings
    • Field Label: Allow Form Responses for Attendee Group
    • API Name: conference360__Allow_Form_Responses_for_Attendee_Group__c
    • Data Type: Picklist
      • Picklist values: Yes, No, and None
      • Default value: None
    • Help text: “When a registration includes multiple Attendees, the user can expedite registration by copying the first Attendee’s responses to form questions to all other attendees. Does not copy contact info.”
    • Please Note:
      • The Forms must be identical and have the same Form record ID.
      • The Copy related info to all the responses button will only be displayed if the first Event Item shown has custom questions.

Event Builder

• Alignment issues on the Speaker page in the Event Builder were fixed. Each Speaker’s image (Image URL) and name (First Name and Last Name) are now vertically aligned.
• If a user clicks Event Builder while in an Event record and, in the Event Builder, moves between the Begin from Scratch and Clone an Event options before going back to Edit Existing Event, the original Event’s data will still be there. Previously, the original Event’s data was no longer visible when the user clicked Edit Existing Event, causing confusion.

Webapp Release

Bug Fixes

• Stripe Checkout: When an Attendee registers for an Event using Stripe Checkout, the Event Registration Submission (ERS) record’s Status will be set to “Completed,” and the related Invoice and Attendee records will be created. Previously, if an Attendee closed their browser window before the screen could redirect back to the completion page, there were intermittent issues where the ERS record was left in draft status, and the completed Transaction didn’t have related Invoice and Attendee records. (Known Issue: 000003916)
• Form Elements: When a Form Element includes information in the Supplemental Question Information field, the Attendee will see that the Form Element’s Question has been bolded to help it stand out more. Previously, the Supplemental Question Information field’s text stood out more than the Form Element’s Question when using the Dynamic UI. (Known Issue: 000003742)
• Caching: If an Event’s UI Experience = “Tabbed,” registered Attendees will appear on the Event webpage’s Attendees tab. Previously, Attendees were not visible due to a cache setting, which caused a delay in the page’s updating. (Known Issue: 000003502)
• Social Media: The robots.txt on Event webpages was updated to ensure that social media previews are displayed correctly on Facebook. Recent Facebook updates caused the social share URLs with previews to stop working.
• Event Settings: If an Event’s UI Experience is set to “Dynamic” or “Full-Width,” the Primary Color (#) and Background Color (#) configured in the Event Settings record will appear as expected on the Event webpage. Previously, the Primary Color (#) and Background Color (#) were switched. (Known Issues: 000003956 and 000003646)
• Caching 2.0: If Caching 2.0 is enabled and an Attendee clicks a keyword on an Event Group webpage, they will now see the Keyword’s Keyword in the URL. Previously, Attendees saw the Keyword record’s ID instead of the actual keyword. (Known Issue: 000004010)
• Fees/GST: When using the Data Dictionary with DocumentLink, users will see the value in the Invoice’s Dynamic Fee Name field replace the Line Item row label for "Tax." Previously, the Line Item row label for "Tax" did not display the Dynamic Fee Name value, even though the Dynamic Fee Name value replaced “Tax in the totals section.
• Big List Options: When using an iOS or Android smartphone to register for an Event, the picklist options in a Big List Group will appear as expected on the registration form. Previously, picklist values were cut off. (Known Issue: 000003424)

Checkout

• If an Event has a free Event Item with Type = “Main event ticket” and one or more paid Event Items with Type = “Other,” the pricing summary will show the total amount due. Previously, the amount due wasn’t shown in the Summary section during checkout, causing confusion about the cost. (Known Issue: 000003480)
• On the Sessions tab, Attendees can now click the ALL tab or a specific date to see other Sessions when the Event’s UI Experience = “Tabbed .” Previously, nothing happened when an Attendee clicked the tab. (Known Issue: 000003923)
• If an Attendee only selects free Tickets when registering for an Event, they will see the heading Additional Information on the contact information screen. Previously, Attendees saw “How do you want to pay?” even though the Tickets were free. (Known Issue: 000003873)
• If an Event offers a free Ticket, a paid Ticket, and a discount Code, Attendees can add the free Ticket, discount Code, and paid Ticket – in that order – and the total cart value and discount amount will display correctly. Previously, the total cart value and discount amount were displayed incorrectly.
• When an Attendee clicks the Sessions tab when viewing an Event using UI Experience = “Tabbed and then clicks the back arrow to return to the Sessions tab page, they will return to the Sessions tab page. Previously, clicking the back arrow took the Attendee to the Event’s homepage. (Known Issue: 000003926)
• If an Attendee registers for a free Event with paid Sessions, the cost for each Session and the total amount due will be visible on the Summary page. Previously, neither the individual Session cost nor the total amount due appeared, causing confusion. (Known Issue: 000003545)
• If an Attendee registers for an Event with a smartphone and applies a discount Code to their cart, the adjusted price will be visible at the bottom of the screen (the amount next to the Register button). Previously, the amount displayed at the bottom of the screen was the full price of the Ticket instead of the adjusted price.
• When an Attendee views an Event with UI Experience set to “Dynamic” or “Tabbed,” they will see the location pin/map icon in its entirety. Previously, the icon was cropped by surrounding text or elements. (Known Issue: 000003939)
• If an Attendee tries to register for an Event with UI Experience = “Dynamic” and the Event has Remaining Capacity = “0” and Waitlist Enabled = “True” (checked), the Attendee will see the Join Waitlist button instead of the Register button. (Known Issue: 000003781)

Error Messages

• API error messages are now relayed more accurately, improving error handling for Event webpages. In addition, an error scenario caused by Attendees registering for an Event twice in a row has been resolved. Previously, registering for the same Event twice in a row resulted in the second registration failing.
• If the Event Settings One Unique Attendee Email Per Event is enabled and an Attendee tries to register with an email already in use, they will see the following error message: “Duplicate email registration not allowed." Previously, the Attendee saw "Registration failed; please try again later."

Event Object

• If an Event in an Event Group has an Event End Date set to today’s date and the Event End Time is in the past, the Event will no longer be visible on the Event Group’s webpage. If the current time is between the Event Start Time and Event End Time, the Event will be marked as “Upcoming.” This logic was updated to respect the current user’s locale/time zone. Previously, completed Events still had an "Upcoming" banner. (Known Issue: 000004008)
• When an Event has UI Experience = Dynamic,” the text in the Description field will appear as expected. Previously, text in a large font size resulted in overlapping text.

User Interface (UI)

• If an Event has UI Experience = “Dynamic,” Session images will scale correctly during checkout if the Session Description field is empty. Previously, the image was not responsive, which caused it to overflow its container.
• An Event’s images will now use the correct proxy (media.blackthorn.io) when displayed on the Event webpage. Additionally, the user interface was updated, including adding a fallback image for Session Speakers. Previously, images did not use the correct proxy, causing issues with the user experience.
• When an Attendee clicks Add to Calendar to add a Session to their calendar, the Session link in the calendar entry takes them to the Session webpage. Previously, clicking the link took the Attendee to a blank page when the Event’s UI Experience = “Dynamic.” And when the Attendee refreshed the blank page, they were redirected to the Event Group webpage instead of the specific Session webpage.

Enhancements

• Contact Us: A CAPTCHA challenge was added to the Contact Us form to reduce spam emails and deter automated submissions sent via the Contact Us component on an Event. (Known Issue: 000003866)
• Events App: Unused cookies were removed from the Events webapp.
• Caching 2.0: For Caching 2.0, the loading performance during checkout of a Form Big List Group with a large number of related Form Big List Options has been improved.

Accessibility

• If an Attendee uses a visual or screen reader and selects “Pay Later” during checkout for a paid Event, they will receive a notification that the payment fields have been cleared.
• During checkout for paid Events, Attendees now have complete control over navigating between fields, especially when entering credit card information. This update ensures the focus remains in the same field and improves accessibility as screen readers can now read the information.
• If an Attendee uses a screen reader to view an Event Group with UI Experience = “Calendar,” they can navigate the dates and Events with the screen reader. The screen reader will announce each date and Event and interact with it as a link according to WCAG standards.
• Screen readers will announce the active month when Attendees click the "Previous Month" and "Next Month" buttons when an Event Group has UI Experience = “Calendar.”

Checkout

• Attendees accessing an Event from their AttendeeLink can either click the Redeem Item button or use the quantity selector to add a Ticket to the cart for themselves. (Known Issue: 000003219)
• The primary action button (Register, Continue, Review Sessions, Pay, etc.) has been moved to the bottom of the page to improve accessibility during checkout. The button will remain visible as Attendees scroll through the options on the page, preventing Attendees from having to scroll to find the button to move to the next step.
• Enhance the Event registration experience by using the Event Settings’ Allow Form Responses for Attendee Group field to allow the first Attendee to copy their question responses to all other Attendees with the click of the Copy related info to all the responses button. Please Note:
  • The Forms must be identical and have the same Form record ID.
  • The Copy related info to all the responses button will only be displayed if the first Event Item shown has custom questions.

Field/Layout Updates

New

Object: Event

• Field Label: Include Zoom URL In Calendar Description
  • API Name: conference360__Include_Zoom_URL_In_Calendar_Description__c
  • Data Type: Checkbox
  • Description/Help text: When enabled, the Zoom URL will be included in the invite’s Calendar Description field.

Object: Event Item

• Field Label: Pending Capacity
  • API Name: conference360__Pending_Capacity__c
  • Data Type: Number
  • Description: This field stores the pending capacity of Event Items. This is automatically calculated. Do not update the field manually.
• 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.
  • This field is related to the foundational development of the feature and is not functional.

Object: Event Settings

• Field Label: Remove URL from Attendee Links
  • Data Type: Picklist
  • Help Text/Description: When enabled, the Attendee’s Webinar/Meeting Join URL field (Join Video Stream button) will be deleted when the Event’s Webinar/Meeting URL field is cleared.
• Field Label: Allow Form Responses for Attendee Group
  • API Name: conference360__Allow_Form_Responses_for_Attendee_Group__c
  • Data Type: Picklist
  • Help text: “When a registration includes multiple attendees, the user can expedite registration by copying the first Attendee’s responses to form questions to all other attendees. Does not copy contact info.”

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.