This release enhances the Eventbrite to Salesforce Opportunities sync by addressing contact linking, refunds, field availability for syncing, and incorrect net sales calculations. The changes include clarifying how Primary Contact population works and what conditions can prevent relationships from being established, introducing configuration options to prevent contact linking issues, and identifying which Salesforce fields reflect refunded or deleted orders to drive Salesforce Flow triggers. The update also resolves the issue where the Eventbrite Status field was not updated during sync, and makes the Eventbrite Has Contact List and Eventbrite Opted In fields available for syncing. Additionally, the Net Sales calculation is corrected to reflect ticket price minus discounts. Finally, the absence of a Closed Lost Reason has been addressed to prevent sync failures when moving Opportunities to Closed Lost.

A new dynamic capability has been introduced for the company field mapping in the Salesforce integration with Eventbrite. Eventbrite's canned fields no longer include the company name and it is now captured as a custom question. You can use pattern or merge fields in the Default Value for the company mapping to derive the name from incoming Eventbrite data, for example [FirstName] [LastName] or [EventName] [LastName]. This feature preserves backward-compatible behavior by continuing to map the old field via Field Mappings. If needed, there are considerations for how this should apply during Account creation for Contacts, and a separate ticket will determine the best approach in that context.

This release addresses an issue where merging duplicate contacts could leave an incorrect record ID in the member compound key, potentially linking members to deleted or incorrect records. When the correct contact is selected as the master during a merge, the member's link is updated accordingly. If the incorrect contact is chosen as master, the system now prompts you with manual cleanup options to resolve the linkage. During the next synchronization, if the wrong contact has been deleted, the member will re-link to the correct contact automatically. The update also adds safeguards for scenarios where no matching contact exists by email after a wrong deletion, helping prevent orphaned references. Additional notes indicate that the contact lookup is configured to set the related field to null on delete and that orphaned references may require manual cleanup or a full resync with Rematch enabled.

The Manage Mailchimp Members Flow configuration editor (mcPropertyEditorMember LWC) has been updated so that tag-related options are no longer inside the Advanced accordion. Tag details, including the Select Mailchimp Tags dual listbox and the Dynamic Tags input, are now in their own collapsible accordion section labeled Tags. The Tags section is positioned above the Advanced section. The Advanced section now contains only Member Status, Resubscribe Members (when applicable), and Bypass Internal Queue. Modified file: force-app/main/default/lwc/mcPropertyEditorMember/mcPropertyEditorMember.html. This update improves UX by separating tag configuration from advanced options and making the Tags section easier to find without expanding Advanced.

Mailchimp events are customizable activities that contacts engage in beyond email interactions, and tracking them has been implemented to capture these signals in Salesforce. These events support market analysis, segmentation, and triggering automations, helping you monitor registrations and categorize contacts based on their product interactions to improve audience targeting and personalized marketing. This update enables you to track customizable Mailchimp events, analyze and segment based on those events, and automatically trigger workflows when events occur.

A new validation capability has been introduced to warn users when segment names contain brackets or semicolons, which can cause sync issues with Campaign Monitor API field keys. This improvement introduces a dedicated error code CM4SF_SEGMENT_INVALID_NAME and applies to batch jobs in ImportListViewBatch.cls and ReportToListBatch.cls, where the start method checks Segment_Name__c for invalid characters and, if found, logs a maintenance log warning and records a warning in import results without blocking the import, ensuring backward compatibility. The warning provides details including the segment name and import title, with occurrence tracking to surface repeat issues. The change is backwards compatible, and existing imports will continue to run unblocked. A maintenance log entry and a corresponding import results warning will appear. Unit tests have been added or updated to cover these scenarios. For future improvements, UX-based validation in the Import Wizard UI is planned to proactively prevent users from entering invalid characters. Acceptance criteria include the new error code CM4SF_SEGMENT_INVALID_NAME, validation added to ImportListViewBatch.cls and ReportToListBatch.cls, the maintenance log with occurrence tracking, the warning appearing in import results, existing imports continuing to run, and unit tests updated.

