April 2020 - Version 2.74

The April 2020 release is here! :dancers:

Once the below updates have been reviewed, please upgrade your events and payments app from the appexchange.


April 2020 Release Webinar

We had a webinar on Tuesday, April 7th at 10:00 AM CST where customers learned all about our new features and enhancements from Ashley Wagner, the Director of Customer Success at Blackthorn.

Click here for the recording


New front-end features and enhancements

There are certain features and enhancements that have now been automatically pushed to production. They were pushed on April 9th at 5:30 AM CST.

Upgrade instructions

  1. Review and upgrade your Payments App (even if you have free events) here.

  2. Then upgrade your Events App here.

  3. Visit the Blackthorn | Events Admin tab, navigate to Scheduled Jobs and click the "Schedule recommended event jobs" button. You can see our scheduled jobs in Setup - Jobs - Scheduled Jobs. You can find more details here.


Testing (No Longer Needed)

From now until April 9th, the below directions will teach you how to test the new features and enhancements until they are automatically pushed. The features and enhancements that are part of this will have a BETA label next to them in the below documentation.

To Do
You will need to replace the event page and AttendeeLink URLs 'events.blackthorn.io' domain to a test domain.

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

For example, say you want to test our visibility control feature. When you create your attendee, an AttendeeLink URL is generated with the "events.blackthorn.io" domain like this one:


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:


^^ Same instructions above go for the Event Page URL field on the Event record.

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.

Feature section

  1. Automatic update to the Attendance Status for no shows.
    When an attendee registers for an event but does not attend, after the event (that is when the Event's end date/time is in the past) a new batch job named "Blackthorn | Events Process No-Show Attendees" will automatically update the attendee's Attendance Status to No Show. To learn more about this new feature, click here.

  2. Event Summary fields on Contact, Lead and Attendee.
    When the event organizers want to know whether an attendee who has been invited to an event has attended an event in the past, we have a new summary field named "Events Attended" on the Contact, Lead and Attendee objects. This will show the total count of Attended events for that attendee when the Attendance Status is set to Attended. For more information, click here.

  3. Data Dictionary
    This will support languages all over the globe and provide you the ability to easily override labels with just a couple clicks! For more information, please click here.

  4. Event Visibility
    This let's you expose certain tickets to certain attendees through the AttendeeLink. If you have multiple membership levels where each level shouldn't see each others pricing, than the Event Item Visibility Control feature is for you. To learn more about this feature, click here.

  5. Virtual Events
    This feature lets you host webinars or live streaming events for your attendees through the AttendeeLink. You can manage all events and attendee data for all online events entirely in Salesforce, without integrations or data transfers. To know more about this, click here.

  6. Precheckout and checkout rich text fields
    We support two new rich text fields on the pre-checkout and checkout pages during registration which will allow you to show any additional information that you would like! Click here for more information.

  1. Blackthorn Events Community Lightning Component BETA
    Th new Blackthorn Events Lightning component allows customers to register for an event from a Lighting component on a Community. There are two view types, Calendar and List, that show upcoming events. For more information click here.


  1. Internet Explorer - While still unsupported, we have made a few changes to our pages on Internet Explorer. Our priority was to make sure you can register for events and checkout. We have also included a banner to recommend upgrading to a modern browser.

Recommended modern browser options:

  1. When a long postal code string was entered during the checkout process, it failed the Event Registration Submissions record, further failing to create attendee/contact records. To prevent this, we are storing only the first 10 digits/characters in the Postal Code field for the Attendee and the Payment Method records.

  2. For events with thousands of attendees, there was an issue updating the event; and pushing the update to all of the attendees. Previously, this flagged an Apex CPU time limit exceeded error. This was updated to push a batch job to update the description for the attendees automatically 30 minutes after the description on the event had been updated.

  3. For events that have 1 spot remaining, when two people are registering at the same time; it will now flag an error when whoever is last, attempts to register. This is our way to ensure events aren't overbooked.

  1. On the Mobile Check-In app, badge printing settings now include a picture and additional fields to display on the attendee badge. For more information about this feature, click here. If you'd like to install the Mobile Check-In app, go here

Bug fixes

  1. Sales Documents are now created with the default ISO Currency set from the Sales Document Record Type, instead of USD.

  2. Previously there was an error when trying to create an Attendee without the Payments Admin permission set. This has been fixed so the payments permission set is not needed.

  3. Previously, the Form field was throwing an error for the Limited user permission set. Read access for all objects have been provided now in the Limited Access permission set.

  4. The AttendeeLink field was previously not populating on the Campaign Member record when synced from Event to Campaign. This now works.

  5. Previously, when adding an event to Apple Calendar, it was not adding the event to the calendar. This has now been fixed and is working properly. If you'd like to read more about using the calendar feature, you can read about it here. BETA

  6. Previously when adding an event to an Outlook Calendar, it was not adding the event to the calendar. This has now been fixed and is working properly. If you'd like to read more about using the calendar feature, you can read about it here. BETA

  7. When Attendee Form fields outside of Name, Email, and Phone are required, you weren't able to complete the waitlisted form. This has now been fixed. BETA

  8. When trying to match an attendee to a person account, it failed and threw an error "Invalid field PersonEmail for Lead". This has now been fixed.

New Fields/Layouts



Please add the below fields on the respective object page layouts. If you have custom permission sets, make sure the fields are granted access where necessary.

  1. Auto-update Attendance to No Show - This is a picklist field on Event Settings which needs to be set to 'Yes' when you want the Attendee Attendance status to be updated for No Show.

  2. Events attended - Number field on Contact and Lead object to store the count of events attended by the respective contact/Lead and formula field on the Attendee record.

  3. Visibility Control - New Multiselect picklist field on the Event, Event Item, Attendee and Contact object record. This field defines the visibility access for the ticket type or event item through the Event URL or AttendeeLink. (Currently, supported only for Event Item and Attendee)

  4. Precheckout Details - New rich text field on the Event object to add rich text information (images and/or text) on the pre-checkout page.

  5. Checkout Details - New rich text field on the Event object to add rich text information (images and/or text) on the checkout page.

Did this page help you?