October 2023 - Version 4.9
  • 29 Nov 2023
  • 4 Minutes to read
  • Dark
    Light

October 2023 - Version 4.9

  • Dark
    Light

Article summary

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

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

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

Off-Cycle Release

October 10, 2023

  • Attendees can now fill out Forms that include Big List Group Options without the Form freezing or taking too long to load. Previously, an error in the filter used to retrieve Big List Group Option values caused intermittent long load times and freezing.

BT Salesforce Release

Bug Fixes

  • The Webinar/Meeting Join URL will be populated on the Session Attendee record, even if the custom setting Process Event Registration in Batches is set to” True”, and the Blackthorn | Batch Event Registration Submission scheduled job is scheduled. Previously, a bug caused the URL generation to fail when using this configuration. (Known Issue: 000002340)
  • The Event Auto Sync feature will now create Campaign Members with the same Status as the Status designated on the Event Setting. Previously, the Status of Campaign Members, who were automatically created, was not set to the Status on the Event Setting record.
    • Users can also set a Campaign Member’s Status to correspond with the Attendee’s Registration Status = “To Invite”. Previously, there wasn’t an option to set a corresponding value for this status. (Known Issue: 000002940)
    • Before using the Event Auto Sync feature, complete the following steps.
      • Add the Campaign Member Invited Status (Campaign_Member_Invited_Status__c) field to the Event Setting's page layout.
      • Add the new field, Campaign Member To Invite Status (Campaign_Member_To_Invite_Status__c), to the Event Setting's object and page layout and layout and update any custom permission sets.
  • A user with the Blackthorn |Events (Organizer) permission set can now clone Events because they have read access to the Fee object. Previously, they could not clone an Event because a lookup field referenced the Fee object and all Fee object permissions were unique to Blackthorn | Payments permissions sets. (Known Issue: 000003039)

Webapp Release

Bug Fixes

  • Attendees will now see the discount amount displayed next to the applied code and in the total calculation. Previously, a regression issue introduced in the August release caused the applied code to be displayed without the discount amount.
  • When an event organizer publishes an Event with no Event Items, Attendees will no longer see a “Closed” banner on the Event landing page. Previously, the banner logic did not consider Events without Event Items, causing Attendees to see a “Closed” banner on active Events. (Known Issues: 000002971 and 000003015)
  • Mobile device users will now see the banner image (Image URL) for an Event that is using the Dynamic UI. Previously, a bug caused the banner image to be replaced by a stock photo on mobile devices. (Known Issue: 000002985)
  • If an Attendee enters a discount code that covers the full cost of the items in their cart at any point during the checkout process, then the payment information fields will be hidden. Previously, if a discount code was entered before the final checkout step, then the payment information was still required. In addition, the $0 total will now be displayed throughout the checkout process instead of disappearing. (Known Issue: 000003021)
  • Users can now add domains to the Allowlist via the Events Admin tab and see the change reflected in the webapp. Previously, the server number was not compared to the package correctly. (Known Issue: 000002998)

Enhancements

  • When an Attendee views an Event Group URL, they will now see the Event Keywords sorted alphabetically within a Keyword's Category. Previously, Event Keywords were sorted by the date they were created.
  • If an Attendee is logged into a Experience Cloud site, they can now add additional registrations for an Event they already registered for. Previously, Attendees could only complete the registration process once per Event. This scenario also applies to authenticated users accessing an Event via iframe. Please note that additional Event Items are only available if the event organizer has not set a Max Quantity for an Event Item.

Field/Layout Updates

New

  • Location: Event Settings object
    • Field Name: Campaign Member To Invite Status
    • Field Label: Campaign_Member_To_Invite_Status__c

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 10/17/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.