An improvement has been implemented to bulkify the SubscriberImportTriggerHandler to prevent SOQL governor limit errors when deleting multiple Subscriber_Import__c records. Previously, the deleteSubscriberImports method performed a SOQL query inside a loop and used a break statement, which could lead to governor limit issues when deleting many imports and would only process the first segment. Similarly, the deleteScheduledJobs method queried CronTrigger inside a loop for each deleted import, increasing governor limit risk during bulk deletions. The new approach collects all import IDs into a set and executes a single bulk query of Subscriber_Import__c records using WHERE Id IN :importIds, processes all segments without breaking after the first, groups work by listId to minimize API calls, and calls a future method for each unique listId/segmentName combination. For scheduled jobs, the updated logic gathers unique Run_As__c IDs, queries CronTrigger in bulk using CronJobDetail.Name IN :jobLabels, builds a map for fast lookup, and processes deletions in memory. These changes reduce governor limit risk, preserve the existing cleanup semantics (field cleanup and segment deletion queue), and improve performance when deleting large numbers of imports. Testing requirements include validating deletion of a single import with a segment, deleting 200 imports with segments to confirm no governor limit errors, deduplication when multiple imports share the same segment name, handling of different segment names, ensuring imports without segments are skipped, and verifying scheduled job cleanup with multiple imports. Acceptance criteria include: no SOQL queries inside loops, processing all imports with segments rather than only the first, no governor limit errors when deleting 200+ imports, preservation of existing functionality, and maintained or improved test coverage.

A bug was reported where the Check Matching Rules action would return no matches for Person Accounts, even when a matching record existed outside of the EB4SF application. This issue occurs in environments with Person Account-enabled orgs and active Salesforce Duplicate Rules for Person Account objects, where EB4SF Matching Rules are used for incoming attendees and order contacts. The issue has been escalated for investigation, with plans to update the code to ensure the Check Matching Rules flow correctly identifies matching Person Accounts. This work aims to improve the reliability of the matching process for Person Accounts in this release.

StripeStatusBatch now always maps Stripe subscription IDs to their status, ensuring the Stripe_Status__c field is updated for all subscriptions regardless of status. In addition, IDs are only added to the missing licence candidate set when a completed checkout exists and the status is not canceled. This prevents canceled subscriptions from being repeatedly logged as missing, while still allowing existing licences to store Stripe_Status__c = canceled. The update is implemented in the StripeStatusBatch.cls file at b12-force-base/main/default/classes/StripeStatusBatch.cls.

Updated seven Emma invocable actions with Agentforce-optimized annotations to improve AI agent understanding and usage. All seven invocable actions, including AddContactToSubscriberList.cls, AddLeadToSubscriberList.cls, DeleteContactFromSubscriberList.cls, DeleteLeadFromSubscriberList.cls, UnsubscribeContactFromSubscriberList.cls, UnsubscribeLeadsFromSubscriberList.cls, and ImportWizardAction.cls, have been enhanced. Improvements include AI-focused descriptions in the @InvocableMethod annotations, mandatory parameter flags added via required=true on InvocableVariable parameters, and enhanced variable descriptions with example values and AI guidance. A consistent iconName has been applied across all actions, and a new customer documentation resource documentation/Agentforce Setup.md has been created, featuring step-by-step Agent Action setup instructions, parameter configuration guidance, example prompts, and troubleshooting tips.

Invocable Actions have been updated to better support Agentforce AI agents with richer descriptions and clearer guidance. InvocableDiscount.cls now includes a description in the @InvocableMethod annotation to explain when the AI should use the action, and the InvocableVariable descriptions for Event Id, Discount Code, and Percentage Off have been enhanced for clarity. InvocableCloneMappings.cls also includes a description for the @InvocableMethod annotation and improved InvocableVariable descriptions for the From Event Id and To Event Id parameters, with a note that both Salesforce Record IDs and Eventbrite Event IDs are accepted. Documentation has been expanded with a new Agentforce setup guide at documentation/Agentforce.md and an Eventbrite section added to the Confluence Agentforce Setup page. The updates reinforce key principles by providing AI-ready descriptions that explain usage, detailing how to locate IDs, including example values where helpful, and clearly marking required parameters.

