Alicante Bouschet - November 2025

Overview

The following article covers what's new in our Alicante Bouschet release (beginning in November 2025) to provide a detailed understanding of what's changing, how new features work, how to enable them and any additional factors your team should consider. If you're new to Practifi or our release documentation, please review our best practices for 📚 Using Practifi Release Notes.

With Alicante Bouschet, we're introducing our own Notetaker that integrates with Smart Notes and Follow-up Assistant. We're also adding AI-generated content blocks to Smart Notes, rolling out more enhancements to our Black Diamond integration and introducing several other productivity upgrades and fixes.

• Product Enhancements
  • Notetaker
  • AI Content Blocks for Smart Notes
  • Enhanced Custom Field Control for AI-Generated Smart Notes
  • Intelligence Features Page
  • Campaign Attribution Processing Notifications
  • Enhanced Email Template Selection in Send an Email Action
  • Related Record Field Access for Picklist Fields in Active Forms
  • Active Form Field Assignment Warning Fix
  • Follow-up Assistant Utility Bar Component
  • Black Diamond Integration Enhancements
    • Sync Team Assignments
    • Customizable Field Labels
    • Configurable External ID Mapping on Account Object
  • Xplan Integration Enhancements
    • Superannuation Ownership Tracking
    • Retirement Income Ownership Tracking
    • Partner Retirement Income Synchronization
  • Microsoft 365 Sync Mailbox Visibility Enhancement
  • New Project Object
  • New Objects Introduced for Internal Logging
• Resolved Issues
  • Household Name Duplication in Record Side Panel
  • Contact Point ParentId Population on Initial Contact Creation
  • Improved Handling of Late Deliverable Fulfillment
  • Process Deep Clone - Duplicate Actions Fix
  • Process Types Displaying on Incorrect Entity Stages
  • Active Form Validation – NEXT_N_DAYS Date Literal Fix
  • Incorrect Record Display in Active Forms With Multiple Sections
  • Corrected Queue Display Label in Task Assignment
  • Follow-up Assistant - Smart Note Suggestion Generation Fix
  • Black Diamond Sync Error Clearing AUM on Client Records
• Change Log

Product Enhancements

Notetaker

Practifi's new Notetaker transforms client meeting documentation by automatically transcribing and summarizing video conferences. Your team can focus entirely on client conversations while the AI captures every detail, generates structured summaries and suggests relevant follow-up actions.

The Notetaker joins meetings as an attendee, transcribes the conversation and delivers a comprehensive summary with suggested action items after completion. Users can add meeting summaries directly into Smart Notes, while Follow-up Assistant analyzes content to recommend relevant tasks and processes.

How It Works

Notetaker can be synced with Microsoft Outlook users' calendars to automatically detect and join meetings. Alternatively, users can invite the Notetaker bot to Outlook, Zoom and Google Meet events using the meeting URL. After joining, Notetaker generates a transcript that is stored in Practifi for future reference. Firms can also change the settings so the transcript is not stored.

When the meeting concludes, the AI processes the transcript to create a professionally formatted summary highlighting key discussion points, decisions and next steps. This summary automatically appears in the Meeting Summary section of the Meeting record, while Follow-up Assistant suggests relevant topics, tasks and processes based on the meeting content.

Please note: Notetaker requires Outlook calendar sync in order to automatically join meetings.

Notetaker is a part of our Practifi Intelligence add-on. If you're interested in this functionality, please reach out to your Client Success Manager or Practifi contact.

AI Content Blocks for Smart Notes

Building on the introduction of Smart Notes in our Sauvignon Blanc release, Practifi Administrators can now create dynamic, intelligent content for use in Smart Notes with AI-generated content blocks. These blocks use artificial intelligence to automatically generate personalized information based on client data like portfolio summaries, meeting talking points or regulatory updates, saving time while ensuring relevant and contextual content for every client interaction.

Admins configure AI content blocks by writing prompts in natural language to define what the AI should generate, selecting external information sources it can reference and validating results using real Client records before deploying to the rest of the team.

Please note: AI content blocks for Smart Notes are a part of our Practifi Intelligence add-on. If you're interested in this functionality, please reach out to your Client Success Manager or Practifi contact.

