June 2024 Newsletter

Events customers on our May release or later are eligible to take advantage of our new and improved caching architecture, which means faster updates to your events landing pages and reduced load times for your attendees.

Payments customers on March release or later will experience massive performance improvements to nightly auto-processed transactions.

We support the last 12 months of releases, but recommend that you stay up to date with our 3 major releases to benefit from our new features and bug fixes.

Blackthorn Events

1. BREAKING CHANGE: As of June 2024, Blackthorn no longer supports using Internet Explorer (IE) with the Events app. Microsoft officially stopped supporting IE in June 2022 and recommends using Edge (configured in IE Mode if necessary).
2. Enhancement | Translatable Post-Event Surveys/Questions: Post-Event Surveys/Questions can now be translated. However, please note the following:
   • Default values, picklist values, and big list values will not be translated to accommodate custom flows and logic.
   • Since Post-Event Questions can work independently from Events/Event Settings, they are not impacted by the Event Settings’ Source Language and Target Language fields. Instead, the questions will be written in the language set by the org’s locale.
3. IN PROGRESS | Advanced Visibility: We are alerting you to new objects and fields being deployed with the June release related to the foundational development of a new feature, but are currently not functional. The new Advanced Visibility feature will be for organizations using an Experience Cloud site who want to exhibit granular visibility controls. The new objects are called BT Rule, BT Rule Condition, and Blackthorn Base Settings.

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 is a Salesforce Release Update that 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. DocumentLink Enhancement | NEW FIELD on Invoice: The Invoice record has a new field called Dynamic Fee Name. The field is populated when an Invoice related to an Event with an associated tax Fee is created or updated. The field’s value will then be used in DocumentLink’s Invoice to override the Tax column’s label. This update is related to the foundational development of the Tax/GST feature and is not functional.
   1. Field Label: Dynamic Fee Name
   2. API Name: bt_stripe__Dynamic_Fee_Name__c
   3. Data Type: Text
   4. Description: The name of the label used to display the tax Fee on an Invoice. For Events, it is the Fee Name of the Fee associated with the Event.
3. PayLink Enhancement | Translation & Data Dictionary: Users can now translate button labels and other static text on PayLinks. The Data Dictionary provides multilingual support, allowing Admins to establish a default language that serves as the primary language for all users. Admins can also override the default language and customize users’ language experiences when specific predefined criteria are met.
4. Mobile App (iOS) Enhancements: Multiple Enhancements and Bug Fixes have been deployed with the June release, and here are a few highlights:
   1. Blackthorn iOS Mobile FSL app users will now see the following message in the Blackthorn Logs, “Something went wrong. Please return to the Field Service app, refresh the record, then try again.” Previously, users received this message, “invalid ID field: {!btfslmobileext__Open_Charge_Record_Id__c),” causing confusion.
   2. iOS Mobile Payments app users can now use the Blackthorn Payments | Mobile Settings custom setting Skip Receipt Screen to determine if the last screen will show the option to send a receipt.
      1. If Skip Receipt Screen = “True” (checked), the last screen won’t show the option to send a receipt.
      2. If Skip Receipt Screen = “False” (unchecked), the last screen will show the option to send the receipt.

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

Blackthorn Messaging

1. Bug Fix | “Uncaught Object Error” on Bulk SMS Campaign Page:
   1. Description: Previously, when a user tried to send bulk SMS from a campaign record, they received the following error. Also, when they clicked Done, the screen did not update."Uncaught # throws at https://xxxxxxxxxxxx--simplesms.vf.force.com/auraFW/javascript/VXZJYkJtTFAtX2RjOGFiVmZaelpqQTk4bkk0bVJhZGJCWE9mUC1IZXZRbmcyNDguMTAuMy01LjAuOQ/aura_prod.js:103:67615"
   2. Resolution: We removed unnecessary libraries, which were loading even though they were not in use anymore, to fix both issues.
2. Enhancement | Refreshing a Sandbox Will Not Interrupt the Production Account
   1. Description: Refreshing a sandbox caused the Account and API Key to be cloned, which caused problems with the related production account in the BT Base package and Messaging app.
   2. Resolution: Using the production Account and API Key in the refreshed sandbox is now restricted. If a user tries to open the Messaging Admin tab after the Sandbox was refreshed, they will see the following error.

Blackthorn Catalog (previously Storefront)

1. Enhancement | Form Builder Tab: The Store page layout now includes a tab for the BT Form Builder. After clicking the tab, users can edit existing BT Forms related to the Store on the Store record. If a user clicks the BT Form Builder tab when no BT Forms are associated with the Store, they will see the following message: “There is no Form associated with this Store.”
2. Webapp Enhancement: We updated the code in Catalog to prevent robots and website crawlers (such as search engines) from accessing and indexing Catalog web pages, preventing certain Catalog information from appearing in web search results.

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