June 2022 - Version 3.64
  • 13 Jul 2022
  • 8 Minutes to read
  • Dark
    Light

June 2022 - Version 3.64

  • Dark
    Light

If you have any questions about the release note, please don't hesitate to reach out to us through our support form.

REQUIRED: The Candy Shop link must be used to upgrade the June release for Events.

The Candy Shop is open! This is your one-stop shop for installs and upgrades. To visit the Blackthorn Candy Shop page, go here.

Breaking Changes

Event Preview Page Update

The ability to switch between languages within an Event Preview page is now available. Users can switch between languages (translations) within an Event Preview by using the same method (language picklist) they use when viewing an Event Page URL.


Enhancements

Important Update

Blackthorn Events now supports Products and Donations at Checkout, and our Static Translations feature for multi-language Events is now in Beta.

Front End

  • Waitlisted registrants are now able to remove themselves from an Event’s waitlist via their AttendeeLink.

Back End

  • The AttendeeLink now supports a custom cancelation message that is added via the new Event Setting field, Ticket cancelation message.

  • The Advanced Permissions Assignments button has been added to the Configuration tab on the Blackthorn | Events Admin page. Clicking the button opens a modal where the user can assign/remove multiple Blackthorn permission sets at once.

Important to Know

The “Donations” and “Products” sections will be updated automatically when Events is install and/or upgraded. The new fields on the Attendee (Donated field and Purchased Products field) need to be added manually as they are not added by default to page layout.

Bug Fixes

Front End

  • The Event Name will not display in the Image Section of Events in an Event Group if the Event record includes an invalid Image URL. Only the Image icon will be displayed.

  • The first letter of the first word in each section of the Error 2010 page will now be capitalized.

  • Picklist options with the “|” symbol on a Form Element can now be selected.

  • If an Attendee is registered for a paid Event and tries to cancel the registration via the Attendee’s AttendeeLink, the cancelation modal will now show the correct error message.

  • An Event’s Event Start Time and Event End Time will be listed in the Attendees’ timezone when added to their calendar.

  • The AttendeeLink will now only show the Sessions associated with the Event Item (Ticket) that an Attendee has registered for instead of showing all of the Sessions. Hidden Sessions will only be visible on the post-checkout AttendeeLink page.

Registration/Checkout

  • The Contact section on checkout will be displayed during checkout regardless of the contact information that is entered on the Attendee form.

  • The custom donation amount entry in the checkout cart will be updated immediately after the user types the custom donation amount value in the box.

  • The zip code for addresses in Germany, Austria, and Switzerland is now required when registering an Attendee for an Event.

  • The Phone field on the Attendee checkout form has been updated to only allow phone numbers with a maximum of 12 numbers. The error message for an invalid phone number has been changed to “Please enter numbers only, no special characters.”

  • A user can only enter a custom donation amount if the value is greater than $0.00.

UI Experience

  • When the UI Experience is set to “Full-Width”, the Sessions section on the Event Page will show both the dates and times for the different Sessions.

  • When the UI Experience is set to “Full-Width” and a Custom Image is not defined for an Event Sponsor, the following will occur:

    • The Event Sponsor will not be displayed.
    • A Sponsor Tier label will not be displayed when all Sponsors in that Tier are missing a Custom Image.
  • When the UI Experience is set to “Full-Width” and a Custom Image is defined for an Event Sponsor, the Sponsor will be displayed under the relevant Tier.

  • When viewing an Event Group in an iframe, users can now toggle between the List and Calendar layouts/views.

Does your organization only host free Events?

The look and feel of the checkout experience has changed, including the removal of any reference to cost and dollar amounts. For only Free Events, the following changes were made to the checkout experience:

  • Changed Checkout button to Register
  • Changed the header “Order Summary” to “Summary”
  • Removed individual ticket prices
  • Removed the Subtotal line
  • Removed the Total line

