March 2024 - Version 4.20

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

Off-Cycle Releases

March 20, 2024

The Base package Contact Trigger (bt_base__ContactTrigger) feature is still in development and has been turned off until a feature-flagged toggle can be added. This update will not impact existing functionality. Users can now delete Contact records without causing a permissions-related error.

March 15, 2024

This hotfix improves SEO for Event pages by aligning with SEO best practices. The Events app now sets the “title” and "canonical title" values in the HTML of the Event pages. Those values are set according to the Account name of the customer organization, with the default Blackthorn.io values used as a fallback.

March 8, 2024

Form field values will now map correctly to custom fields on custom objects, including Blackthorn objects. Previously, a Form field’s picklist value would not map to a custom field on the Attendee object. (Known Issue: 000003345)

March 6, 2024 - Version 4.19.1

This hotfix is part of our continuing effort to address issues our customers are experiencing with events failing to appear consistently within event groups.

What This Hotfix Does
When the cache is overloaded, a cache update (referred to as cache invalidation) can fail, preventing the event group from showing all relevant events. This hotfix reduces overload by lowering the number of connections to the cache by grouping event IDs within the event group.

What This Hotfix Does Not Do
This hotfix does not prevent incomplete events from being displayed. Although this hotfix is an improvement, it does not prevent all scenarios where missing events can occur. However, it does introduce improvements that should minimize the rate of occurrence.

Next Steps
We continue to work on additional underlying issues that can cause events to disappear from the event group and will release any fixes as soon as they are ready. In addition, we are working on a larger, more permanent caching solution to be included in a future release.

BT Salesforce Release

Bug Fixes

• When a user imports a report with Accounts and Contacts from the Attendee tab on an Event, only the first 2000 rows/Attendees will be added to the Event. Salesforce has a limit of 2000 rows. You must use a Data Loader to import more than 2000 Attendees. (Known Issue: 000003110)
• Events users can now send emails from the Smart Scheduler. Blackthorn Base version 1.23 and Events version 4.14.1 are required. Previously, emails could not be sent. (Known Issue: 000003284)
  • NOTE: There is a known issue with sending scheduled emails. The scheduled time is currently being offset by 2 hours. This issue is now under review.
• The Enable Accessibility field (conference360__Enable_Accessibility__c) on the Blackthorn | Events Settings custom setting has been deprecated. To disable the accessibility widget, please contact Blackthorn Support. (Known Issue: 000003263)

Experience Cloud

• Community users will no longer get Blackthorn Log errors when registering Attendees via the Experience Cloud. The Attendees will be registered, and the Remaining Capacity will be updated accordingly. Previously, community users with site Payment and Event licenses and the Blackthorn | Events (Community/Platform User) / Blackthorn | Payments (Community/Platform User) permission sets received Blackthorn Log errors. (Known Issue: 000003190)

Attendees

• An Attendee can successfully register for Events with the same Event Name without triggering Blackthorn Logs and an ERS failure. This fixes a known Salesforce issue that resulted in Blackthorn Logs and failed ERS attempts. (Known Issue: 000003276)
• When the Campaign field is defined on an Event record, and an Attendee registers for the Event, the Attendee will be added to the Campaign as a Campaign Member. Previously, the Campaign Member record wasn't created, and a Blackthorn Log with the following error was created. "Exception Type = System.DmlException Full Error Message = Insert failed. First exception on row 1; first error: REQUIRED_FIELD_MISSING, Attempted to add a campaign member where either the member id 'null' or the campaign id '7014R0000013waM' is null.: []". (Known Issue: 000003250)

Enhancements

• Event organizers using the Event Wizard or Event Builder can now use the Contact lookup field to populate the Speaker record with the Contact record’s data. The Speaker record will include the Image URL and alternative help text for the image. Previously, the Speaker record was added without automatically copying the Image URL and alternative help text.
  • Note: Images uploaded via the Event Builder will only be added to the Speaker record. If there is an existing, related Contact record, the Speaker’s Image URL must be added manually to the existing Contact record.
