Note: If you ever need past release notes, bookmark this community link for quick access. >>> https://community.blackthorn.io/s/package-updates

Blackthorn Events

Sales Tax/GST for Events Checkout

The updated Fees feature for Event checkout and Invoices allows Event organizers to collect the credit card processing fee separately from the total amount due and apply required taxes. Use the following links to learn more.

• New Functionality: Learn more about the updated functionality and new logic associated with the Fee object and related updates to the Company Info, Invoice, and Event Item objects.
• Checkout Process: Learn about the order of calculations and supported scenarios.
• Using Fees: Customize your Event with either tax-inclusive pricing or taxes calculated at checkout and create Event Items that are tax-exempt.
• Set Up Goods and Services Tax (GST) Fees: For countries that use GST, our step-by-step guide will walk you through setting up Fees and the Invoice/DocumentLink.

Table Manager

The Events Table Manager is a new Salesforce Lightning component located on the Event object and is designed to efficiently manage your Event’s table and seat assignments. It’s as easy as dragging and dropping Attendees into Table and Seat assignments. This user-friendly tool offers the following functionality.

• Intuitive Drag-and-Drop Interface: Easily assign Tables and Seats by dragging Attendees right where you want them.
• Efficiency: Reduce the effort required and the potential for errors in table and seat management. The tool can bulk-assign Seats and support up to 100 Tables with 10 Seats each.
• Improved User Experience: Visualize and alter Attendee seating as needed.
• Validations: Prevent users from exceeding established limits on assignments and changes between saves.

Click here to learn more about the new Table Manager.

Recurring Events and the Builder

• Event organizers can now create, publish, and manage Recurring Events with the Event Builder, streamlining the Event scheduling and management process.
• When a user clones an Event in the Event Builder, they can edit all Event fields before saving the cloned record. This functionality now matches the Event Wizard.
• Users can now configure and manage emails from within the Event Builder when editing existing Events. The “Emails” page includes the following components and functionality:
  • Email Templates Related List
    • Create new Email Templates
    • See Email Templates related to the current record.
  • Email Configuration
    • Includes the same functionality as the Event record page component (Send Emails From, Confirmation Email, Waitlisted Email, and Waitlisted Pending Email)
  • Send Email
    • Send emails instantly.
    • Includes the same functionality as the Event record page component (Send Emails From, Email Template, Attendee Filter, Total Attendees, Email List, Attendee Preview, Preview Email, and Send)

Mobile Check-in App

• Bug Fix
  • Android Only – Badges: Android Mobile Check-in app users can now click the TAKE PHOTO button in the Attendee’s Badge section to take a photo of the Attendee. Previously, users could not launch their device’s camera by clicking the TAKE PHOTO button.
• Enhancements
  • Biometric Authentication: Mobile Check-in app users can now set up and use their mobile device’s biometric authentication feature to log into the app. Click here for instructions to set up and use the biometric authentication feature.
  • Attendees: If a user changes an Attendee’s information, including their name or email address, in Salesforce, the Mobile Check-in app will correctly display the new information on the app’s history screen. Previously, the app only displayed the old information on the check-in history screen.

Click here for more information about the Mobile Check-in app’s release notes.

For more information on these enhancements and a full list of bug fixes, please click the Events Release Notes button.

Blackthorn Payments

1. SALESFORCE KNOWN ISSUE | Enable Secure Static Resources for Lightning Components: This Salesforce release update has been postponed indefinitely. Test Run on this Release Update should remain disabled in order to use our Virtual Terminal components. This is due to a Salesforce Known Issue.
2. Batch Jobs: The Payment Balance Update batch process now only includes Connected Accounts with Update Balance = “True” (checked). Previously, it included all Connected Accounts, causing a large number of accounts to be processed together.
3. Mobile Payments App: The Mobile Payments app’s logic was updated to ensure a user can process different Transactions across different Payment Gateways and create a successfully processed Transaction and a valid Payment Method.

For more information on these enhancements and a full list of bug fixes, please click the Payments Release Notes button.

Blackthorn Events