Enhanced Custom Field Control for AI-Generated Smart Notes

We've added a new configuration option for AI Smart Notes to give you greater control over which fields are included when your organization's CRM data is sent to our AI model.

The Include Custom Fields in CRM Data checkbox is now available in the Smart Note Settings custom setting in Salesforce Setup. This setting controls whether local custom fields are included when our AI model processes your CRM data to generate Smart Notes.

In some organizations, local custom fields have been created with API names identical to Practifi packaged fields. When our AI model encounters fields with duplicate API names, it can lead to conflicts that affect data processing and note generation accuracy. This new setting helps prevent these conflicts while giving you flexibility in how Smart Notes accesses your CRM data. 

Here's how it works:

• When the setting is enabled, the AI model includes all local custom fields in the CRM data, except those that share the same API name as standard Practifi fields. Custom fields with duplicate API names are automatically excluded to prevent conflicts.
• When the setting is disabled, all local custom fields are excluded from Smart Notes CRM data.

We recommend reviewing your organization's custom field naming conventions to ensure that local custom fields don't use the same API names as standard Practifi fields, as they will be excluded from CRM data when generating AI Smart Notes. If you notice any issues with field data in Smart Notes, check for duplicate API names in your local custom fields and consider renaming them.

Intelligence Features Page

We've added a new page to the Settings app where Practifi Administrators can manage Practifi Intelligence licenses and configure settings for Follow-up Assistant and Notetaker. Previously, Follow-up Assistant controls could be found on the Additional Features page.

This change makes it easier to manage AI-powered features in one place.

Campaign Attribution Processing Notifications

Previously, when adding contacts to campaigns in bulk with Practifi Promote enabled, users had no visibility into the status of attribution processing. After clicking Add to Campaign, the Attributed Revenue section showed 0 records, forcing manual refreshes without knowing when processing completed or if it succeeded.

We've implemented a notification system that informs users when campaign attribution processing completes for large operations (25+ contacts).

Notification Types

There are two types of notifications for campaign attribution processing:

• In-App Bell Notification:
  • Quick confirmation with campaign name and member count
  • Includes error alerts if processing encounters issues
  • Click to navigate directly to the campaign page
• Email Notification:
  • Detailed summary including campaign name, members processed, batches processed and status
  • Direct link to view attribution records

How It Works

• Automatic processing: Large operations (25+ contacts) are processed in batches to prevent Salesforce governor limit errors.
• Smart Delivery: Notifications trigger only when using the Add to Campaign button from the UI (not for CSV imports, API operations or manual record creation).
• Coverage: Works across all campaign member addition methods from Campaign records, Contacts list view and Directory. 

Enhanced Email Template Selection in Send an Email Action

Previously, the Send an Email action type in Practifi task templates and process tasks required the Developer Name of email templates, which was difficult to locate, as it could only be accessed through the Developer Console. This created challenges for client-side administrators configuring workflows.

The Email Template field now accepts both the Record ID and Developer Name of Lightning Email Templates, providing greater flexibility in workflow configuration. Either identifier can be entered when setting up a Send an Email action.

We've updated the help text for the Email Template field to the following: "Specify the Record ID or Developer Name for the Lightning Email Template you wish to send."

This improvement addresses the needs of both technical users working with data migration scripts and administrators managing workflows through the standard interface. 

Related Record Field Access for Picklist Fields in Active Forms

Picklist fields in Active Forms could not dynamically populate related record details based on the selected value. For example, selecting an account from a picklist did not automatically fill fields such as Owner or Value. This functionality was only available for Lookup fields, forcing administrators to use manual entry rather than the more intuitive picklist, reducing flexibility in form design.

Dynamic Picklist fields now support related record population in the same way as Lookup fields. When a value is selected from a picklist, related fields automatically populate with data from the selected record, improving efficiency and consistency.  

Help text for the Prefill Form Field and Prefill Lookup Location fields on the Active Form Field object has been updated to clarify support for single-record lookups and Dynamic Picklists. 

Please note: While Lookup fields allow traversing up to five levels into related records, Dynamic Picklists currently support only one level of traversal. This is due to a Salesforce platform limitation when configuring dynamic picklist fields. Administrators should plan form designs accordingly. 

