This update enforces that Create Only is non-interactive for any mapping row with no Salesforce field mapped, across Lead, Contact, Person Account, Campaign, Opportunity, and related screens. When a Salesforce field is selected, Create Only becomes enabled, and clearing a mapped field resets it to false and disables it again. These changes apply consistently across all mapping-row UX, reducing confusion and preserving existing runtime behavior for mapped fields.

AnswersBatch now passes DuplicateRuleHeader.AllowSave = true when updating existing Contacts and Leads during Eventbrite answer synchronization, aligning with the RuleBatch path. Previously, AnswersBatch used Database.update without AllowSave, which could trigger duplicate-rule blocks even though RuleBatch had already created or linked those records via DMLQueue with AllowSave=true. Eventbrite_Answer__c updates in this batch remain unchanged unless we decide they should receive the same treatment, and Mapping validation tests remain unchanged as they intentionally use plain inserts to surface duplicates in the validation UI.

During a full event refresh, the progress indicator could display as finished while AnswersBatch was still running, causing users to review Lead or Contact fields prematurely. This release ensures the progress state remains active until AnswersBatch completes for the entire sync path, including any downstream batches. An optional label such as 'Syncing custom answers' may appear while AnswersBatch is running, and batch weight percentages are adjusted to keep progress totals coherent.

The new Eventbrite Attendee Component provides a contact-level view of events attended, with attendee, order, answers, and email data accessible in a detail panel and quick-access dropdowns. This release resolves a critical issue where refreshing table-level attendee records could trigger a Primary Sync failure; refreshes will no longer produce errors and the sync continues on schedule. A small display refinement improves readability by adding space between the component title and the records count.

Email tracking history being enabled or changed now triggers a full refresh to ensure data completeness, addressing gaps from forward-looking incremental syncing. If a full refresh of tracking history isn’t feasible, the refresh will cover all tracking data to preserve accuracy. We’re also considering exposing this refresh as an option from the Sync Now button for on-demand updates.

Previously, invocable actions required an email on the triggering object. You can now pass an email field from any related or child object in the flow, enabling subscription or tag management based on records like program enrollments or opportunities even when the source object has no email. This expands flexibility for flow-driven automation, aligning with Data Wizard capabilities and common customer use cases.

This update prevents the editor from overwriting a manually set recordId when admins provide a value and resolves a save validation error for flows triggered on non-person objects. It also exposes recordId as a visible input in the Flow Builder, enabling admins to bind it to a Flow resource such as a looked-up Contact ID. Additionally, Tags and Advanced sections are now shown consistently regardless of the triggering object, with clearer guidance on how recordId is used.

This release adds CMBatchDeleteSubscribers to the allBatches synchronization check so the primary Salesforce sync waits for delete operations started by the REFRESH AND REPLACE import to complete. This prevents race conditions and helps ensure data consistency between Campaign Monitor and Salesforce.

Mailchimp Limited now enforces read-only access for core customer-facing objects, reinforcing least privilege at both the data and UI layers. Previously only Mailchimp_Account__c was read-only, making Limited similar to Standard at the object-permission level. While the UI already hides write actions through the Mailchimp_Manage_Memberships permission, the updated object permissions prevent modifications via API, Data Loader, or custom code, enhancing overall data safety.

An enhanced workflow for the Sent and Unsubscribed activity sync now performs incremental cleanup during the synchronization process, instead of creating all records and deleting them at the end. This reduces temporary storage usage and speeds up processing for large lists, while preserving your configured retention window. Improved error handling ensures partial failures won't leave lingering records and allows the cleanup to resume automatically.

Updates preserve existing Mailchimp Batch Size custom settings when editing mcMaintenanceSettings, preventing overwrites of user added settings and potential data loss. The release introduces a user interface option to not cap repeat Email Activity, which would raise all batch sizes to 1000 for greater throughput. It also ensures that the counts of opens and clicks in Salesforce align with Mailchimp, providing a consistent cross platform view.

Previously, enabling activity, extending the retention days, or running a full refresh would download the entire Sent/Unsubscribe activity set and delete it only at the end, potentially causing storage spikes and incomplete cleanup after errors. The update optimizes the flow by performing deletions during processing in batches and improving error recovery, reducing storage usage and improving reliability for large lists. It also aims to refine how the sync keeps only the relevant records, speeding up subsequent runs.

Emails can now be filtered by archive status within Data Wizard, giving you control over which messages are included in analysis and exports. This optional filter helps you focus on active and relevant communications, improving efficiency and data accuracy.

Maintenance settings now support boolean values, enabling clear on/off configurations. A numeric slider is introduced to input values more accurately and minimize entry mistakes.

The integration now shows a clear message whenever it detects execution in a Salesforce sandbox, helping users confirm the environment and avoid confusion.

The Preview Mapping Rules modal now displays the default values, giving you clear visibility into the current configuration before you apply changes. This helps validate mappings more efficiently and reduces guesswork when reviewing setup. This enhancement applies to the Salesforce integration, streamlining the mapping workflow.

The Manage List button is now consistently enabled across all member components, eliminating instances where it appeared greyed out. This improvement streamlines workflows for managing lists within the Salesforce integration.

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.

With this release, the Salesforce Mailchimp integration updates how subscriber counts are calculated to rely on per-list member_count rather than the org-wide total_subscribers metric. Previously, the code pulled total_subscribers from the Mailchimp root endpoint (/3.0/), which counts both active subscribers and unsubscribed members and therefore overstates the deliverable audience. In practice, an example might return 29,850 total_subscribers, consisting of 21,631 active subscribers and 8,301 unsubscribed members. The new behavior uses the member_count value from each list's stats via the /lists/{list_id} endpoint and sums these values across all lists to determine the accurate total. Implementation involves replacing the org-level API call with per-list lookups, extracting stats.member_count for each list, and aggregating the results. Key differences include that total_subscribers equals active plus unsubscribed and is not suitable for campaign delivery, while member_count reflects only active subscribers. Considerations include reviewing Context7 MCP documentation for Salesforce Apex to avoid governor-limit issues. In terms of endpoints, the old approach used GET /3.0/ with total_subscribers; the new approach uses GET /lists/{list_id} and reads stats.member_count per list. Acceptance criteria require updating the code to fetch per-list stats, summing member_count across lists, ensuring the subscriber count reflects only active deliverable subscribers, considering caching for performance when multiple lists exist, and updating unit tests to reflect the new calculation.

An update strengthens converted lead protection by preventing any post-conversion updates to Leads during batch processing and by ensuring members are re-parented to the associated Contact with Lead__c cleared on conversion. This enhances reliability in scenarios where re-parenting could fail or be skipped due to race conditions or limitations, so subsequent runs no longer attempt to update converted Leads. The changes affect the Rules batch, which now skips updates to Leads when IsConverted is true, and the Email Opt-Out batch, which avoids updating HasOptedOutOfEmail on converted Leads. The Lead trigger handler already re-parents to Contact and clears Lead__c on conversion, and this behavior is reinforced. The Data Wizard may source converted Leads through user-provided List View, Report, or SOQL queries; those converted Leads are now properly handled to avoid updates. A UI warning is added to the wizard when the object is Lead and the query does not exclude IsConverted=false. Unit tests have been added to verify the updated behavior across all scenarios.

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.