1. Permission Set Update | Events (Lite Users): The Blackthorn | Events (Lite User) permission set is now available. Users with this permission set have Create/Read/Edit access for the Attendee, Attendee Group, Session Attendee, and Track Attendee objects and Read-only access to most Events’ objects. Users with the Blackthorn | Events (Lite User) permission set can also check in Attendees using the Mobile Check-in app.
   1. The Blackthorn | Events (Lite User) permission set does not grant access to the following Events’ objects: Waitlist, Hotel Room, Hotel Room Block, Expense Entry, Event Notification, Event Item Purchase, Event Group Association, Attendee Data Message, Data Sync Retries, Budget Expense, Badge Printing Configuration, Badge Printing Configuration Details, and Flight.
2. CRM Packages Update | Salesforce Package Names: Each Blackthorn Salesforce product has a Package Name on your org’s Installed Packages page. On February 20th, starting at 8 am ET, we will update these package names to improve our internal automation. The package name is a label and does not affect the product’s functionality. As of February 20, 2024, each package name will no longer contain the “bar” character.
   1. Blackthorn | Events
   2. Blackthorn | Mobile Payments
   3. Blackthorn | Paylink
   4. Blackthorn | Connected App
3. Webapp Release Enhancement | Event Groups BREAKING CHANGE: Event Groups using Aspen, List, and Calendar UI previously combined keyword filters with “AND” logic. The default behavior has changed to combine keyword filters with “OR” logic. If you prefer to maintain the existing “AND” logic, event groups with affected UIs must be updated so that Combine Keyword Filters with AND Logic = True. Combine Keyword Filters with AND Logic is a new field included in the February Events release for Salesforce and should be added to your event group page layout if needed.
   1. Previous behavior for Aspen, List, and Calendar Event Group UI:
      User selects “Evening” and “Spanish” keywords, and only sees events that include both Evening and Spanish keywords.
   2. New behavior for Aspen, List, and Calendar Event Group UI:
      User selects “Evening” and “Spanish” keywords, and sees all events that include either Evening or Spanish keywords.

For more information on these enhancements and a full list of bug fixes, please click the Events Release Notes button.

Blackthorn Payments

1. SALESFORCE KNOWN ISSUE | Enable Secure Static Resources for Lightning Components: This Salesforce release update has been postponed indefinitely. Test Run on this Release Update should remain disabled in order to use our Virtual Terminal components. This is due to a Salesforce Known Issue.
2. Payments Enhancements | High Volume Batch Processing: The introduction of high-volume batch processing resolves the issue of scalability with our batch processes. Previously, batch processes were limited to one record at a time to ensure that Payments complied with Salesforce’s limits. The new protected custom setting is in Blackthorn Pay – Features.
   1. Field Label: Auto-Charge Batch Size
   2. API Name: Auto_Charge_Batch_Size__c
   3. Data Type: Number(3,0)
   4. Description: Controls the batch size of the scheduled job. The default setting is 1. Currently, the maximum supported value is 75.
3. Compliance Enhancement | API Calls: To ensure Compliance meets Salesforce’s upcoming ICU Local Formats requirements, all classes in the Compliance repository will reference API version 45.0 or higher.

For more information on these enhancements and a full list of bug fixes, please click the Payments Release Notes button.

Blackthorn Messaging

1. Issue Using a Site License
   
   1. Description: A user with a Site License received the following warning message on the Contact record after upgrading the production org. “The component is part of the AppExchange Package Blackthorn Messaging, and requires a license to use.”
   2. Resolution: Previously, the Messaging app did not acknowledge the license assignment record, causing problems when trying to send SMS messages. Users with a Site License must upgrade the Messaging app to version 3.43.16 or higher to resolve the issue.
2. Issue Using a Site License
   
   1. Description: After activating and configuring the Messaging app for an org with a large number of active users, the following error was triggered upon opening a Contact record with the RLC component. “Error: Simplesms: too many query rows: 50001”
   2. Resolution: Updates were made to manage orgs with a large number of active users who have avatars.

Blackthorn Storefront

