July 2023 - Version 3.103.2

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

New Features

Event Builder

The new Event Builder improves upon the Event Wizard by providing Event Organizers and Planners with a “What you see is what you get” interface and an efficient design for creating and updating Events.

Click here to learn more about the differences between the Event Builder and the Event Wizard.

Dynamic UI

The new Dynamic UI displays the information entered for an Event. This means less effort is needed to determine if you will create a simple or complex Event.

Here are a few more features included in the new Dynamic UI.

• A contemporary look and feel with a large banner and streamlined navigation creates a more delightful user experience.
• Attendees can scroll to see a comprehensive view of an Event’s details on one page or use the navigation bar to jump to a section of interest.
• The customizable footer with hyperlinks creates better connectivity and consistency across your organization’s web presence.

Off-Cycle Release

June 29, 2023

• Performing a hard refresh on an Event Group URL will no longer cause some of the Events in an Event Group to disappear. Previously, if a user queried more Events than the query limit, only recurring Events from the last request remained. (Known Issues: 000002900 and 000002915)

June 22, 2023

• June’s Webapp release contained a version conflict for the social media fields on the Speaker object. This conflict prevented Event websites from loading if the Event included Speakers. (Known Issue: 000002896)

Labeling Updates

To simplify the release note process, we have relabeled the different sections in the Release Notes. Going forward, each bullet point will be listed under either BT Salesforce Release or Webapp Release (previously referred to as a platform release). The BT Salesforce Release typically occurs the week before the Webapp Release.

• For more information about the new terminology, please review Important Definitions.
• To review the dates for each release type, please see the Blackthorn 2023 Release Dates.

BT Salesforce Release

Bug Fixes

• Invoice Line Items will now populate with the relevant Event and Event Item details. Previously, those details only populated for Line Items with corresponding donations. (Known Issue: 000002362)
• Generating a recurring Event from a published Event template now functions as expected. The following validation error will no longer occur. “Insert failed. First exception on row 0; first error: FIELD_CUSTOM_VALIDATION_EXCEPTION, To Publish, please create at least one Ticket (Event Item).: []” (Known Issue: 000002737)
• Registered Attendees can join Zoom meetings via the Webinar/Meeting URL without being prompted to also register on Zoom’s end before entering the meeting room. This corrects a blocker introduced by an update to the Zoom waiting room. (Known Issue: 000002779)
• Recipients of an Event receipt email will now see their first name populated in the greeting. Previously, the merge field in the first name position referred to the Primary Registrant First Name field, which is often not populated. The merge field now references the Bill To First Name field. (Known Issue: 000002791)
• When an Attendee provides a phone number during registration, the phone number will be saved to the Attendee record. Previously, a bug introduced by a checkout update prevented the phone number from being saved.

Event Wizard

• When a banner image is uploaded in the Event Wizard and enhanced domains are enabled, the image will be displayed correctly. A fix for this bug was included in the March release, but the previous fix did not fully resolve the problem. (Known Issue: 000002578)
• Previously, when the Event Wizard was used to edit a published Session, the Registered field would reset to “0” but the Registered count would correct itself after the next Attendee registered for the Session. This bug has been fixed. The Session’s counts will accurately reflect the number of registrations and availability. (Known Issue: 000002638)

Permission Sets

• The Blackthorn | Events (Admin) and Blackthorn | Events (Organizer) permission sets were updated to include access to post-registration and post-Event Forms and Form Submissions. (Known Issue: 000002686)
• Users with the Blackthorn | Events (Admin) permission set assigned via a Permission Set Group can now successfully authorize the Events app. Previously, the Blackthorn | Events (Admin) permission set had to be assigned individually for authorization to work. (Known Issue: 000002746)

Sessions

• After cloning an Event with a Session and Table record, the cloned Table record will now point to the cloned Event’s Session instead of the original Event’s Session. (Known Issue: 000002709)
• For free Events, Attendees waitlisted for a paid Session can now register for the paid Session when their Registration Status is updated to "Pending". Previously, the redeem functionality for waitlisted Sessions did not support the combination of free Events with paid Sessions. (Known Issue: 000002718)

Enhancements

• The new field Source was added to the Attendee object. The Source field tracks the origin of the Attendee data and will be automatically populated with the appropriate value based on how the Attendee was created. The values include Web App, Salesforce UI, Bulk Import, Attendee Registration Component, Campaign Sync, and Check-In App.
  • Location: Attendee object
  • Field Name: Source
  • API Name: conference360__Source__c
• When a (decrypted) Webinar/Meeting Password (conference360__Webinar_Password__c) is sent via email from the Email template builder, the password is decrypted and visible to the recipient. The password is encrypted while stored in Salesforce.
  • To allow this to happen, two new fields were created – one on the Event object and one on the Session object.
    • Event object
      • Label: Webinar/Meeting Password
      • Name: Webinar_Password2__c
    • Session object
      • Label: Webinar/Meeting Password
      • Name: Webinar_Password2__c
  • Before using either field on the Attendee email template, create a formula field on the Attendee object for each new field that references each new field. Afterward, use the formula field(s) on the email templates.
  • Existing customers with custom permission sets need to update their permission sets to match the following for the new field.
    • Blackthorn | Events (Limited Access) - Read/Edit
    • Blackthorn | Events (Organizer) - Read/Edit
    • Blackthorn | Events (Read Only) - Read
    • Blackthorn | Events (Admin) - Read/Edit

Webapp Release

Bug Fixes

