August 2023 - Version 4.0

If you have any questions about the release note, please don't hesitate to reach out to Blackthorn Support.

New Feature: Credit Card Fees

New Object

• Name: Fee
• The Fee object is Read only for all Payments permission sets except for the Blackthorn | Payments (Admin) permission set.

New Fields

• Label: Fee Name
  • API Name: Name
  • Location: Fee object
• Label: Fee Percentage
  • API Name: Fee_Percentage__c
  • Location: Fee object
• Label: Default Fee
  • API Name: Default_Fee__c
  • Location: Fee object
• Label: Payment Processing Fee
  • API Name: Payment_Processing_Fee__c
  • Location: Event object

Functionality

• The Payment Processing Fee field is editable with any Blackthorn Events permission set except for the Read-only permission.
• Current Blackthorn users will need to manually add the Payment Processing Fee field to the Event record page layout.
• Event Admins can create a Fee record to store payment processing fee details and assign the Fee to an Event. If a Fee is assigned to an Event, the Fee will be added to the total amount when a credit card is selected as the Payment Method. Displaying the Fee Name during checkout is available with Tabbed, Full-width, Simple, BYO CSS, and Dynamic UI.
• A separate Line Item will be included on the Invoice for the credit card Fee.
• If a Payment Processing Fee is set as the default, it will automatically be linked to newly created Events.
• The Payment Processing Fee can be changed for each Event.
• Users who can edit the Event can also edit the Payment Processing Fee field.
• If a user does not have access to the Payment Processing Fee field, the field will be populated when a new Event is created if a default Fee has been defined.
• The Payment Processing Fee will only be applied when the Payment Method is a credit card.

How to Add a Fee to an Event Record

1. Click the Payment Processing Fee field on the Event record.
2. Search for and select an existing Fee. OR Click + New Fee.
3. Complete the following fields to create a new Fee.
   • Fee Name (required)
   • Fee Percentage (required)
   • Default Fee
4. Click Save & New or Save.

For more information about Fees, click here.

BT Salesforce Release

Bug Fixes

• When an Attendee registers for an Event with multiple Event Items using identical information for all Event Items, only one Campaign Member will be created with that information. Previously, no Campaign Members were created due to duplicate rules. (Known Issue: 000002582)
• When an Attendee makes a payment to a country other than the US for any type of Event Item, the currency will now be correctly recorded on the relevant Opportunity and/or Invoice. Previously, the correct amount was shown, but the currency matched the payer’s currency instead of the payee’s currency. (Known Issue: 000002800)
• The Event End Date/Time custom field on the Attendee object will now properly display the Event's Event End Date and Event End Time. Previously, an error caused the field to display the Event Start Date. (Known Issue: 000002793)
• Email Template Builder users can now view and adjust the builder’s settings. (Known Issue: 000002389)
• Users can now scan a list of Sessions and see the related Session Speakers in the Speakers field. Previously, a bug prevented the Speakers field from being populated. (Known Issue: 000002179)
• When an Event’s UI Experience = "Simple", users cannot add multiple Tickets, including Custom and Guest Tickets to the Event. Previously, this restriction was only enforced for Main Event Ticket types.
• Users will see that the Event Start Date, Event Start Time, Event End Date, and Event End Time fields will be displayed in a consistent format. For example: [Month abbreviation] [Day], [Year] [Time]. (Known Issue: 000002793)
• The automatically generated Zoom meeting Approval Type is now set to “Automatically Approve” instead of “Manually Approve.” This change was made to counter Zoom’s new default setting of “Manually Approve” which prevented Zoom links from being generated for Attendees. (Known Issue: 000002826)
• After installing Blackthorn Events and following the in-app guidance to create sample test data, an Events Admin will now see the sample dashboard populated with data. Previously, the dates on the sample data did not fall within the criteria of the reports within the dashboard, causing the dashboard to remain empty. NOTE: Additional improvements and bug fixes will be included in the next release.
• Attendees created using the BT Attendee Builder component on an Event record will have the Registration Status field automatically set to "To Invite". Previously, Attendees created via the Attendee Builder had a blank Registration Status field. This problem was confined to Attendees who were not added via Lead or Contact records. (Known Issue: 000002856)
• Guest users visiting a site hosted on the Experience Cloud can now see Blackthorn Events components. (Known Issue: 000002902)
• After a user creates a qualifying Event Item from the Event record, the Publish button will automatically appear. (A qualifying Event Item is any Type except “Donation” or “Guest”.)

