February 2023 - Version 3.90.2

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

Off-Cycle Release

Events Version 3.89

January 31, 2023

• Updates were made to the backend Attendee registration process to prevent duplicate charges and duplicate ERS records. To resolve this issue, customers MUST upgrade both packages to the latest Events (3.89) and Payments (5.92) versions.

Payments Version 5.92

January 31, 2023

The following updates were made to prevent a Coupon on the first (prorated) Invoice from being applied to the entire Invoice as well as individual prorated Line Items when Proration Behavior = “Create Prorations” on a Subscription using a percentage off Coupon.

• New Field
  • Location: Line Item object
  • Field Label: Is Not Discountable
  • API Name: IsNotDiscountable__c
  • Added to Stripe Billing permission set
• Functionality
  • The default setting for this field is “False”.
  • Users must set Is Not Discountable = "True" on any Line Item records that should not be discounted.

Enhancements

Front End

• The backlink in the top banner on the Event pages will remain in the same location when users move between pages.
• The focus state outline will be visible on each focused element as a user navigates the page via the keyboard.
• The Skip to Main Content link is now the first tab to appear when tabbing through the following pages.
  • Event Group pages (Aspen, Maple, List, and Calendar)
  • Event Detail pages (Simple, FullWidth, and Tabbed)
  • Event Registration pages (Checkout pages)
• When the user clicks the Skip to Main Content link, the focus will move to the main content of the page.

Back End

• For those using Events Version 3.68+, the AttendeeLink Custom Questions mapping prefill of data no longer requires a feature flag.

Bug Fixes

Front End

• The Country shown in the Payment information section will accurately reflect the Country chosen in the Attendee information section.
• When joining a webinar meeting via an AttendeeLink, Attendees will no longer receive the "This meeting link is invalid (3001) - error code 2004." error and will be able to join the Event.
• When the Event Settings’ One Unique Attendee Email Per Event field is checked and 2+ Attendees use the same email address to apply a promo code, the user receives the “Duplicate email registration not allowed” warning. The message “One unique email per ticket” also appears under the Code field.

Back End

• When creating an Event, the "Insufficient permissions: secure query included inaccessible field" error has been resolved for those using the Blackthorn | Events (Admin), Blackthorn | Events (Organizer), and Blackthorn | Events (Read Only) permission sets. For those using custom permission sets, update the following:
  • Permission Set: Blackthorn | Events (Organizer)
  • Object: Event
  • Field: Chat Channel Created (Chat_Channel_Created__c)
  • Read Access = “True”
  • Edit Access = “True”
• In the Attendee Registration Lightning Component, the Form Element will only display the Big List Group option selected for that Form Element.
• When the One Unique Attendee Email Per Event checkbox is checked on Event Settings and an Attendee is "pre-registered", they will no longer receive the "Code is invalid" error.

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 02/14/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 attendee 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.