1. Salesforce Enhancement | Authorize Button: When a user clicks the Authorize button, Storefront and BT Checkout will be authenticated in the org.
2. Forms Enhancement | BT Form Elements: The help text for the following BT Form Element fields has been updated.
   1. Form: “The BT Form this BT Form Element is related to.”
   2. Question: “The question of this BT Form Element.”
   3. Hint: “A hint for this question. Will be displayed as placeholder text within the input field on the BT Form.”
   4. Sort Order: “Set the order for the questions/BT Form Elements.”
   5. Required: “Select this checkbox if the BT Form Element is required.”
   6. Form Big List Group: “Select a BT Form Big List Group if you have a picklist or a type ahead custom question with more than 1,000 options.”
   7. Picklist Values: “The answer values if the question type is a picklist.”
3. Webapp Enhancement | Inventory Management: No fewer than 12 updates have been added to the inventory management features, including updates to Available Inventory, Remaining Inventory, Show Quantity Remaining on Store, and more!

For more information on these enhancements and a full list of bug fixes, please click on the Storefront Release Notes button.

Blackthorn Events

1. Event Builder Enhancement: Event Builder users can now configure and manage emails from within the Event Builder when editing existing Events. The “Emails” section was added to the left-side navigation under Attendees. Note: When the Event Builder is used to create a new Event, the “Emails” tab will be hidden. The “Emails” page includes the following components and functionality. For more information on how to use this function, please refer to the full release notes.
2. Recurring Events Enhancement: When using the Recurring Events feature, a new Event will be generated when there are no more Events with Status = “Active” in the Recurring Event series. Previously, when Recurring Method = “Keep One Open,” multiple Events were generated according to the Count field instead of creating one more active Event based on the schedule. For more information on how to use this function, please refer to the full release notes.
3. Zoom Integration Update: When an Event or Session’s Zoom Registration Approval Type field is set to “Manually Approve Registration” or “Automatically Approve Registration,” Attendees/Session Attendees can click their AttendeeLink to join as participants. If the Session Attendee’s Webinar/Meeting Join URL field is blank, the webapp will use the Session’s Webinar/Meeting URL, ensuring Session Attendees have the correct access. Previously, Attendees were incorrectly added to Zoom meetings as hosts.

For more information on these enhancements and a full list of bug fixes, please click the Events Release Notes button.

Blackthorn Payments

1. SALESFORCE KNOWN ISSUE | Enable Secure Static Resources for Lightning Components: This Salesforce release update has been postponed indefinitely. Test Run on this Release Update should remain disabled in order to use our Virtual Terminal components. This is due to a Salesforce Known Issue.
2. Fees Enhancement: The Fee object’s page layout was updated to make the Type field required to create a Fee record.
3. Spreedly Transaction Enhancement: If a Spreedly Transaction fails, the Transaction will now contain the following information describing the reason for the failure.
   • If the response includes an error code, it will be stored in the Transaction’s Error Code field.
   • The Transaction’s token will be stored in the Transaction’s Spreedly Transaction Token field.
   • The date the Transaction was processed will be stored in the Processed Date field.
4. Mobile Payments for Android Update: If “Tap to Pay” is added as a picklist value for the Accepted Payment Methods field on a Payment Gateway, Android Mobile Payments app users will see “Tap to Pay” as an accepted payment option. (Known Issue: 000003417)

For more information on these enhancements and a full list of bug fixes, please click the Payments Release Notes button.

Blackthorn Events

1. Zoom Breaking Change: The Zoom Registration Approval Type (Zoom_Registration_Approval_Type__c) field was added to the Event object in response to Zoom’s update on April 22, 2024. This field will enforce the approval type as a required value. If you do not want to enforce registration, no action is required. Previously, Zoom meetings generated during Event creation required a guest to authenticate to join the meeting. (Known Issue: 000003320)
   • Use this field to define the type of approval a meeting registration requires. The three types of approval are “No registration required” (default setting), “Manually approve registration,” or “Automatically approve registration.” The default setting is “No registration required.”
   • The Zoom Registration Approval Type field is not automatically added to the Event page layout. Click here for detailed steps to add the field and set a value to auto-approve / manually approve registrations.
