Version 0.41.0.1 Release Notes

These release notes are organized into Functional Features, Updates and Bug Fixes and Technical Features, Updates and Bug Fixes.

Important Items and Upgrade Action Steps are things you should read to determine if your org needs to take an action prior to upgrading or what post upgrade steps need to be taken.
Known Issues highlights issues we recognize not functioning as expected and will be working to fix in the next release.
Functional Features, Updates and Bug Fixes captures everything in the release that have a direct impact on the Registrant or Event Manager experience. These are features or functionality utilized and noticed as part of the Summit Events App.
Technical Features, Updates and Bug Fixes captures everything in the release that is within the codebase. They impact the functionality and features of the Summit Events App, but aren’t likely noticeable from an Admin or Event Manager perspective.
Issues Closed is a comprehensive list of GitHub issues (Bugs and Feature Requests) that are closed as part of this release.

Important Items and Upgrade Action Steps

This release includes fixes for Contact Matching Mappings, logged-in user registration address mapping, and transactional email QR code rendering. Organizations using custom matching metadata, logged-in community user registration, or transactional emails with QR codes should validate those flows in a sandbox or UAT environment before deploying to production.

Post Deploy Instructions:

If your org uses Summit Events Contact Matching Mappings, review any mappings where Matching_Only__c is selected in CUstom Metadata Types and the mapped values are used only for matching and are not copied onto newly created Contact, Lead, or Person Account records.
If your org supports logged-in portal or community user registration, test registrations where the Contact record includes longer address values, full state names, or country values that may not match the restricted Registrant Country picklist.
If your org uses custom Summit Events Registration page layouts, review whether the following fields should be added to your custom layout:
- Registrant_Country_Text__c
- Registrant_Id_QR_Code__c
If your org uses transactional emails with the Registrant_Id_QR_Code__c merge field, send a test transactional email and confirm the QR code renders as expected.

Known Issues

None known as part of this release at this time.

Functional Features, Updates and Bug Fixes

Contact Matching Mapping Matching Only Flag Fix #640

Summit Events now respects the Matching Only flag on Summit Events Contact Matching Mapping custom metadata records. When a mapped field is marked as matching only, the value is used for matching but is no longer copied onto newly created Contact, Lead, or Person Account records.

This prevents matching-only data from being added to new records during the registration and matching process.

Post Deploy Instructions: Review matching metadata records where Matching_Only__c is selected and validate expected matching behavior in a sandbox or UAT environment.

Transactional Email QR Code Rendering Fix #641

The QR code generated by the Registrant_Id_QR_Code__c formula field now renders correctly in transactional emails. This allows transactional email templates that include the registrant QR code merge field to display the QR code image as expected.

Post Deploy Instructions: Test any transactional email templates that include Registrant_Id_QR_Code__c and confirm the QR code appears correctly in the delivered email.

Logged-In User Contact Address Mapping Improvements #644

Logged-in user registration has been updated to better support Contact address values when mapping Contact data onto the Summit Events Registration record. This helps prevent registration errors caused by Contact address values that are longer than the target registration fields or that do not align with restricted picklist values.

When a Contact country value does not match the Registrant Country picklist, the value can now be stored in the new Registrant_Country_Text__c field instead of blocking registration.

Post Deploy Instructions: Test logged-in community user registration with Contacts that have full state names, longer street values, postal code values, and country values that may not match the Registrant Country picklist.

Registration Address Field Limit Alignment #595

Several Summit Events Registration address fields have been updated to better align with standard Salesforce Contact address field lengths. This improves reliability when address data is copied from Contact records or used in downstream automation.

Updated registration address handling includes support for longer street, state, zip/postal, and country text values.

Post Deploy Instructions: If your org has Flows, Process Builder automation, Apex, integrations, or validation rules that reference Summit Events Registration address fields, review and test those processes after upgrade.

Technical Features, Updates and Bug Fixes

Matching Only Field Filtering

The Contact Matching logic now includes Matching_Only__c when retrieving matching metadata and removes matching-only field values before creating a new Contact, Lead, or Person Account record.

This ensures matching-only fields remain available for matching logic without being written onto newly created matched records.

Post Deploy Instructions: No administrator action is required beyond testing custom matching configurations.

Transactional Email Image Encoding Handling

Transactional email processing has been updated to correctly handle encoded image merge values, including QR code images generated from formula fields. This allows QR code image markup to be reconstructed properly during email generation.

Post Deploy Instructions: No administrator action is required, but organizations using QR codes in transactional emails should send a test email after upgrade.

Logged-In User Registration Address Mapping Logic

Logged-in user Contact-to-registration mapping has been updated to safely map and truncate address values where needed. Country mapping now validates Contact country values against the Registrant Country picklist and stores non-matching values in Registrant_Country_Text__c.

Post Deploy Instructions: No administrator action is required, but organizations using logged-in user registration should test address mapping in a sandbox or UAT environment.

Registration Address Metadata Updates

The following Summit Events Registration field updates are included in this release:

Registrant_Country_Text__c was added as a new text field.
Registrant_State_Province__c length was updated.
Registrant_State__c length was updated.
Registrant_Street_1__c length was updated.
Registrant_Street_2__c length was updated.
Registrant_Zip__c length was updated.

Post Deploy Instructions: If you use custom page layouts, add the new Registrant_Country_Text__c field where helpful for visibility and troubleshooting.

Unit Test Updates

Unit tests were updated for contact matching and transactional email behavior to support the fixes included in this release.

Post Deploy Instructions: No action required.

Issues Closed

#595: Should we align Summit Events Registration Address field text limits to Salesforce Contact field? It can create issues if Flows are involved.
#640: [BUG] - The Matching Only flag is not respected with the Summit Events Contact Matching Mappings within the Custom Metadata Types
#641: [BUG] QR code not rendering in transactional emails
#644: [BUG] - Contact User Mapping to Registration Error

Have a question or need support?

The best place to ask questions or troubleshoot Summit Events App is the Summit Events App Trailblazer Community group. If you have a feature request or found a bug, please open a GitHub Issue in the Summit Events App repository.