The EB4SF integration now automatically inherits category, format, and subcategory metadata from parent series events for recurring Eventbrite instances when the API response does not provide these fields for child events. This enhancement improves data quality in Salesforce by ensuring recurring event instances carry the same metadata as their parent series, enabling more accurate categorization and reporting. To enable this behavior, the integration establishes a link between child events and their parent series using a series_id, detects missing metadata on generated child events, fetches the parent event when needed, and populates Category__c, Format__c, and Subcategory__c with the inherited values. Existing events with missing metadata will be backfilled as part of the update. The change is designed to be transparent to users and does not require changes to existing workflows, though it may add a small number of additional API calls to fetch parent metadata, which can be mitigated with caching.

Mailchimp invocable actions have been enhanced to be Agentforce-ready by introducing descriptive metadata annotations. The updates add descriptive metadata to the InvocableMethod annotation for the Manage Mailchimp Members action and to the InvocableVariable annotations for both actions, along with improved descriptions in the corresponding result classes. For Manage Mailchimp Members, the action now includes description, label, and required attributes; the same enhancements apply to the Manage Mailchimp Tags action. Customer-facing documentation has been created for Agentforce setup, including prerequisites, step-by-step setup instructions for both actions, topic configuration recommendations, test prompts, a troubleshooting guide, and parameter reference tables. The available Agentforce actions are Manage Mailchimp Members, which subscribes or unsubscribes people to Mailchimp audiences, and Manage Mailchimp Tags, which adds or removes tags from existing audience members. Note that Agent Actions must be configured through the Salesforce UI; GenAiFunction metadata is not supported in scratch orgs; customers require Agentforce licenses to use these features; invocable actions are included in the managed package and agent configuration is performed per org.

An enhancement has been released to render PDF documents inline in the File Preview Modal by updating the dbFilePreviewModal LWC component. The previous behavior displayed a static placeholder instructing users to Click Download or Open in Dropbox below to view this PDF. The new approach uses getShareLink with a raw=1 parameter to serve the raw PDF content directly to the browser, enabling inline viewing. The changes include: dbFilePreviewModal.html now uses an iframe to render the PDF and includes a loading state while the URL is fetched; dbFilePreviewModal.css improves iframe styling with a height of 70vh for a better viewing experience; dbFilePreviewModal.js adds PDF-specific handling in loadPreview to switch to getShareLink, introduces convertToRawUrl to convert Dropbox share links to raw format, and updates modalSizeClass to use a larger modal for PDFs. From a technical standpoint, Dropbox temporary links are download URLs, whereas share links with raw=1 serve the raw content that browsers can render. CSP trusted sites were already configured to allow framing from _.dropboxusercontent.com and _.dropbox.com. In testing, all 287 Apex tests pass, and PDFs now display inline in the preview modal.

A minor UI alignment improves consistency by aligning the Billing Details label in the dropdown submenu with the modal title. The Account Detail modal now includes a View User action that navigates to the related Salesforce User record, mirroring the Mailchimp integration, and a Make Admin action that assigns the Admin permission set to the user.

A new search capability has been introduced on the folder selection page to help users quickly locate existing folders when configuring Dropbox for Salesforce or creating a new workspace. This enhancement addresses the challenge of navigating large folder trees by enabling fast, intuitive filtering. The feature improves setup efficiency and reduces the time spent browsing folders. Acceptance criteria include implementing a user-friendly search on the folder selection page and ensuring the search remains responsive and efficient even with extensive folder hierarchies.

This release aligns the Billing Details option in the dropdown with the Account Details modal title to remove inconsistency. In the Account Detail Modal, a new View User action now navigates to the related Salesforce User record, mirroring the behavior used in Mailchimp. Additionally, a Make Admin action is introduced to assign the admin permission set to the selected user.

Billing screen improvements align the Billing Details option in the dropdown sub-menu with the Account Details modal title for a more consistent experience. In the Account Details modal, the dropdown currently includes only Unassign; we are exploring enhancements such as a View User option that navigates to the corresponding Salesforce User record (similar to the Mailchimp integration) and an option to assign the admin permission set to the user when selected.

A status-based filtering update has been introduced to the Mailchimp to Salesforce sync to ensure archived Mailchimp members no longer participate in field mappings. Archived members will not trigger Salesforce updates, preventing stale data from overwriting correct information. The change applies a status filter in the batch process, aligning with existing status handling in other batches and operating independently of the Disable_Archived__c setting. This enhancement addresses customer expectations that archived members be removed from syncing updates to Salesforce and keeps data in Salesforce accurate and up-to-date.