2. Experience Cloud | Community Profile Users: When using Event components in the Experience Cloud, Community Profile users can access Attendee Reports and will no longer experience redirecting issues. Please note that users need access to the Blackthorn | Events Reports folder to use the Lightning Quick Actions for different reports.
3. IN PROGRESS | Fees – Tax/GST: We are alerting you to new objects and fields being deployed with the May release that are related to the foundational development of this new feature; however, this update is not functional yet. The new fields on the Event, Event Item, and Event Item Session objects are part of the ongoing development of the Tax/GST feature and will support the use of taxes.
   • Event object: Tax Fee Calculation Type
   • Event Item object: Tax Amount and Price with Tax
   • Event Item Session object: Tax Amount, Price with Tax, and Tax Rate

For more information on these enhancements and a full list of bug fixes, please click the Events Release Notes button.

Blackthorn Payments

1. SALESFORCE KNOWN ISSUE | Enable Secure Static Resources for Lightning Components: This Salesforce release update has been postponed indefinitely. Test Run on this Release Update should remain disabled in order to use our Virtual Terminal components. This is due to a Salesforce Known Issue.
2. Spreedly | Payment Methods: When creating a new Payment Method in a Spreedly gateway, Payment Methods with either a 2 or 4-digit value in the card’s Expiration Year field will be correctly stored and synched to the Payment Gateway.
3. Chat Button: The Chat button on the Blackthorn | Payments Admin and Blackthorn | Payments Setup Wizard tabs has been deprecated.

For more information on these enhancements and a full list of bug fixes, please click the Payments Release Notes button.

Blackthorn Catalog (previously Storefront)

1. Help Text in the Store Builder: Help text was added to the following fields in the Store Builder.
   1. Store Store Name
   2. Store Featured Keyword
   3. Store Branding Setting
   4. Branding Setting Logo URL
   5. Product Image URL
2. Help Text in the Form Builder: Help text was added to the following fields in the Form Builder.
   1. Type
   2. Required
   3. Question
   4. Supplemental Question Information
   5. Maps To (Object)
   6. Maps To (Field)
   7. Default Value
   8. Hint
3. Store User Interface: The CSS in the Branding Setting’s Custom CSS URL field will now be visible in the related Store, Store Product pages, and the pre-checkout pages.

Please click the Storefront Release Notes button for more information on these enhancements and a full list of bug fixes.

Blackthorn Events

1. Default ticket selection: Help your attendees zoom through registration! Event Organizers can use the new Event Item’s Default Quantity Selection field to define the default quantity for Tickets, Guest Tickets, or Products that are automatically added to the cart when an Attendee reaches the ticket selection step. 

   When an organizer enters a value in the Event Item’s Default Quantity Selection field, and the Event Item isn’t sold out, the default quantity is automatically added to the cart the first time an Attendee reaches the ticket selection screen. 

   IMPORTANT NOTE: If a potential Attendee receives an invitation with an AttendeeLink and goes to the Event webpage from the AttendeeLink to purchase Tickets, Guest Tickets, or Products, the current behavior will occur. The new Default Quantity Selection functionality will not be applied, and the Default Quantity Selection value will not be added to the cart.

2. Encourage attendees to share your event on social media: Click the Share button to generate a URL for Attendees to share Events on LinkedIn, X/Twitter, or Facebook. The shareable link includes metadata like image, title, and description. Clicking the Share button opens a window with a sharable link and buttons for each platform. When you click the LinkedIn, X/Twitter, or Facebook button, the following happens.
   • LinkedIn: Enter a message to accompany the link and click Post.
   • X/Twitter: Use the following message: “I am looking forward to attending [Event Name] – you can check it out here: [event social URL]”) or edit it and click Post.
   • Facebook: Enter a message to accompany the link and click Share. (Facebook will only correctly render images larger than 200x200px in Facebook posts.)