Manual Step Required for Existing Practifi Organizations

Due to a known Salesforce limitation, help text updates for custom fields with lookup filters cannot be deployed automatically. After upgrading, Practifi Administrators should manually update the help text for the Prefill Form Field and Prefill Lookup Location fields to reflect the new functionality. Refer to the Change Log or contact Practifi Support for the updated help text content. 

Active Form Field Assignment Warning Fix

When mapping Active Form fields to Task OwnerId or ActivityDate in subsequent process tasks, users encountered a warning message stating "These fields had conflicting data inputs, so a single value was chosen as the saved one." This warning appeared even when the mappings functioned correctly and no Assignment Type was set, leading to confusion and unnecessary support requests.

We've removed OwnerId and ActivityDate from the predefined fields validation list. Warning messages no longer appear in Process Task Validation or during Active Form completion when mapping these fields using the "Create New Task in Process" action.

This resolves the warning issue for:

• Dynamically assigning task ownership via Active Form User lookup fields when creating new tasks in a process
• Setting fixed due dates via Active Form fields when creating new tasks in a process

Limitations

This fix is specifically scoped to the Create New Task in This Process action type and applies only to the OwnerId and ActivityDate field mappings.

Warning messages may still appear when:

• Using other action types  
• Mapping to fields other than OwnerId and ActivityDate

Please note: These warning messages are cosmetic; the underlying field mappings continue to work as expected. We're considering a broader enhancement to address all action types and mappable fields in a future release.

Follow-up Assistant Utility Bar Component

Users can now access Follow-up Assistant via a utility bar component, providing quick access to AI-powered follow-up suggestions from anywhere in Practifi without leaving the current page.

Previously, Follow-up Assistant was accessible only from the side panel on the Home page and individual Client/Prospect record pages. With this enhancement, users can now access follow-up suggestions through a convenient component that stays with them as they navigate through Practifi.

For Practifi organizations created after the Alicante Bouschet release, the Follow-up Assistant utility bar will be enabled automatically. For existing Practifi instances, administrators must add the Follow-up Assistant component.

Follow-up Assistant Notifications

Follow-up Assistant sends bell notifications when new follow-up suggestions are generated, helping ensure important action items don't go unnoticed. System notifications for Follow-up Assistant are controlled by a configurable setting that administrators can enable or disable based on the firm's preferences. This setting is available in the Settings app > Available Features > Feature Settings for Follow-up Assistant. The setting is inactive by default.

Notifications are sent to:

• The entity owner: The user who owns the Client or Prospect record for which the follow-up suggestion was generated.
• The content creator: The user who created the content (note, Smart Note or Feed post) that triggered the suggestion.

Example: If User 1 owns a client entity and User 2 posts to the Feed for that entity, both User 1 (the entity owner) and User 2 (the content creator) will receive a notification for the follow-up suggestion generated by the Feed post.

When a follow-up suggestion is generated from a standard note, Smart Note or Feed post, eligible users receive a bell notification. Clicking the notification opens the related content:

• Standard notes open in a standard Salesforce page.
• Smart Notes open in a new workspace tab for inline viewing.
• Feed posts open in a workspace tab showing the Feed page.

Black Diamond Integration Enhancements

Sync Team Assignments

Black Diamond Teams now sync as structured records in Practifi, replacing the previous delimited-text-field approach. This enhancement introduces bidirectional synchronization of team assignments between Practifi and Black Diamond, adds team-based visibility and sharing control and establishes a foundation for future multi-integration team management.

Key Benefits

• Centralized Visibility: View and manage all Black Diamond Teams in one place – Settings → Groups. This new structure supports consistent team management across Black Diamond and future integrations.
• Flexible Assignments: Assign one or multiple teams to clients.
• Bidirectional Sync: Team updates automatically synchronize between Practifi and Black Diamond for clients.
• Enhanced Reporting: Team data can now be used in reports and list views.
• Future-Ready Architecture: Enables upcoming features such as team-based sharing rules and cross-integration team management.

Key Points

• Clients can have multiple teams in both systems
• Teams accumulate when adding Group Assignments (no override)
• Manual Group Assignments in Practifi sync to Black Diamond only for Groups originally synced from Black Diamond.
• Deleting Group Assignments in Practifi removes corresponding teams in Black Diamond 