Link_Clicked__c on Mailchimp_Email_Activity__c has been deprecated and removed because it duplicates Activity_URL__c, which already stores clicked URLs. The field was never populated by Apex, and the UI relies on live Mailchimp API data through Activity_URL__c, which is also the source used by reports, layouts, and selectors. No data migration is required since Link_Clicked__c is unused. This release removes the field from permissions, the report type, and the field metadata, and also eliminates the remaining commented code reference in McEmailActivityBatch.cls. Reports will continue to function as they rely on Activity_URL__c, and you can run tests to verify deployment success. The change is low risk with no customer data impact, and if you have custom reports referencing the deprecated field, you may need to switch them to use Activity_URL__c.

Billing screen improvements align the modal title with the Billing Details option for a consistent user experience. The Account Detail Modal will include a new View User action that navigates to the Salesforce User record. There is also consideration to add an option to assign the admin permission set to a user directly from the dropdown, enabling streamlined admin provisioning.

The Account Details screen in the Salesforce integration has been enhanced to address issues observed in production. The available seats display now reflects the correct total, improving clarity for users. License assignment feedback has been improved to better indicate when a license is not allocated as expected. The Dropbox Admin permission set is now correctly assigned to system admins and is no longer described the same as the standard permission set. The billing portal link remains disabled as work continues on this feature.

A new batch process migrates legacy marker-file mappings to Salesforce using the Db_Folder_Mapping__c records, enabling faster lookups and more reliable path resolution without Dropbox API calls. The migration is implemented with DbMarkerFileMigrationBatch as the main class and DbMarkerFileMigrationBatchTest to ensure 100 percent test coverage. Two migration modes are available: SCAN_ONLY provides a preview of what would be migrated, and MIGRATE creates the mapping records. To run, enable the Setup Wizard option for legacy customers, and execute the migration via Anonymous Apex using DbMarkerFileMigrationBatch.startMigration('MIGRATE'). Key features include skipping org-level markers ending with .00Dxxx.sfdb, skipping private root markers containing a hyphen, preventing duplicate mappings, assigning the correct workspace to migrated mappings, and sending an email summary upon completion. Marker files remain in place after migration and pose no risk. Documentation is available in Confluence under Dropbox Migration.

Billing Screen changes introduce alignment between the Billing Details option in the dropdown and the modal title to improve consistency across the billing UI. The Account Detail modal dropdown will include a new View User action that navigates to the corresponding Salesforce User record, mirroring the behavior used in Mailchimp, and a Make Admin action that assigns the admin permission set to the user.

A number of known issues are affecting the Account Details screen. In production testing, the seat availability indicator shows 2 of 5 seats available, while the expected total is 8. The license assignment flow may not reflect a newly assigned license, and attempting to assign a user can result in an error if the user does not yet have a license. The Dropbox Admin permission set is not assigned to system admins and currently shares the same description as the standard permission set. The billing portal link is currently greyed out as this functionality is a work in progress. We will provide updates as fixes are implemented.

On the Account Details screen in production, several licensing and billing-related issues have been observed. The available seats display shows 2 out of 5 when it should be 8. When attempting to assign a user, such as Barbara, the UI does not immediately reflect the assigned license and, on retry, an error occurs indicating that a license is required. The Dropbox Admin permission set is not assigned to system admins and currently shares the same description as the standard permissions set. The link to the billing portal is currently greyed out, reflecting ongoing work in progress.

Billing functionality has been enhanced to show users their trial end date and provide access to the Stripe Billing portal. A license banner now appears at the top of the Dropbox component displaying the remaining trial days and a Subscribe Now button. A new Account Details option under Connection Settings provides access to the billing portal. The Account Details modal mirrors the dbConnectionSettings.html modal and includes a Billing Portal button at the bottom left with a close button at the bottom right. It also features a searchable table for assigning seats to Salesforce users, automatically assigns the Dropbox_Standard permission set when a seat is assigned, displays the number of available seats left with a minimum of 5 and no maximum, and shows the cost per seat as 5 USD. The Stripe Billing portal is integrated using the provided example.

A security review of the Dropbox integration has been completed to strengthen data protection and access controls within Salesforce workflows. This update enhances audit visibility and secure data handling for users syncing content between Dropbox and Salesforce.