3. New Zoom Option: The new Include Zoom URL In Calendar Description field was added to the Event object to allow users to show/hide Zoom links in the invite’s Calendar Description field after an Attendee clicks the Add to Calendar button. If Include Zoom URL In Calendar Description = “True” (checked), the Calendar’s description will include text similar to “To join the meeting directly, click here: https://zoom.com/url/to/meeting.” NOTE: Attendees who join via the direct Zoom link will NOT have their attendance status updated in Salesforce.

For more information on these enhancements and a full list of bug fixes, please click the Events Release Notes button.

Blackthorn Payments

1. Transactions: When a partial refund is issued for a Transaction, the refunded Transaction’s Amount reflects the correct amount, and the Transaction’s Payment Status is set to “Partially Refunded.” Previously, a refund Transaction was created for the full amount of the original Transaction, and the original Transaction’s Payment Status was incorrectly set to “Refunded.”
2. Authorize.net: If a user tries to save a new Payment Method with an incorrect zip code on an Authorize.net gateway, they will receive an error message letting them know that the Address Verification Security (AVS) failed and the Payment Method will not be saved. Previously, users received a confusing error message.

For more information on these enhancements and a full list of bug fixes, please click the Payments Release Notes button.

Tell us what you want us to build next! Your response to this 10-minute product feedback survey will not only help us prioritize our next features, but will also enter you in a drawing for one of ten $50 gift cards.

• For Events App Customers
• Survey closes on October 31, 2024
• Only customers from the US, Canada, UK, or Australia are eligible for the drawing

Blackthorn Events

1. Pre-Checkout Details and Ticket Selection: This update is a potential breaking change for those using a workaround to solve this issue. Pre-checkout details will now appear during Ticket selection, and checkout details will appear on the Contact Information/Payment screen. Previously, pre-checkout details and checkout details were swapped, causing problems when completing the registration process. (Known Issue: 000003851)
2. Event Settings: When an Attendee registers a group, they can now click the Copy related info to all the responses button to copy their Form responses to all Attendees in the group if the new Allow Form Responses for Attendee Group field is set to “Yes.” The new field removes the repeated copy-paste step and decreases the time it takes to register everyone.
   • Forms must be identical and have the same Form record ID.
   • The Copy related info to all the responses button will only be displayed if the first Event Item shown has custom questions.
3. Accessibility: Default values were added to the Sponsor’s Alternative Text for Visual Impairment and Speaker’s Alternative Text for Visual Impairment fields to save time during Event creation. Note: Default values can be overwritten.
   • Sponsor: Alternative Text for Visual Impairment = “[Sponsor Display Name] logo”.
   • Speaker: Alternative Text for Visual Impairment = “Portrait of [Contact First Name] [Contact Last Name]”.

For more information on these enhancements and a full list of bug fixes, please click the Events Release Notes button.

Blackthorn Payments

1. Payment Schedules: When a Transaction’s Transaction Status is set to “Failed,” the related Payment Schedule field Schedule Status will be set to “Failed,” and Payment Status will be set to “Overdue.” Previously, the Schedule Status was set to “Future,” and the Payment Status was set to “Scheduled.” Click here for more information about the statuses and their definitions. (Known Issue: 000002805)
2. Virtual Terminal: Users searching for a Payment Method in the LWC Virtual Terminal will see identifying information such as the Payment Method’s Holder’s Name, Email, or Last 4 Digits, depending on the Payment Method type and available information. Previously, the user saw the Payment Method’s numeric Salesforce name (E.g., PM0000001, PM0000002, etc.), making it difficult to locate the correct Payment Method. (Known Issue: 000003097)
3. Custom Settings: When the Blackthorn Pay – Trigger Settings custom setting Enable Payment Intents for ACH PMs = “True” (checked), hidden fields remain hidden, and mapping works as expected. Previously, if the custom setting was checked, hidden fields were visible, mapping broke, and users received a Terminal Data Initialization Error. (Known Issue: 000003932)

For more information on these enhancements and a full list of bug fixes, please click the Payments Release Notes button.

Don’t miss our next major release party