Attendee Registration Component

• Users can now select Lead records from the Attendee Registration Component to create new Attendees. Previously, users could only select Accounts or Contacts.
• Users can now register Attendees for Events that include Forms with the Attendee Registration Component. Previously, Forms would be visible during registration, but they would cause an error in the Attendee Registration Component. (Known Issue: 000002782)

Clone an Event

• When a user clones an Event with Event Keywords, the existing Event Keywords will be properly related to the cloned Event. Previously, the original Event’s Event Keywords were moved to the new Event, altering the original Event.
• When a user clones an Event with Sessions and Session Keywords, the existing Session Keywords will be properly related to the cloned Event’s Sessions. Previously, the original Session Keywords were moved to the new Session(s), altering the original Event and Sessions.
• Clicking the Clone button on an Event record will successfully create a new Event record, even if an org includes a custom field with the same name as a Blackthorn field name. Previously, the automation would fail when two field names were the same. (Known Issue: 000002672)

Event Builder

• Using the new Event Builder to clone Event Items with Sessions now clones the Event Item Session Junction records. Previously, the Event Builder cloned Event Items and Sessions, but the junction between the Event Items and Sessions was not maintained in the cloned Event.
• When creating an Event with the Event Builder, users can now create new Attendees by selecting an existing Event with Attendees. A copy of each Attendee record from the existing Event will be created new Event.
• When a user selects Edit Existing Event, they will start editing the Event from the General Info section. Previously, selecting Edit Existing Event took the user to the Event’s Landing Page. Also, if the user returned to the General Info section, the page layout looked like they had clicked Start from Scratch.
• When a user clones an Event with a related Form using the Event Builder, the newly created Event will also be related to the Form. Previously, Events cloned via the Event Builder did not include the Form value.
• When using the Event Builder to create or edit an Event, users can now select an Account in the Venue field and see the Venue's name and address auto-populate the fields in the Event Builder.

Enhancements

• Event Items with Type = “Donation” and Type = “Other” (Products) can no longer use the Waitlist Enabled and Waitlist Capacity fields. Previously, it was possible to configure waitlists for Products and Donations. This caused an Event to appear to have Tickets available even though the Tickets were sold out.
• Users will now see the Primary Color reflected on the Event’s Landing Page in the Event Builder. Previously, only default colors were visible on the Landing Page, and custom colors appeared on the Event webpage.
• “ACH” is now an active value in the Enabled Payment Methods picklist on the Event Settings object.
• Event organizers can now accept payments via electronic fund transfer (ACH) during the Event checkout process. To activate this Payment Method, go to the Event Settings record for the Event and add “ACH” to the Enabled Payment Methods. For some organizations, the "ACH" picklist value will need to be activated via Setup.
• Cloning an existing Event with a Payment Processing Fee will result in a cloned Event that includes the same Payment Processing Feevalue.
  • If the original Event's Payment Processing Fee field is blank, the cloned Event's Payment Processing Fee will also be blank.
  • If a Default Fee value exists on the original Event, the cloned Event will have the Default Fee related to it.
  • The Payment Processing Fee related to the Event that is being cloned takes priority over the Default Fee, including empty fields.

Webapp Release

Bug Fixes

• When Currency Display = "ISO" on the Event Settings for an individual Event, the ISO code will appear throughout the registration process. When the Currency Display field on the Event Settings for an Event Group conflicts with the Currency Display field for an individual Event, the Event Group's setting will override the individual Event's setting when viewing the Event Group page. (Known Issue: 000002795)
• Pending Attendees who access an Event via their AttendeeLink will now see a banner containing the AttendeeLink Invite Message and RSVP buttons. An Attendee can use the buttons to register or cancel. (Known Issue: 000002815)
• Event Settings applied at the Event Group level will override all Event Settings applied at the individual Event level. Previously, Event Settings applied at the Event level overrode Event Settings applied to an Event Group.
• When Account Postal Code = "Required" on an Event Item record, Attendees are required to provide their "Account Postal Code". This setting overrides all other logic related to the Account Postal Code. (Known Issue: 000002809)
• When a user uploads Events’ descriptions, the text will be displayed properly by responsively wrapping to accommodate the width of the device and browser window. Previously, the text did not wrap unless manually entered via Salesforce. (Known Issue: 000002872)
• Users can now control whether Ad-Blocking and Anti-Tracking are turned on or off when accessing an Event from their community. (Known Issue: 000002942)