• The Deep Clone Layout on Events now includes the following fields: Confirmation Email, Waitlisted Email, and Waitlisted Pending Email. Previously, only the Email Template Related List was cloned. (Known Issue: 000003178)
  • New installations will include the fields on the Deep Clone Layout; however, existing customers must manually add the fields. Follow the steps below to add the custom fields to the Event Deep Clone Layout.
    1. Click the Gear icon.
    2. Click Setup.
    3. Click the Object Manager tab.
    4. In the Quick Find box, enter and click "Event" (conference360__Event__c).
    5. Click the Field Sets tab.
    6. Click “Deep Clone Layout."
    7. Drag and drop the following fields in the "In the Field Set" list.
       1. Confirmation Email (conference360__Confirmation_Email__c)
       2. Waitlisted Email (conference360__Waitlisted_Email__c)
       3. Waitlisted Pending Email (conference360__Waitlisted_Pending_Email__c)
    8. To make a field required, hover over the field in the "In the Field Set" box, click the Wrench icon, and check the Required checkbox.
    9. Click OK.
    10. Click Save.

Experience Cloud

• Experience Cloud users can preview their Event before publishing it by using the BT Events Preview component. Users can also register Attendees from the BT Events Preview component.
• The Event Builder is now available in the Experience Cloud. Users can create a tab on their Experience Site and add the Event Builder component. Experience Cloud users can then create, edit, and clone Events.
• Experience Cloud users with the Blackthorn | Events (Community/Platform User) permission set can add Form Elements to Forms they created in the Experience Cloud. They can also view Forms created by other users in Experience Cloud, but they cannot add Form Elements to Forms created by other users.
• Additional headers will no longer be created when a user edits and saves a Form Element question from the Form Element edit component.
• Experience Cloud Event organizers can now use the iframe preview feature in Experience Cloud to preview an Event page.

Webapp Release

Bug Fixes

• If a user has view access for an Event, they can use the Preview button regardless of the Visibility Control setting on the Event. Previously, the user received the following error after clicking Preview. “You do not have access to this event (Error: 2001).” (Known Issue: 000002964)
• When a discount Code is applied to an Event or Event Item, only one draft Event Registration Submission (ERS) record will be created during registration. Previously, multiple draft ERS records were created during the different stages of the checkout process. (Known Issue: 000003014)
• When the /{orgId}/share/events/{eventId} is pasted to Facebook/Twitter/Slack, it will pull the value from the primary URL and render the image, title, and short description correctly. Previously, the information was pulled from the tag, resulting in incorrect information.
• When using the Dynamic or Tabbed UI, the Order Summary will display $0.00 for the following scenarios: if the Tickets/Sessions are free, a 100% coupon is applied, and the total amount due is zero. Previously, the Order Summary did not display an amount for any of the previous scenarios.

User Interface

• When the Event Settings’ Currency Display field is set to “ISO”, the ISO currency formatting will be applied to all currency displays in the Dynamic UI. Previously, the currency was displayed inconsistently.
• When an Event has a free Main event ticket (Event Item) and a Donation (Event Item) and the User Experience = “Dynamic”, an Attendee will see the donation amount (Price) in the order summary and Invoice Line Items. Previously, the donation amount wasn’t always shown.
• When using the Tabbed UI, Session image proportions will be identical on the Sessions tab and during Session registration. Previously, Session images appeared normal on the Sessions tab but were distorted during registration.
• The footer will be visible when an Event with the Dynamic UI is viewed on a mobile device. Previously, custom URLs were not visible at the bottom of the landing page.
• When using Google Translations to translate an Event with the Simple UI, the alignment of the Event Item Name will appear as expected. Previously, changing the language caused the Event Item Name alignment to shift and the text to overflow.

Enhancement

• Additional updates were made to the Simple and Tabbed user interfaces to improve keyboard accessibility. Users can tab to the Event name, location, date/time, and description when using a screen reader.

Field Update

Removed

• The Enable Accessibility field (conference360__Enable_Accessibility__c) on the Blackthorn | Events Settings custom setting has been deprecated. To disable the accessibility widget, please contact Blackthorn Support. (Known Issue: 000003263)

Base Package

Enhancements

• The Smart Scheduler (Blackthorn Base package) was added to the Blackthorn Candy Shop. Messaging customers can now use Smart Scheduler without downloading the Events or Storefront apps.

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 about this or need help with testing, please don't hesitate to reach out to Blackthorn Support.