New Behavior

• Teams now exist as separate Group records in Practifi.
• Automatic bidirectional sync of team assignments for clients.
• One-way sync of team assignments for contacts (Practifi to Black Diamond only).
• Admins can view and manage teams in Settings > Groups.
• Divisions can have default team assignments inherited by clients (initial sync only).

Customizable Field Labels

We've introduced 9 new custom settings that allow firms to customize how field labels appear in Black Diamond's interface during data synchronization. This gives firms the flexibility to use their own terminology in Black Diamond instead of being locked into standard labels like Billing Address or Alternate Email. 

New Custom Settings

The following custom settings are now available for configuration in Salesforce Setup under Custom Settings > Black Diamond Integration Settings: 

Account Address Labels

Custom Setting	Default Behavior
BD Account Shipping Address Label	When blank, displays the current label of the Shipping Address field from Practifi in Black Diamond.  When populated, the custom label appears in Black Diamond's interface for this address field.
BD Account Billing Address Label	When blank, displays the current label of the Billing Address field from Practifi in Black Diamond.  When populated, the custom label appears in Black Diamond's interface for this address field.

Contact Address Labels

Custom Setting	Default Behavior
BD Contact Mailing Address Label	When blank, displays the current label of the Mailing Address field from Practifi in Black Diamond.  When populated, the custom label appears in Black Diamond's interface for this address field.
BD Contact Other Address Label	When blank, displays the current label of the Other Address field from Practifi in Black Diamond.  When populated, the custom label appears in Black Diamond's interface for this address field.

Contact Email Labels

Custom Setting	Default Behavior
BD Contact Email Label	When blank, displays the current label of the Email field from Practifi in Black Diamond.  When populated, the custom label appears in Black Diamond's interface for this email field.
BD Contact Alternative Email Label	When blank, displays the current label of the Alternative Email field from Practifi in Black Diamond.  When populated, the custom label appears in Black Diamond's interface for this email field.

Contact Phone Labels

Custom Setting	Default Behavior
BD Contact Work Phone Label	When blank, displays the current label of the Work Phone field from Practifi in Black Diamond.  When populated, the custom label appears in Black Diamond's interface for this phone field.
BD Contact Home Phone Label	When blank, displays the current label of the Home Phone field from Practifi in Black Diamond.  When populated, the custom label appears in Black Diamond's interface for this phone field.
BD Contact Mobile Phone Label	When blank, displays the current label of the Mobile Phone field from Practifi in Black Diamond.  When populated, the custom label appears in Black Diamond's interface for this phone field.

Considerations

If these custom settings are left blank:

• The system automatically uses whatever label is currently configured on each field in Practifi.
• These labels are sent to Black Diamond during sync.
• No action is required if you're satisfied with the existing field labels appearing in Black Diamond.

If custom settings are populated:

• Custom labels will appear in Black Diamond's interface when viewing synced data.
• Practifi continues to use its standard field labels.
• Custom labels are transmitted during the sync process to Black Diamond. 

Example Scenario

A firm wants Trading Email to appear as a field label in Black Diamond instead of Alternate Email.

Configuration: Set Custom Setting BD Contact Alternative Email Label to Trading Email.

In Black Diamond: When viewing a contact's email section, the label is displayed as Trading Email with the corresponding email address value from Practifi.

In Practifi: The field continues to be displayed as Alternate Email (or whatever the field label is configured as in Practifi). 

Configurable External ID Mapping on Account Object

 We've introduced a new custom setting that allows firms to configure which External ID fields on the Account object should store the Black Diamond Client Relationship ID. This enhancement provides flexibility for firms that already utilize the standard External ID field for other purposes, thereby preventing data conflicts and enabling improved reporting capabilities.

The following custom setting is now available for configuration in Salesforce Setup under Custom Settings > Black Diamond Integration Settings: 

Custom Setting	Default Behavior
External Id Account	Use this field to configure the External ID field on the Account object to store the Black Diamond Client Relationship ID. Enter the API Name of the desired External ID field.  When blank, the system defaults to the standard practifi__External_Id__c field.

