May 2024 - Version 4.24

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

Breaking Change

Zoom Users

The Zoom Registration Approval Type field was added to the Event object in response to Zoom's update on April 22, 2024. This field will enforce the approval type as a required value. If you do not want to enforce registration, no action is required. Previously, Zoom meetings generated during Event creation required a guest to authenticate to join the meeting. (Known Issue: 000003320)

• Field Label: Zoom Registration Approval Type
• API Name: Zoom_Registration_Approval_Type__c
• Data Type: Picklist
• Description: Use this field to define the type of approval a meeting registration requires. The three types of approval are “No registration required” (default setting), “Manually approve registration,” or “Automatically approve registration.” The default setting is “No registration required.”

The Zoom Registration Approval Type field is not automatically added to the Event page layout. Click here for detailed steps to add the field and set a value to auto-approve / manually approve registrations.

BT Salesforce Release

Bug Fixes

• Merge Tags in the Email Template Builder work correctly when the Salesforce user’s Language is set to "German". Previously, the Merge tags weren't visible in the Email Template Builder. (Known Issue: 000003303)
• When the Relationship Settings’ Contact Account Rule field is set to “Bucket Account,” a new Contact record without a matching Account will be added to the “Bucket Account.” Previously, the Account matching rules incorrectly added the new Contact record to the “Basic Bucket” Account.
• Only one active Event will be created at a time for Recurring Events when Recurrence Method = “Keep One Open”. The following updates were also made. Previously, the Blackthorn | Events Recurring Event Generate batch job created multiple active Events when the Recurrence Method was set to “Keep One Open”. (Known Issue: 000003121)
  • The Recurring Events logic will now use the Event Status instead of the Event End Date to determine if an Event is active.
  • The Recurring Event Active Event Validation flag, which is turned off by default, was added to the Blackthorn | Events Settings custom setting.
  • When Recurring Event Active Event Validation is enabled and Recurrence Method = “Recurring”, new Events will not be created until the count of active Events is less than the value in the Count field.
• The Clone button (Lightning Action) was added to the Form page layout to give users an easy way to clone Forms. Previously, cloning Forms with the Data Wizard caused Events to experience 2004/2006 errors. (Known Issue: 000003356)

Experience Cloud

• When a logged-in guest user registers additional Attendees via the Experience Cloud and Express Registration is enabled, the newly created Attendee records will respect the relationship settings related to the Event. Previously, the additional Attendee records did not respect the relationship settings and were associated with the logged-in user's Contact record. (Known Issue: 000002803)
• When a Community User updates the Attendee data (registration statuses) from the Experience Cloud Site, the changes will be reflected in the Event’s totals (Attendance Summaries). Previously, modifying Attendee registration data did not update the Event’s Attendance Summaries because of missing permissions. (Known Issue: 000003138)

UI Experience

• When a user edits an existing Event in the Event Builder, the UI Experience value remains the same as it was before the user edited the Event. Previously, the Event’s UI Experience value automatically changed to “Dynamic.”
• When an Event’s UI Experience is set to “Dynamic,” the Total Amount due during checkout will be shown after a user selects a Ticket. Previously, the Total Amount wasn’t visible.
• When a user edits an existing Event in the Event Builder, the UI Experience value remains the same as before editing the Event. Previously, the Event’s UI Experience value automatically changed to “Dynamic.”

Enhancements

• The duration of the Event Builder load times has been decreased. Users will also see a spinner to indicate that the component is loading.
• Updates were made to handle Translations more efficiently, improve error handling, and prevent the Events app from crashing. Previously, an issue caused a 2003 Translation Error, which caused the Events app to crash when Translations exceeded the provisioned limits for Google Translate API.

Fees - Tax/GST

The new fields on the Event, Event Item, and Event Item Session objects are part of the ongoing development of the Tax/GST feature. This update is related to the foundational development of the feature and is not functional.