10/03/24, 11:00 AM to 11:45 AM ET

• Demos of our major new Events features
  • Advanced Visibility
  • Table Manager
  • Restrict Overlapping Sessions Selection
  • Sales tax / GST for Events checkout
  • Biometric authentication for Mobile Check-in Login
  • Recap of caching & capacity enhancements
• Live Q&A with the Product team
  Submit your questions for the Live Q&A in advance to experiences@blackthorn.io
• Blackthorn trivia contest

Note: If you ever need past release notes, bookmark this community link for quick access. >>> https://community.blackthorn.io/s/package-updates

Blackthorn Events

Advanced Visibility (Early Access)
Advanced Visibility allows Event Organizers to leverage Contact or Person Account data to control visibility and eligibility within the Experience Cloud or an authenticated iframe. Please open a case with Blackthorn Support to enable Advanced Visibility.

The feature uses rules with specific criteria to determine who can see and register for Events, Event Items, and Sessions. In tandem with Express Registration, Advanced Visibility helps Attendees find and register for relevant Events faster. Discover some of Advanced Visibilities’ benefits.

• Flexible Rule Creation: Creates different rules for each Event, a single rule for multiple Events, or any combination.
• Customizable Eligibility: Tailor your Attendees’ visibility experiences with options like Extend Visibility to Account and Extend Eligibility to Account.
• Compatibility with Visibility Controls: Seamlessly integrate Advanced Visibility with existing Visibility Controls, allowing for flexible configurations.

Overlapping Sessions
Event Organizers can now prevent Attendees from registering for overlapping Sessions. This functionality allows for a more organized and manageable registration experience and ensures that Event resources like Session seats and Event spaces are used effectively.

Matching and Duplication
Attendees can now register for multiple Events with identical names. The BT Events Attendee Matching Rule was updated to use an Event_ID instead of the Event Name to distinguish between Events. The registration process will also be successful if the BT Event Attendee Duplicate Rule’s Action on Create is set to “Block.” Previously, when Attendees registered for multiple Events with identical names, duplicate Attendee records were created. And if the BT Event Attendee Duplicate Rule’s Action on Create was set to “Block,” no Attendee records were created. NOTE: To use this new matching rule immediately, please make sure it is selected. (Known Issue: 000003791)

Potential Change in Default Behavior
If you have an Event that no longer shows expired Tickets/event-ended banners, but the expired Tickets/event-ended banners were previously visible, check the Show Expired Tickets field on the Event Settings record.

Previously, the Show Expired Tickets field’s default behavior was not respected, causing Tickets with a Sales End Date in the past to appear in the list of available Tickets, even though Show Expired Tickets was set to “False” (unchecked).

When the Event Settings Show Expired Tickets setting is set to “False” (unchecked), Event Items with a Sales End Date in the past will not appear in the list of purchasable Tickets. If Show Expired Tickets is set to “True,” and the Event Item’s Sales End Date is in the past, the Ticket will be visible but will have a label stating that it is not for sale. (Known Issue: 000003154)

For more information on these enhancements and a full list of bug fixes, please click the Events Release Notes button.

Blackthorn Payments

1. SALESFORCE KNOWN ISSUE | Enable Secure Static Resources for Lightning Components: This Salesforce release update has been postponed indefinitely. Test Run on this Release Update should remain disabled in order to use our Virtual Terminal components. This is due to a Salesforce Known Issue.
2. Permission Sets: The new permission set, Blackthorn | Payments (Lite User), was created. Users with this permission set have read-only access to all BT Payments objects and standard Salesforce functionality, such as reports and dashboards. Note: Users with this permission set cannot use packaged actions such as capturing Transactions, processing Refunds, etc.
3. Virtual Terminal: When the Virtual Terminal is in Lite Mode, input parameters will be correctly mapped when embedding the LWC Virtual Terminal in a screen flow. Previously, the input parameters were not mapped to the Virtual Terminal fields. (Known Issue: 000003009)

For more information on these enhancements and a full list of bug fixes, please click the Payments Release Notes button.