Considerations

If the External ID Account custom setting is left blank:

• The system uses the standard practifi__External_Id__c field on the Account object
• BD Client Relationship ID populates this field during sync
• Existing data in this field will be overwritten 

If the External ID Account custom setting is populated with an API Name:

• The system uses the specified External ID field (e.g., practifi__BD_Client_ID__c)
• BD Client Relationship ID populates the configured field
• The standard External ID field remains unchanged, preserving existing data

Xplan Integration Enhancements

We've made several improvements to how Practifi synchronizes with Xplan, focusing on better data accuracy and more flexible ownership tracking. These changes help ensure that data remains synchronized correctly and provide more visibility into ownership information. 

Superannuation Ownership Tracking

The owner of each superannuation account can now be viewed and managed directly in Practifi. Previously, all synchronized superannuation records defaulted to 100% ownership without indicating whether they belonged to the Primary Member or Partner/Spouse. This made it difficult to accurately track primary vs. spouse superannuation holdings.

A new Related Contact field (practifi__Related_Contact__c) has been added to the Asset/Liability object, capturing ownership information during the Xplan synchronization. Permission sets have been updated to provide appropriate access to this field. Users can update this information through their customized user interface to reflect the correct owner, providing clearer reporting and more accurate financial pictures for each individual. 

Retirement Income Ownership Tracking

Similar to superannuation, ownership can now be tracked for each retirement income stream. As with superannuation, retirement income ownership wasn't being captured during the Xplan synchronization. This enhancement provides the same ownership visibility for retirement income that is now available for superannuation.

A new Related Contact field (practifi__Related_Contact__c) has been added to the Retirement Income object. During the sync, this field is automatically populated with the Primary Member information. Permission sets have been updated to ensure users have appropriate access to view and manage this ownership data.

This allows accurate assignment of retirement income to the correct household member and maintains proper records for financial planning purposes. 

Partner Retirement Income Synchronization

Similar to superannuation, ownership can now be tracked for each retirement income stream. Retirement income Synchronization has been expanded to include Partner records, not just Primary Clients.

Previously, retirement income data only flowed for the primary member in a household. Now, when a Partner/Spouse has their own retirement income in Xplan, that information will also synchronize to Practifi.

When synchronizing from Xplan, the system checks if a Partner ID exists on the Contact record and pulls their retirement income data accordingly.

When pushing updates back to Xplan, the system checks the Related Contact field on the retirement income record:  

• If the Related Contact is blank or matches the Primary Member, the data is pushed using the primary member's ID.
• If the Related Contact is the Partner, the data is pushed using the partner ID.

This ensures complete visibility into household retirement income in Practifi and maintains accurate ownership when syncing back to Xplan.

Microsoft 365 Sync Mailbox Visibility Enhancement

This enhancement addresses a security consideration in shared Microsoft 365 tenant environments. Previously, administrators could view and add any mailbox during Microsoft 365 Sync setup, regardless of permissions. This posed visibility and security risks, particularly for IT providers managing multiple client organizations within a single tenant. The system now validates permissions in real time, displaying only those mailboxes for which access has been granted.

Practifi now checks mailbox permissions using Microsoft's mailFolders API during the user search. The process unfolds as follows:

• An initial search query runs, limited to 100 potential matches (if more results are returned, the administrator adds more specific terms to refine the search).
• For the shortlisted users, the system then sends up to five batch requests—each handling up to 20 permission checks—to verify access without overloading the process.
• Only mailboxes where the authenticating admin has Read and Manage permissions are shown. This approach maintains efficiency even in larger tenants (thousands of users) and relies entirely on the Graph API, ensuring no impact from the Exchange Web Services (EWS) deprecation in October 2026. As a result, during sync configuration searches, visibility is restricted to authorized mailboxes only, supporting isolation across multiple client organizations.

Configuration Notes

• Organizations assign a dedicated Microsoft administrator account for Practifi authentication to each client organization.
• Users grant mailbox permissions to the relevant organization's administrator account through the Microsoft Admin Center (for example, Adele's mailbox appears in searches if permissions have been approved for [e-mail], whereas Alberto's does not if approval is pending).
• Tenant-level policies, including Address Book Policies and information protection barriers, are verified to support user segmentation. 