Enhancements

• Attendees who are registered for an Event but are waitlisted for a free Session can now register for the Session via their AttendeeLink when a spot becomes available. (Known Issue: 000002722)
• Users can now view and report on Form responses that include a “false” value for a checkbox question. Previously, only checkbox questions with positive or checked responses were included. (Known Issue: 000002676)
• When logged into a community, users can now select a number of tickets for an Event without having to add themselves as an Attendee. The user can then click Registerto complete the registration process.
  • The Disable Requirement to Add Myselffield (checkbox) was added to the BT Event Listing component. The default setting is “True” or checked.
    • When Disable Requirement to Add Myself = “False” or unchecked, the user cannot register other Attendees without registering themselves. They must click the Add Myself button.
    • When Disable Requirement to Add Myself = "True" or checked, the user does not have to add themselves to register other Attendees.
    • NOTE: The Add Myself button will always be visible, even if Disable Requirement to Add Myself = “ False” (unchecked).

Accessibility

• A vision-impaired Attendee can use assistive technology to navigate the ticket selection and payment detail pages in a meaningful sequence. The phone country code is now selected before the phone field. Previously, the phone country code field was selected after all other fields, including the button used to navigate away from the page.
• To ensure users can perform various actions via keyboard (ex. activating buttons, links, and form controls), non-tabbable HTML elements were converted to HTML elements that can be tabbed.

Field/Layout Updates

New Object

• Name: Fee
• The Fee object is Read only for all Payments permission sets except for the Blackthorn | Payments (Admin) permission set.

New Fields

• Label: Fee Name
  • API Name: Name
  • Location: Fee object
• Label: Fee Percentage
  • API Name: Fee_Percentage__c
  • Location: Fee object
• Label: Default Fee
  • API Name: Default_Fee__c
  • Location: Fee object
• Label: Payment Processing Fee
  • API Name: Payment_Processing_Fee__c
  • Location: Event object

Mobile Check-in App

Version 1.1.3

Bug Fix

• Using the External ID feature to scan a QR code will create an Attendee from a Contact with the Contact’s name fields properly mapped to the corresponding Attendee’s name fields. Previously, prefixes, middle names, and suffixes disrupted the mapping, causing duplicate Contact records with improperly mapped names. (Known Issue: 000002938)

Admin Upgrade Instructions

To upgrade Events to the newest version, go to the Blackthorn Candy Shop.

Blackthorn has adopted Salesforce’s managed package installer to simplify the installation process. Since Payments is already installed, the installer will install Base Package and make sure the correct version of Payments is installed before installing Events.

For step-by-step instructions, click here.

Testing

From now until 08/22/23, the directions below will teach you how to test the new front-end features, enhancements, and bug fixes until they are automatically pushed to the front end.

To Do

You will need to replace the Event Page and AttendeeLink URLs, events.blackthorn.io' domain, to a test domain.

TEST DOMAIN: https://preview.events.blackthorn.io/

For example, when you create your Attendee, an AttendeeLink URL is generated with the "events.blackthorn.io" domain like this one:

https://events.blackthorn.io/2E12oua7/attendee/ty2W6t9awokrDMaLWi8Mf4sLMedhdrWSBHw6HS7kqVnJ0kKmCK63yl0IxWpbAUBo

You'll then click on the AttendeeLink URL so it opens up in a new page. Remove "events.blackthorn.io" and replace it with "preview.events.blackthorn.io" so it looks like this:

https://preview.events.blackthorn.io/2E12oua7/attendee/ty2W6t9awokrDMaLWi8Mf4sLMedhdrWSBHw6HS7kqVnJ0kKmCK63yl0IxWpbAUBo

If you have any questions about this or need help with testing, please don't hesitate to reach out to Blackthorn Support.