• The Payments app will now include the Event’s Tax Fee and Event Item’s Tax-Exempt fields in the Invoice/Transaction processing.
• The following updates were made to the Event and Event Item objects to support the use of taxes.
  • Event Object
    • Field Label: Tax Fee Calculation Type
      • API Name: conference360__Tax_Fee_Calculation_Type__c
      • Data Type: Text(100)
      • Description: Defines whether the Tax is inclusive or calculated at checkout. It is determined by the associated Fee Tax Display Setting field.
  • Event Item Object
    • Field Label: Tax Amount
      • API Name: conference360__Tax_Amount__c
      • Data Type: Number(16, 2)
      • Description: Calculated as a percentage of the Price based on the associated Fee.
    • Field Label: Price with Tax
      • API Name: conference360__Price_with_Tax__c
      • Data Type: Number(16, 2)
      • Description: Line item Price plus Tax
• The following updates were made to the Event Item Session object.
  • Field Label: Tax Amount
    • API Name: conference360__Tax_Amount__c
    • Data Type: Number(16, 2)
    • Description: The Tax Amount is calculated as a percentage of the Event Item Session’s Price based on the associated Fee. It is also equal to the related Line Item’s Tax amount.
  • Field Label: Price with Tax
    • API Name: conference360__Price_With_Tax__c
    • Data Type: Number(16, 2)
    • Description: The Price with Tax equals the Line Item’s Price plus the Event Item Session’s Tax Amount.
  • Field Label: Tax Rate
    • API Name: conference360__Tax_Rate__c
    • Data Type: Percent(15, 3)
    • Description: The Tax Rate for the Event Item Session is set automatically based on the Event’s Tax Fee lookup.

Experience Cloud

• The Builder button is now available on the Event record detail page in the Experience Cloud.
• When using Event components in the Experience Cloud, Community Profile users can access Attendee Reports and will no longer experience re-directing issues. Please note that users need access to the Blackthorn | Events Reports folder to use the Lightning Quick Actions for different reports.
• The Event Builder tab is now available on the Events app. To launch the Event Wizard, go to a specific Event record and click the Event Wizard Lightning Action Button.
• The following updates were made to resolve doubleheader and redirect issues in the Blackthorn Events Components in Experience Cloud.
  • The Form Edit component will automatically launch from the Lightning Action.
  • The Form Edit component behaves as expected when used in the Experience Cloud.

Webapp Release

Bug Fixes

• The country shown on the Payment Info page will be the same as the country selected on the Attendee Info page. Previously, the country shown differed from the country chosen because of a difference in the country picklists on the Attendee Info and Payment Info pages. (This only occurred with country names between Cyprus and Gambia.)
• The utm_source value will be relayed properly using a translated Event registration page with tracking (UTM) parameters. UTM Parameters, including utm_source, are used in URLs and help with app analytics/user tracking for conversions. Previously, the utm_source value was blank for the Attendees. (Known Issue: 000003527)
• Updates were made to handle Translations more efficiently, improve error handling, and prevent the Events app from crashing. Previously, an issue caused a 2003 Translation Error, which caused the Events app to crash when Translations exceeded the provisioned limits for Google Translate API.
• When the Cancel Registration button is enabled on the Event Settings record, the button will be visible on the AttendeeLink whether or not the Event is part of an Event Group. Previously, when a user tried to cancel their registration, and the Event was related to an Event Group, the Cancel Registration button was not visible on the AttendeeLink. (Known Issue: 000003331)
• Attendees can now click the Add to Calendar button and select Office 365 to download the ICS file on the post-registration page. Previously, after an Attendee selected Office 365, the ICS file didn’t download, preventing them from adding the Event information to their calendar. (Known Issues: 000002926 and 000002941)
• When an Event’s Webinar/Meeting URL field includes a YouTube Live Stream URL, Attendees can now access the live stream by clicking the Join Video Stream button. Previously, the Attendee was shown a black screen and could not access the meeting. (Known Issue: 000003436)
  • Important Note: The YouTube Live Stream URL must be in the following format: “http://www.youtube.com/live/[live stream id]”.