New Project Object

We've added a new Project object to Practifi to support future functionality planned for 2026. This object is currently available with basic configuration and includes an Entity Lookup field.

This early release enables clients to begin custom development work against the object that will be used for our upcoming project management features. 

New Objects Introduced for Internal Logging

As part of ongoing platform enhancements, we've introduced two new custom objects designed for internal logging purposes:

• Log Line (practifi__Log_Line__c)
• Log Transaction (practifi__Log_Transaction__c)

These objects are part of our internal logging tool and do not impact current functionality or workflows. They are included in the release notes for transparency, as they will appear in client organizations. 

Resolved Issues

Household Name Duplication in Record Side Panel

We've resolved an issue where Household names were duplicated in the side panel on custom Lightning record pages. This affected certain customized configurations but did not impact the standard product page.

We implemented a targeted CSS update to correct the global styling conflict, ensuring Household names display correctly without duplication.

Contact Point ParentId Population on Initial Contact Creation

We've resolved an issue where Contact Point records created during initial contact addition to a Household or Organization were missing the ParentId field. This occurred when the Custom Metadata Setting "Store contact details as Contact Points" was enabled and contact details (phone/email) were entered during Contact creation. 

The ParentId was populated only after subsequent updates to contact details. This caused visibility issues for non-admin users due to sharing rule dependencies.

We updated the New Record - Household/Organization - Member flow to populate the contact's AccountId with the Household Entity Id during creation. Contact Point records now immediately receive the correct ParentId value, ensuring proper data relationships and sharing rule functionality from the start. This applies to all options in the "When a contact details field is updated" custom setting.

This fix will be deployed automatically with the Alicante Bouschet upgrade; no additional action is required.

Improved Handling of Late Deliverable Fulfillment

When Deliverables configured with "Treat it as overdue" were fulfilled late, the system calculated the next due date in the past, which prevented the automatic creation of reminder tasks. This caused Deliverable workflows to stop, leaving users without notifications to complete upcoming fulfillments.

Now, when a Deliverable is fulfilled late and the next due date falls in the past, the system automatically creates the fulfillment task immediately. A system notification is sent to alert users to prioritize the overdue Deliverable. Multiple Deliverables can now be fulfilled on the same day without the workflow getting stuck.

Example:

• A monthly Deliverable that is due on July 7th is fulfilled on August 10th.
• The Next Due Date is calculated as August 7th (already past).
• The system creates the August fulfillment task immediately on August 10th.
• A system notification is sent to alert users to the late fulfillment.

The Last Fulfillment Date field on the Deliverable record page is now read-only for non-admin users to prevent accidental disruption of the workflow.

Please note: Modifying the Last Fulfillment Date manually to a date significantly earlier than the Next Due Date may cause the Deliverable workflow to halt. Deliverables should be fulfilled through standard task completion rather than by manually adjusting fulfillment dates.

Process Deep Clone - Duplicate Actions Fix

When a process was deep cloned, any other processes with actions that referenced it would also duplicate those actions. This meant the referencing process ended up with two actions, one pointing to the original and another to the new copy. This behavior was unintended and caused confusion in workflow configurations.

Deep cloning now works as an isolated operation. Only the cloned process is affected, and other processes keep their original action references without duplication. This ensures processes can be cloned without unexpected changes to related workflows.

Process Types Displaying on Incorrect Entity Stages

Previously, Process Types and Task Templates configured with "Related To: Client" were appearing on entity records regardless of their actual stage. This meant client-specific processes would incorrectly display on prospects, firms in acquisition stages, and other non-client entities.

We've updated the underlying mapping logic to properly recognize Household entity acquisition stages. Missing stage mappings have been added to ensure the system correctly identifies which Related To options should be available based on the context record. These mappings complement the existing Individual and Organization acquisition stage mappings, completing the stage recognition logic across all entity types.

Process Types and Task Templates now appear only when launched from entities matching their configured "Related To" criteria. This ensures:

• Client-specific processes appear only on actual Client records.
• Business Development processes appear only on entities in corresponding acquisition stages.
• Cleaner, more relevant process selection lists when working with different entity types.

