June 2024 - Version 4.27

Please review the updates below and follow the upgrade instructions to upgrade your Events application.

Table of Contents

• Breaking Change
• BT Salesforce Release
• Webapp Release
• Field/Layout Updates
• Upgrade Instructions
• Important Definitions

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).

Off-Cycle Release

July 2, 2024

• When using an authenticated iframe with the BT Event Listing Disable Requirement to Add Myself = "True" (checked), registrants must select a Ticket for themselves. Previously, a Ticket was automatically added to the cart for the current user even though Disable Requirement to Add Myself was enabled.
• When a user registers for an Event via the authenticated iframe, the pre-fill functionality only applies to the main Ticket. Guest Tickets will no longer be pre-filled with the logged-in Attendee's information and will not have access to the Add Myself button, regardless of the BT Event Listing’s Disable Requirement to Add Myself setting. Previously, guest Tickets were automatically pre-filled with the same information as the main Ticket contact information, causing duplicate errors on the checkout page. (Known Issue: 000003760)

BT Salesforce Release

Bug Fixes

• Users can successfully upload a 4MB or larger image using the Event Wizard. Previously, an image that size would not load, and the user did not see an error message. (Known Issue: 000003403)
• Events users can now complete the checkout process using an ACH Payment Method and a Stripe Payment Gateway. (Known Issue: 000003393)
• If a user deletes a registered Attendee from an Event or Event Item, the corresponding totals will update correctly. Previously, deleting Attendees did not update the totals. (Known Issue: 000003554)
• When a user enters text in the Alternative Text for Visual Impairment field for a Donation or Product via the Event Builder, the text will be saved correctly.
• If a user registers multiple Attendees for an Event, each with a different company name, the Account’s Account Name for each Attendee will be populated with the correct company name. Previously, only the Account related to the first Attendee had the correct Account Name. The other Account Name fields were populated with the Attendees' first and last names. (Known Issue: 000003507)
• The Blackthorn | Events (Admin) permission set was updated to include permissions for the following fields. This update is related to the foundational development of the Tax/GST feature and is not functional.
  • Event
    • Tax Fee Calculation Type (conference360__Tax_Fee_Calculation_Type__c)
  • Event Item Session
    • Price with Tax (conference360__Price_With_Tax__c)
    • Tax Amount (conference360__Tax_Amount__c)
    • Tax-Exempt (conference360__Tax_Exempt__c)
    • Tax Rate (conference360__Tax_Rate__c)

Conditional Questions

• When a user selects a value from the drop-down to answer a question on the Attendee Registration component, the related conditional question will be displayed as expected. The conditional question will no longer be visible when the user deselects the value. Previously, the conditional question did not appear when a user selected a value from the drop-down.
• If a user answers a conditional question using one of the following field types, the related child field will respond correctly. (Checkbox, Date, Email, Multi-Select Picklist, Picklist, Text, Text (30,000), and URL) Previously, when a user answered a conditional question, an error related to the child field was triggered.

Forms

• When using the BT Attendee Registration component to register an Attendee for an Event with a pre-registration type Form, the related Form Submission Answers record will be generated. Previously, the record wasn’t generated, and the answers were not saved.
• Form Submission Answers not mapped to a field will be processed with an updated error tracking process that uses fewer resources. Previously, the FormSubmissionProcessAnswersBatch batch job required the Maps To (Field) and Maps To (Object) fields to have a value. If they didn't, additional scheduled jobs were created. (Known Issue: 000003530)

Enhancements

• To improve the checkout experience when using the Dynamic and Tabbed UIs, users will see a grayed-out Checkout button and a visual loading indicator when longer processing occurs. Previously, the button was only grayed out, and when processing took a while, users were given no information about the status of the registration process.
• If Salesforce’s Territory Management feature is enabled and the Event Item’s Address field is set to “Optional” or “Required,” then the Country field must be set to “Required.” If a user tries to set the Country field to “Hide” or “Optional,” the user will receive the following message. “Country is required when state is required or optional due to enabling Territory Management.” Previously, when the Country field was set to “Hide” or “Optional,” the following occurred.
  • The Contact record wasn’t matched to an Attendee record.
  • An Attendee record wasn’t created when a matching Contact record didn’t exist.
• The BT Rule object now includes the Extend Visibility to Account and Extend Eligibility to Account fields. By default, these fields will be added to the page layout. The Extend Contact Visibility to Account (bt_base__Extend_Contact_Visibility_To_Account__c) field was deprecated.
  • Field Label: Extend Eligibility to Account
    • API Name: bt_base__Extend_Eligibility_To_Account__c
    • Data Type: Checkbox
    • Description: Indicates whether the contact is eligible to register for the item based on eligibility within the bucket account of this contact. If one of the contacts is evaluated as eligible, all contacts within the account are eligible. The default value is false (unchecked).
  • Field Label: Extend Visibility to Account
    • API Name: bt_base__Extend_Visibility_To_Account__c
    • Data Type: Checkbox
    • Description: When checked, visibility will be extended from one contact who meets the rule criteria to all contacts within the account. When a contact meets the criteria, all contacts in the account gain access.