Back End

  • Users can now register an individual from a Lead record, Contact record, or Person Account record using the Attendee Registration Lightning Component when the individual’s name has an apostrophe in it.

  • An Event without an Event Start Date or Event End Date is now searchable when a user searches for the Event on the Contact, Lead or Attendee record using the Attendee Registration Lightning Component.

  • After an Attendee enters their email address in the Email field during registration, the email address will be visible in the Primary Email field on the Attendees List.

  • All active fields on an Attendee record will now be mapped to the Contact record in Salesforce.

  • Since the following fields do not have any functionality tied to them, they have been deprecated and removed from all permission sets.

    • conference360_Registration_End_Date_c
    • conference360_Registration_End_Time_c
    • conference360_Registration_Start_Date_c
    • conference360_Registration_Start_Time_c
  • During checkout, the “Sold Out” message will only appear on Tickets when the Remaining Capacity is set to “0”.

  • After reauthorizing the Events app as a different user, the Authorized User value on the Events Health Check page will now be updated to reflect the new authorized user.

  • Error messages generated from Connect360 requests will now provide additional details to clarify the issue.

  • When using the Event Wizard, the Registered value for an Event will now update correctly when an Event Item’s Quantity Available is updated.

  • If an Attendee has their Registered Status set to “Invited” and a second Attendee with the exact information joins the Waitlist, the Registered Status of the first Attendee will be updated to “Waitlisted - Pending”. A second Attendee Record will not be created.

  • If an Attendee registers for the last open spot for an Event, their Registered Status will change to “Registered”. If a second Attendee with the exact information registers for the same Event, a second Attendee Record with the Registered Status set to “Waitlist-Pending” will not be created.

Cloning an Event

  • Users will now be able to clone an Event without receiving a blank white screen.

  • After cloning an Event that has the same Sessions in the Event and in the Event Item, an Attendee will be able to see the cloned Event’s Sessions during checkout.

  • After cloning an Event with at least one Event Item in the Event Wizard, the Event Item in the cloned Event will retain the same settings as the original Event Item.

Data Dictionary (Translation)

  • Users can now use debug to find the Data Dictionary keys.

  • If a Data Dictionary entry is created with new text for LBL_SALE_STARTS_WITH_CONJUNCTION, the new text will be aligned and resized properly to fit on the BT Events Listing Component.

  • When an Event has a specific Time Zone selected and the Event Settings’ Language Selector is set to “On”, the text in the time on the Event Page URL will be translated. For example, instead of “18:00 to 23:00” (English), it should say "18:00 bis 23:00 Uhr" (German).

Event Settings

  • If the One Unique Attendee Email Per Event checkbox is selected in Event Settings, a Warning message will be displayed when a user registers for multiple Tickets with different names but the same email address.

  • If the One Unique Attendee Email Per Event checkbox is selected in Event Settings, the ERS Status will be set to “Completed" when a user registers for multiple Tickets with different names and with different email addresses.

  • Custom CSS will now be applied from the Event Settings page to the post-Event survey form.

Sessions

  • If a Session’s Status is set to “Active”, the Session will be displayed on the Event’s landing page.

  • If a Session’s Status is set to anything other than “Active” or is left blank, the Session will not be displayed on the Event’s landing page.


Field, Object, and Layout Changes

New

  • The AttendeeLink now supports a custom cancelation message that is added via the new Event Setting field, Ticket cancelation message.

Deprecated

  • Since the following fields do not have any functionality tied to them, they have been deprecated and removed from all permission sets.
    • conference360_Registration_End_Date_c
    • conference360_Registration_End_Time_c
    • conference360_Registration_Start_Date_c
    • conference360_Registration_Start_Time_c

Mobile Check-In App

Enhancements

  • On the “Add Attendee Settings” screen, users now have the ability to change each field’s visibility and set which fields are required. For example, the Full Name and Phone fields can be set to “Required” while the remaining fields can be set to “Optional”.

Bug Fixes

  • If the First Name and Last Name fields on an Attendee record are missing, the Attendee record will now be visible in the Mobile Check-in app. The entry will be located at the bottom of the list under the “#” category.

  • After registering and making a payment for an Attendee whose Registration Status changed from “Waitlist - Pending" to "Pending", Invoice and Transaction records will now generate correctly.

We’ve added a new Apex class to avoid a common cause of confusion around Event authorization in a newly refreshed partial or full sandbox. This class will reset the authorization components in the newly refreshed sandbox so users are aware that authorization has not yet been completed. Users will need to add the BTEventsPostSandboxRefresh class to the sandbox refresh process for this reset capability.

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 06/14/22, the directions below will teach you how to test the new front-end features, enhancements, and bug fixes until they are automatically pushed.

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 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 us through our support form.