This enhancement applies universally across the platform, including the Start a Process action, the New Task from Template action and Follow-up Assistant.

Active Form Validation – NEXT_N_DAYS Date Literal Fix

Validation rules using the NEXT_N_DAYS date literal were not working correctly in Active Forms. When conditions like “Greater Than NEXT_N_DAYS:30” were applied, the system incorrectly allowed dates beyond the specified limit instead of blocking them with a validation error.

We resolved a number conversion issue in the Active Form validation logic. The NEXT_N_DAYS date literal now works as intended alongside other date literals (TODAY, TOMORROW, THIS_MONTH), correctly preventing form submission when dates exceed the configured threshold.

This fix applies to both pinned and bespoke Active Form fields across all process types.

Incorrect Record Display in Active Forms With Multiple Sections

Active Forms with multiple sections displayed inconsistent behavior in lookup fields. Each subsequent section was configured to become visible when a field in the previous section was set to a particular value. While the lookup field in the first section correctly displayed records related to the underlying entity in context, subsequent sections displayed records from across the entire organization rather than filtering to the relevant entity. This required users to refresh the browser to see properly filtered results.

We updated the visibility logic to ensure lookup fields consistently display only records related to the underlying entity in context across all form sections, eliminating the need to refresh the browser to load correct data.

Corrected Queue Display Label in Task Assignment

When assigning tasks to queues through bulk edit actions or when creating task templates, queues were incorrectly labeled as groups in the assignment dropdown. This caused confusion, particularly in organizations where groups and queues share the same name, making it unclear whether tasks were being assigned to the intended queue.

The assignment dropdown now correctly displays queues with the label "Queue" instead of "Group" across all task interfaces, including:

• Mass Edit action in data tables (e.g., Data Management app - Tasks table)
• New Task (from template) Global Action
• Create Task Template

This provides a clear visual distinction between queues and groups, ensuring accurate task assignment.

Please note: This fix currently applies only to the Task object. Other objects, such as Processes, Assets/Liabilities and similar records, still display both queues and groups with the "Group" label. A comprehensive fix across all affected objects is planned for a future release.

Follow-up Assistant - Smart Note Suggestion Generation Fix

We fixed an issue where Follow-up Assistant failed to generate suggestions from Smart Notes that had previously worked. When users refreshed Smart Notes after making updates, Follow-up Assistant didn’t generate new suggestions, even for notes that had worked before.

We have now updated the evaluation logic to correctly process Smart Note changes, restoring suggestion generation for both new and updated notes.

Black Diamond Sync Error Clearing AUM on Client Records

We resolved a critical issue in the Black Diamond integration that could cause Assets Under Management (AUM) values to be incorrectly cleared to $0 on client records when sync errors occurred.

When the Black Diamond sync encountered certain errors, the system incorrectly marked unprocessed assets as disposed. This caused the following issues:

• Asset values reset to $0
• Client and Service AUM cleared to $0
• Client segments were miscategorized (since segments are based on AUM)
• Data required manual restoration

The issue occurred sporadically when the sync process hit errors such as "Batchable instance is too big" or JSON parsing errors. These errors were building up in the system's batch state, preventing proper error handling and triggering the incorrect asset disposal.

We've improved how the system manages batch state during synchronization by relocating logging to the execution method. This prevents errors from accumulating and ensures that sync errors no longer result in asset values being incorrectly cleared. 

Change Log

Several product areas have been altered to implement the features and enhancements in this release. The table below consolidates these updates, making it easier to understand the release’s changes as a whole.