Webapp Release

Bug Fixes

• The user experience between the AttendeeLink and the Event URL for sold-out Events now matches. Previously, the Event URL showed a “Sold Out” banner for sold-out Events, but the AttendeeLink didn’t for non-pending Attendees. (Known Issue: 000003428)
• The UTF-8 character “⋮” has replaced the HTML entity code ⋮ in the Event's page title. Previously, the page title showed ⋮ instead of the default separator "⋮".
• The field labels in the Contact information section of checkout were updated to rich text fields so users can add HTML tags like
  to Data Dictionary Entries. (Known Issue: 000003516)
• If an Event using the Dynamic or Tabbed UI has an Event Item with Type = “Other” (Product) with an Image URL and Alternative Text for Visual Impairment, then the Event Item’s Public Item Name will appear on the Event registration page. Previously, the Alternative Text for Visual Impairment text appeared instead of the Public Item Name. (Known Issue: 000003316)
• Users can now register for multiple Events back-to-back without triggering an error. Previously, the registration processes failed on the Event webpage after a user tried registering for a second Event after completing a prior registration. (Known Issue: 000003564)

Event Registration Submissions (ERS)

• When an Attendee uses Stripe Checkout to check out, the resulting Event Registration System (ERS) record will be processed and completed correctly. Previously, there was an issue during checkout with Fee recalculations, which caused duplicate ERS records to be created despite completed and captured Transactions appearing in Salesforce and Stripe. (Known Issues: 000003534 and 000003175)

Forms

• If a Form includes a Form Element with Type = “Multi-Select Picklist” and a conditional question, users can select the value with the conditional question and see the conditional question. Users can also select multiple values, including the value with the conditional question, and see the conditional question. Previously, when a user selected the value with the conditional question, the conditional question disappeared, preventing the user from completing the Form. (Known Issue: 000003338)
• If an Event’s Form has many Form Elements (questions), Attendees who register for the Event will see all the Form Elements, ensuring they can answer the required questions. Previously, Attendees didn’t see all the questions on the Form so some of the required information was missing from their Attendee records.

Enhancement

• If an Event’s Form has many Form Elements (questions), Attendees who register for the Event will see all the Form Elements, ensuring they can answer the required questions. Previously, Attendees didn’t see all the questions on the Form so some of the required information was missing from their Attendee records.
• The following tags for text that is intended to carry semantic weight or emphasis were updated to meet accessibility requirements.
  • < b > to < strong >
  • < i > to < em >

Field/Layout Updates

New

• Object: BT Rule
  • Field Label: Extend Eligibility to Account
    • API Name: bt_base__Extend_Eligibility_To_Account__c
    • Data Type: Checkbox
    • Description: Indicates whether the contact is eligible to register for the item based on eligibility within the bucket account of this contact. If one of the contacts is evaluated as eligible, all contacts within the account are eligible. The default value is false (unchecked).
  • Field Label: Extend Visibility to Account
    • API Name: bt_base__Extend_Visibility_To_Account__c
    • Data Type: Checkbox
    • Description: When checked, visibility will be extended from one contact who meets the rule criteria to all contacts within the account. When a contact meets the criteria, all contacts in the account gain access.

Old

• Object: BT Rule
  • Field Label: Extend Contact Visibility to Account
  • API Name: (bt_base__Extend_Contact_Visibility_To_Account__c)

Upgrade Instructions

Go to the Blackthorn Candy Shop to upgrade Events to the newest version.

Blackthorn has adopted Salesforce’s managed package installer to simplify the installation process. The installer will confirm that the correct Base Package and Payments versions are installed before upgrading Events.

For step-by-step instructions, click here.

Important Definitions

Breaking Change

A breaking change is a significant change that requires a package upgrade to see the update.

Off-Cycle or Hotfix Release

A hotfix is a release that corrects a problem that impacted extensive functionality.

BT Salesforce Release

The following applies to a Salesforce release.

• Salesforce fixes REQUIRE a package upgrade to see and utilize the fixes/enhancements.
• Only users with a System Administrator profile or the ModifyAllData system permission can install packages.

Webapp Release

The following applies to a Webapp Release (previously referred to as a platform release).

• Webapp fixes/changes usually do not require updates to the Salesforce package.
• These updates automatically apply to all customers; you cannot opt-out.

If you have any questions or need help with testing, please contact Blackthorn Support.