• If an Attendee clicks the Register button from their AttendeeLink but decides to change their RSVP and goes back to the main page, the RSVP banner will be visible. Previously, the RSVP disappeared when the Attendee returned to the main page to decline the invitation. (Known Issue: 000003481)
• Users can now download PDF Event Content files using a Google Chrome browser. Previously, users were unable to do so. (Known Issue: 000003248)
• Users will see an updated error message with additional information if they enter an incorrect zip code/postal code during checkout. (Known Issue: 000003446)
  • Original Error Message: “Warning: Checkout failed, please try again later.”
  • Updated Error Message: “Warning: Checkout failed: Incorrect zip/postal code.”

Donations

• The Price for Event Items with Type = “Donation” (Donation) now accurately reflects the amounts specified in Salesforce, and Donations marked as free will display "Free" during registration/checkout. Previously, Donation amounts were shown as $0.00 in the cart when the Donation was marked as free.
• Modifying the Price for Event Items with Type = “Donation” (Donation) during registration will now correctly update the Donation amount in the cart. Previously, modifying the Donation amount did not trigger an update to the cart, even though subtotal/total amounts were calculated correctly.

Event Settings

• If the Events Settings Allow Edits to Attendee fields field is unchecked, Attendees won't be able to edit the Attendee details on a "one-page checkout" Event for the following UIs: Simple, Full-Width with one ticket, Dynamic Simple for both BT Event Listing in a Community + AttendeeLink. Previously, there was an issue with "one-page checkout" Events in the Community. Attendees could update their details during checkout even when Allow Edits to Attendee fields was unchecked. (Known Issue: 000003644)
• The following updates were made to the Event Settings’ footer content. Previously, the fields accepted domain paths even though they didn’t work, and custom labels were shown when the corresponding URL field was empty. (Known Issue: 000003379)
  • The following fields do not take domain paths; only domains (e.g., www . google . com) will work.
    • Custom URL 1
    • Custom URL 2
    • Custom URL 3
    • Custom URL 4
  • Custom labels will not show if the corresponding URL field is empty.

UI Experience

• When an Event using the Dynamic UI has two Event Items, an Attendee can use their AttendeeLink to select both Event Items and register for the Event. Previously, after an Attendee selected the second Event Item, it disappeared from the cart. (Known Issue: 000003390)
• Event and Event Item names written in right-to-left languages will now be displayed correctly on Event webpages. Previously, the names would break in the middle of a word or be cut off in Simple, Tabbed, Full-Width, and Dynamic UIs.

Field Updates

New

• Object: Event
  • Field Label: Zoom Registration Approval Type
    • API Name: Zoom_Registration_Approval_Type__c
    • Data Type: Picklist
    • Description: Use this field to define the type of approval a meeting registration requires. The three types of approval are “No registration required” (default setting), “Manually approve registration,” or “Automatically approve registration.” The default setting is “No registration required.”
  • Field Label: Tax Fee Calculation Type
    • API Name: conference360__Tax_Fee_Calculation_Type__c
    • Data Type: Text(100)
    • Description: Defines whether the Tax is inclusive or calculated at checkout. It is determined by the associated Fee Tax Display Setting field.
• Object: Event Item
  • Field Label: Tax Amount
    • API Name: conference360__Tax_Amount__c
    • Data Type: Number(16, 2)
    • Description: Calculated as a percentage of the Price based on the associated Fee.
  • Field Label: Price with Tax
    • API Name: conference360__Price_with_Tax__c
    • Data Type: Number(16, 2)
    • Description: Line item Price plus Tax
• Object: Event Item Session
  • Field Label: Tax Amount
    • API Name: conference360__Tax_Amount__c
    • Data Type: Number(16, 2)
    • Description: The Tax Amount is calculated as a percentage of the Event Item Session’s Price based on the associated Fee. It is also equal to the related Line Item’s Tax amount.
  • Field Label: Price with Tax
    • API Name: conference360__Price_With_Tax__c
    • Data Type: Number(16, 2)
    • Description: The Price with Tax equals the Line Item’s Price plus the Event Item Session’s Tax Amount.
  • Field Label: Tax Rate
    • API Name: conference360__Tax_Rate__c
    • Data Type: Percent(15, 3)
    • Description: The Tax Rate for the Event Item Session is set automatically based on the Event’s Tax Fee lookup.

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

If you have any questions or need help with testing, please contact Blackthorn Support.