🔧 Implementation Details The product areas below have changed as a part of delivering these enhancements. If you’ve customized them, you won’t receive the changes automatically. A copy of the updated item will be made available in your Practifi instance. You can either replicate the changes or switch to the updated item and replicate your customizations.
Product Area	Feature/Enhancement	What's Changed?
Active Form Field	Enable Related Record Field Access for Picklist-Type Active Form Fields	Updated help text for Prefill Form Field and Prefill Lookup Location fields on the Active Form Field object to clarify support for single-record Lookup and dynamic Picklist fields. Please note: For existing Practifi organizations, this help text update requires manual implementation due to a Salesforce limitation with custom fields that have lookup filters. New organizations will receive these updates automatically. Help text added (manual update required for existing organizations): Field: Prefill Form Field Help Text: Which field in the Active Form will be used to capture the prefill record? Single-record Lookup and dynamic Picklist fields are supported, but not multi-record. Field: Prefill Lookup Location Help Text: To prefill this form field with a value from another record, first specify the field used to locate that record. This field can be a Lookup or dynamic Picklist in the Active Form itself, or a field captured on the Task that the form appears within.
Asset/Liability	Superannuation Ownership Tracking	A new Related Contact field (practifi__Related_Contact__c) has been added to the Asset/Liability object for superannuation accounts. This allows users to view and manage ownership details directly in Practifi during syncs, improving visibility for primary members and partners/spouses. Permission sets have been updated for access.
Black Diamond Integration Custom Settings	Customizable Field Labels	We introduced nine new custom settings that allow firms to override standard field labels in Black Diamond-related page layouts. This enables firms to apply their own terminology for better alignment with internal language. New Custom Settings: BD Account Shipping Address Label BD Account Billing Address Label BD Contact Mailing Address Label BD Contact Other Address Label BD Contact Email Label BD Contact Alternative Email Label BD Contact Work Phone Label BD Contact Home Phone Label BD Contact Mobile Phone Label Behavior: If a custom setting is blank, the standard label remains unchanged. If a custom setting is populated, the custom label replaces the standard label across all relevant Black Diamond layouts.
Black Diamond Integration Custom Settings	Configurable External ID Mapping on Account Object	New Custom Setting Added External Id Account: Allows firms to specify which External ID field on the Account object stores the Black Diamond Client Relationship ID. This provides flexibility in mapping the correct identifier for integration purposes. Help Text Update Added descriptive help text to the External Id Contact custom setting (introduced in the previous release) to clarify its purpose and usage.
Contact Point Object	Contact Point ParentId Population on Initial Contact Creation	The flow now assigns the Household Entity Id to the Contact's AccountId field during Contact creation. This ensures Contact Point records are created with the correct ParentId immediately. Action Required: If you have customized this flow locally, you will need to manually apply this update to ensure Contact Points are linked correctly.
Core Platform	New Project Object	Added a new Project object with an Entity Lookup field to support future project management functionality.
Deliverable	Deliverable Fulfillment - Late Completion Handling	Last Fulfillment Date field on the Deliverable record page is now read-only for non-admin users. Help text added: "Last Fulfillment Date is auto-calculated on deliverable fulfillment. To modify, enable 'Allow Fulfillment Date to be Modified' in the deliverable type and update through the task sidebar under Deliverables."
Follow-Up Assistant	Utility Bar Component	Follow-Up Assistant is now available as a utility bar component, providing access to follow-up suggestions from anywhere in Practifi. New clients receive this automatically; existing clients need to manually add the component via App Manager.
	System notifications for Follow-Up Assistant	Added configurable notification setting in Settings app Available Features Feature Settings for Follow-up Assistant. When enabled, entity owners and content creators receive bell notifications when new follow-up suggestions are generated. The setting is inactive by default.
Group Object	Black Diamond - Team ID Management	Stores Black Diamond Teams as individual records
Group Assignment		Junction object linking Teams to Entities, Contacts, and Divisions
Settings app - Groups tab		Groups tab added to Settings app Groups list view with columns: Name Group ID (Z-number) Type Group Assignments related list on Group records "New" button to manually create Group Assignments
Internal Logging Tool	New Objects Introduced for Internal Logging	Added two new custom objects for internal logging purposes:   Log Line (practifi__Log_Line__c)   Log Transaction (practifi__Log_Transaction__c) These objects are for internal use only and do not impact existing functionality.
Processes & Tasks	Enhanced Email Template Selection in Send an Email Action	Send an Email Action object – Email Template field Help text updated to: "Specify the Record ID or Developer Name for the Lightning Email Template you wish to send."
Retirement Income Object	Retirement Income Ownership Tracking	A new Related Contact field (practifi__Related_Contact__c) has been added to the Retirement Income object. This allows users to view and manage ownership details directly in Practifi during syncs, improving visibility for primary members and partners/spouses. Permission sets have been updated for access.