• The Dietary Preference field's picklist options will now display the picklist "Value" rather than the API Name. Also, the Dietary Preference field's "None" option now has a Data Dictionary key. (Known Issue: 000002216)
• Web browser tab labels are now translated for the Tabbed UI. Previously, only the content of the page was translated while the web browser tab was displayed in English.
• Custom content titles will now properly display the single quote character (Example: d'intégration). Previously, the character was displayed as ' because it was not being decoded.
• When an Attendee views an Event landing page before the Sales Start Date or after the Sales End Date, they will be prevented from registering for the Event and will see the following.
  • a “Sale starts [date]/Sale ended [date]” message
  • a red “Upcoming/Closed” banner
  • the Register button is replaced with a Ticket Information button.
  • Note: At the Event Group level, the Sales Start Date and the Sales End Date will be displayed. (Known Issue: 000002694)
• Users can now test registering for an unpublished Event by clicking the Preview button or the Preview tab. Previously, a bug prevented registration while using the preview feature. (Known Issue 000002899)
• If an Event using the Dynamic UI has tickets with a past or future sales date or if the tickets are sold out, an Attendee will see a message indicating the correct status and relevant date. Previously, the Get Ticket button was visible giving the impression that tickets were available.
• Only one Accessibility icon will be visible in the lower left-hand corner of an Event’s website. Previously, a second icon was visible.
• If a user sets the Primary Color (#) on the Event Settings, they will see that exact color on the Event website. Previously, the Event website included logic to dynamically lighten or darken the Primary Color (#) based on the contrast ratio between the base text color and the primary color. The result was a slightly different primary color than the original hex value. While this change gives users more granular control, it also means that users are now responsible for making their color and contrast accessible to Attendees. (Known Issue: 000002375)

Checkout

• Attendees registering for a paid Session will now see the text in the Session Checkout button wrap to a second line if the text plus a price or “Add” action is too long to fit in the original button. Previously, the button text ran onto the page when the page was translated into Spanish.
• When an Attendee registers for a free Event and makes a Donation, they will see the Donation amount reflected in the Summary. The text on the button will also change to Pay [donation amount] instead of Register. (Known Issue: 000002641)
• After their payment is processed, Attendees who purchased a Ticket via Stripe Checkout will now be redirected to the designated Redirect URL. Previously, Attendees were redirected to the default registration success page. (Known Issue: 000002751)

Event Groups

• A Keyword’s Category field’s picklist options will now display the picklist “Value” instead of the API Name in the Event Group filter. (Known Issue: 000002216)
• The Event labels on the Event Group URL view will no longer be placed on Donations and Products. Previously, if a Donation’s or Product’s Sales Start Date was before the Ticket’s Sales Start Date, the label would reflect the Product’s or Donation’s Sales Start Date. Now, the label will reflect the Ticket’s Sales Start Date and will say “Sales start on…” The same rule also applies to an Event’s price label when the Event is on sale. The price label will say “Starts at $…” and will reflect the lowest ticket price. (Known Issue: 000002568)
• Users can now see the CSS styling added via the Event Group’s Custom CSS URL field reflected in the active Event Group webpage. (Known Issue: 000002668)

Forms

• When a pre-registration Form is applied on the Event level, the Form will only be shown once during registration. Previously, adding a Donation to your Event caused the Form to be shown twice. (Known Issue: 000002781)
• When an Attendee completes a pre-registration Form, their existing data will pre-fill the Form according to the Event organizer’s field mapping, even if the Event Items reference different Forms. Previously, Forms would not pre-fill if the Event Items referenced different Forms. (Known Issue: 000002608)

Enhancements

• An Attendee now has 30 days after the end of an Event to complete a post-event survey. Previously, post-event survey links were only active until the end of the day on the final day of the Event. (Known Issue: 000002693)
• An Attendee registering for an Event on their mobile phone can now enter a promo code from the Order Summary or the Payment step. Previously, promo codes could only be entered from the Order Summary step.

Field Updates

New

• The new field Source was added to the Attendee object. The Source field tracks the origin of the Attendee data and will be automatically populated with the appropriate value based on how the Attendee was created. The values include Web App, Salesforce UI, Bulk Import, Attendee Registration Component, Campaign Sync, and Check-In App.
  • Location: Attendee object
  • Field Name: Source
  • API Name: conference360__Source__c
• When a (decrypted) Webinar/Meeting Password (conference360__Webinar_Password__c) is sent via email from the Email template builder, the password is decrypted and visible to the recipient. The password is encrypted while stored in Salesforce.
  • To allow this to happen, two new fields were created – one on the Event object and one on the Session object.
    • Event object
      • Label: Webinar/Meeting Password
      • Name: Webinar_Password2__c
    • Session object
      • Label: Webinar/Meeting Password
      • Name: Webinar_Password2__c
  • Before using either field on the Attendee email template, create a formula field on the Attendee object for each new field that references each new field. Afterward, use the formula field(s) on the email templates.
  • Existing customers with custom permission sets need to update their permission sets to match the following for the new field.
    • Blackthorn | Events (Limited Access) - Read/Edit
    • Blackthorn | Events (Organizer) - Read/Edit
    • Blackthorn | Events (Read Only) - Read
    • Blackthorn | Events (Admin) - Read/Edit

Mobile Check-in App

Version 1.1.2

Bug Fix

• A user can change an Attendee’s First Name, Last Name, and Email in Salesforce and see the updates reflected in the Mobile Check-in app. Previously, the updates were not reflected in the app. (Known Issue: 000002855)

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 07/25/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.