Overview
The following article covers what’s new in our Blaufränkisch release (beginning in February 2026) 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.
Blaufränkisch introduces powerful AI-driven administrative tools with Smart Component Builder, streamlines entity creation with the new Create an Entity wizard, expands Smart Notes across all activity types, and provides enhanced automation for Black Diamond syncing and improved migration capabilities.
-
Product Enhancements
- Smart Component Builder
- Create an Entity Wizard
- Automated Bulk Sync for Black Diamond
- Black Diamond Portfolio Deletion Handling
- AUM Calculation Enhancements (All Integrations)
- Enhanced Prefilling and Event Creation in Active Forms
- Practifi Intelligence Subscription Monitoring
- Smart Notes Migration Tool
- Smart Notes Supported in Tasks and Calls
- Categories for Smart Notes, Templates, and Content Blocks
- Pin Smart Notes to Lists
- Manage Calendar Connections for AI Notetaker
- Enhanced Field Audit Trail in Practifi Protect
- Microsoft 365 Multi-Tenant Integration
- Styling Change to Read-Only Checkboxes
- Resolved Issues
- Blaufränkisch Minor Release - April 2026
- Change Log
Product Enhancements
Smart Component Builder
We’ve expanded our Admin Intelligence platform add-on with Smart Component Builder, an AI-powered tool that lets administrators create custom Practifi components (tiles and record lists) using natural language, transforming complex technical configuration into simple conversation.
Previously, building custom components required deep Salesforce knowledge, including writing JSON syntax and navigating technical settings. This created barriers for administrators who wanted to customize their team’s experience but lacked technical expertise.
With Smart Component Builder, administrators describe what they want in plain language, and the system automatically generates the configuration. Smart Component Builder supports creating and editing data tables and tile rows, with more component types coming in future releases.
Practifi Administrators can access Smart Component Builder from the Settings app or via edit icons on tiles and tables, and add icons on tile rows and table selectors throughout Practifi.
The interface features a split-panel design: chat with the AI on the left while seeing a live preview on the right. As you refine requirements through conversation, the preview updates in real time. You can also use voice input to describe components hands-free.
Key Capabilities
Conversational Building – The AI guides you step by step rather than requiring everything in one prompt. Add filters, columns, actions, and formatting iteratively. The system asks clarifying questions to ensure it builds exactly what you need.
Edit Throughout Practifi – Click the edit icon on any tile or table (or the add icon on tile rows and table selectors) to open it in Smart Component Builder. Make changes and save—your updates appear immediately across all pages with no additional configuration.
Manual JSON Editor – Technical users can make quick adjustments using the built-in JSON editor, which provides formatting, validation, and error detection. No need for external tools.
Safe Editing – When editing standard Practifi components, the system automatically creates a clone to preserve customizations and prevent override during upgrades. Component relationships update automatically.
Restore Original – If changes don't work as expected, the Restore Original function reverts the component to its configuration at the start of your editing session.
For components created from edit icons, changes appear immediately. For components built from scratch, Smart Component Builder can add tiles or tables directly to existing rows or table viewers for you. However, if you want these components to appear on a record page, you’ll need to add them yourself using Lightning App Builder.
Smart Component Builder makes component customization accessible to more administrators, enabling faster iteration as business needs evolve. The conversational interface provides an entry point for learning, while the JSON editor helps build deeper platform knowledge.
To learn more, see Understanding and Using Smart Component Builder.
Smart Component Builder is part of the Admin Intelligence add-on. Contact your Client Success Manager for more information.
Create an Entity Wizard
We’ve introduced the Create an Entity wizard, a streamlined workflow that consolidates entity creation and lifecycle promotion into a single, guided experience, significantly reducing the number of clicks required.
Previously, bringing new clients into Practifi required navigating multiple separate actions: creating a Household or Organization record, then running the Promote to Prospect and Promote to Client workflows. This fragmented approach required you to remember which steps you’d completed, return to the records to run additional actions, and complete the same entity-creation process multiple times when entering several new clients.
With the Create an Entity wizard, you can now complete the entire journey—from initial entity creation through full client promotion—in one continuous workflow. The wizard walks you through each step with clear progress indicators, smart defaults, and embedded promotion flows, ensuring you capture the right information while saving significant time.
Guided Multi-Step Experience
The wizard provides a structured journey through entity creation:
- Select Entity Type and Lifecycle Stage: Choose whether you’re creating a Household, Organization, or Individual, then select where they fall in your client lifecycle (such as Prospect or Client). Your lifecycle stage selection determines whether promotion flows are included—selecting Client means you’ll complete the Promote to Client action within the same wizard session.
- Enter Entity Details and Members: Capture core information about the entity, with fields that adapt to your entity type selection. For Households, member names automatically generate the household name (for example, “Smith, John & Jane”). For Organizations and Individuals, enter the relevant identifying information.
- Add Definitions and Topics: Classify the entity using Topics for categorization, and use Definition fields such as Client Segment or Influencer Segment. These classifications help with reporting and may trigger specific workflows in your organization.
- Complete Promotion Flows (if applicable): If you selected a lifecycle stage requiring promotion, the wizard embeds the Promote to Prospect and Promote to Client flows directly into the experience, eliminating the need to return later to complete these steps separately.
Smart Field Management
The wizard doesn’t overwhelm you with every possible field at once. Essential fields appear by default, while additional fields are available through an Add menu, allowing you to pick the fields you want to capture data for.
Member Management for Households and Organizations
For Households and Organizations, a Members section allows you to add the people who belong to the entity. Every entity includes a primary member by default, and you can add additional members by selecting relationship types (such as Spouse/Partner, Dependent, or Employee). Each member card can be expanded or collapsed, and household names update automatically as you enter member information.
Success Screen with Quick Actions
After completing all steps, the success screen confirms what was created and provides immediate next actions. You can go directly to the entity’s record page to continue working, click Create Another to immediately start a new entity, or simply close the wizard.
Global Accessibility
The Create an Entity wizard is available as a global action, accessible from anywhere in Practifi through the Global Actions menu. This means you can create entities without first navigating to a specific page, streamlining your workflow regardless of where you’re working in the platform.
The Create an Entity wizard transforms entity creation from a fragmented, multi-step process into a single, efficient workflow that saves time and reduces the cognitive burden of remembering which actions you’ve completed.
To learn more about using the wizard, see Creating Entities Using the Create an Entity Wizard.
Adding the Create an Entity Global Action
If your organization has customized the Global Actions menu, you can add the Create an Entity action by doing the following:
-
In Salesforce Setup, use the Quick Find search to search for and select Publisher Layouts.
-
On the Publisher Layouts page, click the Edit link next to Global Layout.
-
On the Global Layout page, select Mobile & Lightning Actions.
-
Drag and drop the Create an Entity action into the Salesforce Mobile and Lightning Experience Actions section.
- Click Save.
Automated Bulk Sync for Black Diamond
We’ve introduced automated bulk processing capabilities for Black Diamond sync operations, dramatically reducing onboarding time for firms transitioning large volumes of client data into Practifi.
Previously, syncing large volumes of records (for example, 300+ clients during advisor onboarding) required manual, screen-by-screen interaction with the Black Diamond sync flow. This process could take weeks to complete, creating significant delays during critical onboarding periods.
With this enhancement, technical users can now automate the sync process programmatically using a new screenless version of the Send to Black Diamond flow. The flow accepts a single record ID as input and can be invoked through Apex, Salesforce Flows (as a subflow), or Salesforce Process Builder (via a Flow action), enabling batch processing of hundreds or thousands of records. The flow processes records using the same reliable logic as the original manual flow, including data mapping, Black Diamond record creation, and External System Item creation. Black Diamond IDs are stored in the External System Item object for tracking and verification. This automation reduces onboarding time from weeks to days.
Important Considerations:
- Individual Record Processing: The flow processes one record per invocation. The Black Diamond API does not support bulk operations, so automation must loop through records and invoke the flow individually for each one.
- Error Monitoring & Verification: Since this flow runs in the background without a user interface, errors are not displayed to users. We recommend using the External System Item object and your existing Salesforce monitoring practices to verify successful syncs. Records without Black Diamond IDs or with error details may require investigation.
For more information, see our article on Using Black Diamond Automated Bulk Sync.
Black Diamond Portfolio Deletion Handling
We've enhanced how Practifi handles deleted Black Diamond portfolios and strengthened the accuracy of AUM calculations to ensure your client data remains clean and your reporting stays reliable.
Previously, when a Black Diamond portfolio was deleted, associated assets remained linked to clients in Practifi, resulting in orphaned records with stale dates that could skew AUM calculations and create confusion about client holdings.
With this update, when a Black Diamond portfolio is deleted, associated assets and liabilities are automatically marked as Disposed in Practifi. This applies to both Portfolio-based and Client Relationship-based integration models. Disposed assets are retained for historical reference but excluded from AUM calculations, ensuring your reporting reflects only active client holdings.
AUM Calculation Enhancements (All Integrations)
To ensure data consistency and accurate reporting across all scenarios, we've enhanced seven AUM rollup jobs to exclude assets in these non-active stages:
- Disposed
- Draft
- Declined
- Did Not Proceed
- Potential
Now, only assets with stages of Owned, Application, or Financed are included in AUM calculations.
Rollup Jobs Updated
-
Core Product:
- AUM To Service
- Annual Revenue To Service
- AUM To Financial Product
- Number of Assets
-
Superannuation:
- Member Account to Value
- Total Member Accounts
- Active Member Accounts
This enhancement ensures your AUM reporting accurately reflects your clients' active assets, eliminating confusion caused by historical or disposed holdings and supporting reliable business analytics.
Please note: If your firm uses an integration that does not populate the Stage field on Asset records (e.g., Orion, Tamarac), assets with a blank Stage will be excluded from AUM calculations. Contact your Client Success Manager or Practifi contact to discuss options for your environment.
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.
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.
This enhancement ensures your AUM reporting accurately reflects your clients' active assets, eliminating confusion from historical or disposed holdings and supporting reliable business analytics.
Enhanced Prefilling and Event Creation in Active Forms
We’ve introduced two complementary enhancements to Active Forms that provide greater flexibility and control when creating events and prefilling form fields.
Formula-Based Prefilling for All Active Form Fields
A new “With a formula” option is now available for all Active Form fields, enabling sophisticated prefilling scenarios that weren’t previously possible.
Previously, Active Forms supported prefilling fields with values from related records or static values, but couldn’t perform calculations or apply complex logic to determine default values. With this enhancement, all Active Form fields can now be prefilled using Salesforce formulas, providing complete control over default values and supporting complex prefilling logic. The formula executes when the form loads and dynamically recalculates when users change dependent field values.
Key Behaviors:
- Formulas calculate when the form loads and dynamically recalculate when users change dependent field values.
- The formula can reference fields from the Prefill Lookup Location (for example, Task record, related entities).
- This option is available for all Active Form field types and all Active Form actions.
Benefits:
- Enables sophisticated default value calculations
- Reduces manual data entry for users
- Ensures consistent default values across the organization
- Supports complex prefilling logic that wasn’t previously possible
Backend Flexibility for Event Duration
The backend event-creation logic now provides greater flexibility in specifying event duration, supporting formula-based calculations of event end times.
Previously, event creation required explicitly setting both StartDateTime and EndDateTime. This made formula-based duration calculations more complex and limited the flexibility for creating events programmatically.
With this enhancement, when events are created through Active Forms, the system now accepts either:
- End Date and Time (EndDateTime): An explicit end time for the event
- Duration in Minutes (DurationInMinutes): A duration value that the system uses to calculate EndDateTime
Key Behaviors:
- At least one must be provided (EndDateTime or DurationInMinutes). If both are missing, event creation will fail with a validation error.
- When StartDateTime and DurationInMinutes are provided without EndDateTime, the system automatically calculates EndDateTime as: StartDateTime + DurationInMinutes.
- When both EndDateTime and DurationInMinutes are supplied, the system uses the explicit EndDateTime value.
Please note: DurationInMinutes is a backend Salesforce Event field and is not directly visible or editable in Active Form layouts. Users continue to interact with StartDateTime and EndDateTime fields. The primary benefit of this enhancement is enabling formula-based prefilling, where EndDateTime can be calculated from StartDateTime plus a duration.
Benefits:
- Enables formula-based duration calculations for event end times.
- Provides backend flexibility for event creation workflows.
- Reduces the need for users to manually calculate end times.
Practifi Intelligence Subscription Monitoring
We’ve introduced automatic monitoring and notifications when Practifi Intelligence user assignments exceed purchased seat limits, helping administrators proactively manage their Practifi Intelligence subscriptions.
Previously, when a customer’s Practifi Intelligence subscription was reduced (for example, from 10 seats to 8), administrators had to manually identify and remove excess users from Practifi Intelligence license assignments. There was no system notification alerting them that the organization had exceeded its purchased seat limit, which could result in more users having access to Intelligence features than the subscription allowed.
Now, a daily scheduled job monitors the number of assigned Intelligence users against the purchased seat count. When assigned users exceed the purchased limit, the system automatically sends an email notification to administrators, alerting them of the overage and providing the current seat count (purchased vs. assigned).
What This Means for Administrators:
Practifi Administrators are proactively notified when their organization exceeds its Intelligence seat limit, allowing them to take timely action to stay within their subscription. The notification provides visibility into current seat usage, and administrators can decide which users to remove based on their organization’s needs (e.g., offboarded users or adjustments to assignments aligned with business priorities).
Email notifications are sent to users with the Practifi - Intelligence Settings - Administrator permission set. If no users have that permission set, all active System Administrators receive the notification.
The License Overview on the Intelligence Features page in the Settings app displays the assigned vs. purchased seat count, giving administrators a clear view of current usage.
Please note: The system does not automatically remove users. Administrators have full control over which users are removed from Intelligence license assignments. To learn more, see Managing Practifi Intelligence Licenses.
Smart Notes Migration Tool
Practifi has introduced a new migration capability to help firms transition from legacy note-taking methods to Smart Notes. This tool provides a centralized interface for converting existing Notes, Task Descriptions, Call Descriptions, and Event Descriptions into Smart Notes.
Many firms have accumulated valuable client information in traditional Salesforce notes or in the Description fields of Task, Call, and Event records. Previously, there was no streamlined way to convert this legacy content into Smart Notes. This migration tool eliminates the need for manual data entry or custom development work to preserve historical client notes.
How It Works:
The Migration tab—located on the Smart Notes page in the Settings app—displays four content types available for conversion:
- Notes – Standard Salesforce notes attached to records
- Task Descriptions – Content in the Description field of Task records
- Call Descriptions – Content in the Description field of logged Call records (i.e., Task records with a subtype of Call)
- Event Descriptions – Content in the Description field of Event records
Each component on the Migration tab shows a live count of records available for migration. Administrators can migrate each content type independently by clicking the corresponding Migrate button.
A pop-up window displays the exact number of Smart Notes that will be created before processing begins. When confirmed, all available records in that content type are duplicated as Smart Notes without any filtering.
The migration runs as an asynchronous background job designed to handle large volumes of data. Administrators can continue working in Practifi while the migration runs, and will receive a notification when it completes.
Please note: The migration tool is designed to handle Practifi instances of all sizes, including those with millions of records. Processing time scales with the volume of records being migrated. If your organization has a large dataset, we recommend running migrations during off-peak hours to ensure optimal performance. Each content type (Notes, Task Descriptions, Call Descriptions, Event Descriptions) runs as a separate job and can be migrated independently.
For instructions on migrating your content to Smart Notes, see our Using the Smart Notes Migration Tool article.
Smart Notes Supported in Tasks and Calls
Smart Notes can now be added to Task records and automatically created from logged call descriptions, extending Smart Notes functionality beyond Event and Entity records. This enhancement provides consistent documentation workflows across all activity types in Practifi.
Previously, Smart Notes were only available on Event and Entity records. Users logging calls or working with tasks had to rely on traditional Description fields, which lack the text formatting, AI assistance, and collaboration features available in Smart Notes. This enhancement brings feature parity across all activity types, enabling richer documentation for call outcomes, follow-ups, and task completion notes.
Key Features
Smart Notes on Task Records
The Smart Notes component is now supported on Task record pages, enabling users to create, edit, and manage Smart Notes directly from tasks. Smart Notes on tasks include:
- AI-powered content generation
- Rich text editing and formatting
- Collaboration features and version history
- View All functionality when multiple notes exist
- Full-size view in the Notes & Files tab for detailed editing
- Compact view in the right sidebar for quick reference
Automatic Smart Note Creation from Call Descriptions
When enabled, call descriptions are automatically converted into Smart Notes when a call is logged. The description content is transferred to a Smart Note and removed from the Description field, preserving the information in a more structured format. Practifi Administrators can enable or disable this behavior via a new option in Smart Notes Settings.
Smart Notes Roll-up for Tasks and Calls
Smart Notes created from Task and Call records automatically roll up to the related Entity record (such as the associated Client, Account, or Contact), allowing users to see all relevant notes in one place.
Mobile Access
Smart Notes are now accessible on the Salesforce mobile app, including for Tasks and logged Calls.
Categories for Smart Notes, Templates, and Content Blocks
Practifi now supports categories that can be applied to Smart Notes, Templates, and Content Blocks, addressing the challenge teams face when choosing the right asset from a large number of options.
Previously, teams managing large libraries of Smart Notes, Templates, and Content Blocks found it difficult to organize items and quickly locate the most relevant item for a given scenario. Without a systematic way to tag and filter content, users had to scroll through long lists or rely solely on the search function.
With this enhancement, System Administrators can define categories in a central location, and users can then assign them and filter by them across the Smart Notes experience. Administrators can create categories in the Settings app, using the Categories tab on the Smart Notes page.
The system supports two category types:
- Library categories: Used by both Templates and Content Blocks to organize reusable library content
- Note categories: Used by Smart Notes to organize client-facing notes and documentation
This separation ensures that note-level categories stay focused on client work, while library content uses its own shared taxonomy. The library category and note category systems are independent—when users create a Smart Note from a template, the template’s library category does not automatically transfer to the new Smart Note.
Pin Smart Notes to Lists
Users can now pin important Smart Notes to keep them easily accessible at the top of Smart Notes lists on related records. This enhancement addresses the need to highlight critical notes for better visibility, even as new notes are created.
How It Works:
The Pin action is available in the drop-down menu on Smart Notes cards in the following locations:
- Smart Notes List Page
- Entity records - Overview panel and Notes & Files section
- Task/Call/Event records - Notes & Files tab and collapsible Notes heading in the right-hand pane
When a Smart Note is pinned, it appears at the top of the Smart Notes list on the relevant record (e.g., an Entity or Event record page). Pinned notes display a pin icon next to the menu button for easy identification. When multiple Smart Notes are pinned, they are sorted with the most recently pinned note appearing first.
Pinning is context-specific and is tracked per record type (such as Entity, Event, or Task), so pinned Smart Notes can be surfaced at the top of the Smart Notes list for each related record.
The pin action works as a toggle: clicking Pin on a pinned Smart Note changes the action to Unpin, allowing users to remove the pinned status when needed.
Important Notes
- In the Recently Viewed section, pinned notes do not automatically appear at the top—the most recently viewed note appears first, regardless of pinned status.
- For large Smart Note libraries (1000+ notes), the page may need to be refreshed to display pin/unpin changes.
Manage Calendar Connections for AI Notetaker
A new Manage Calendars tab has been added to Notetaker settings, providing administrators with a centralized interface to view and manage calendar connections and addressing an issue where Recall Calendar IDs could be incorrectly reused across different users.
Previously, when a user’s AI Notetaker calendar connection was removed (for example, by deleting the Named Credential and clearing the Recall Calendar ID), the system could reuse the same Recall Calendar ID when a different user authenticated. This caused the first user’s calendar events to incorrectly appear in the second user’s Meeting Digest.
With this enhancement, administrators can now disconnect a user’s calendar connection directly from the Notetaker settings using the Disconnect button.
As part of this change:
- The Recall Calendar ID is properly removed from the User record when the calendar connection is disconnected.
- The system prevents a Recall Calendar ID from being incorrectly reused across different users.
- A confirmation dialog appears when disconnecting a calendar, explaining that the user must re-authenticate their calendar connection to continue using AI Notetaker.
When to Use This Feature:
Administrators can use the Manage Calendars tab to disconnect a calendar connection when:
- Troubleshooting calendar connection issues
- A user changes their email account
- A user needs to connect a different calendar
- A user departs from the organization or no longer requires the Notetaker feature
Important: Always Use the Disconnect Button
Administrators must use the Disconnect button (Intelligence Settings > Notetaker > Manage Calendars) to properly disconnect calendar connections. This ensures the calendar ID is removed from both the User record and the Recall calendar system.
Do not manually delete Named Credentials or Notetaker Calendar Accounts, as these methods do not fully disconnect the calendar from Recall and can cause synchronization issues.
Please note: After a calendar is disconnected, the affected user must re-authenticate their calendar connection to continue using Notetaker. Previously generated meeting events will remain visible on the Meetings page.
Enhanced Field Audit Trail in Practifi Protect
As part of their Spring '26 release, Salesforce has increased the Field Audit Trail limit from 60 to 200 fields per object for organizations with Salesforce Shield or a Field Audit Trail license. Practifi Protect’s Enhanced Field Audit Trail now supports up to 200 tracked fields per object, with changes retained for up to 10 years (compared with 18 months in core Salesforce).
This expanded capacity enables broader field history tracking on critical objects, particularly valuable for firms with extensive regulatory or operational audit requirements.
Our standard Field Audit Trail policy was designed around the previous 60-field limit and focused on key regulatory/operational fields. You can now extend tracking beyond the previous limit to 200 fields per object, based on your specific compliance needs.
What to Know
- Capability: No action required – this is a platform-level Salesforce change automatically available to eligible Practifi organizations.
- Configuration: Administrators can now expand Field Audit Trail coverage to track additional fields (up to 200 per object), subject to your firm's compliance and storage strategy.
Microsoft 365 Multi-Tenant Integration
We’ve introduced Microsoft 365 multi-tenant integration, enabling organizations to connect multiple Microsoft 365 tenant environments to a single Practifi instance. This enhancement addresses the complexities organizations face when managing multiple Microsoft 365 tenants, such as after an acquisition, operating distinct business units, or transitioning from legacy systems.
With this enhancement, administrators can configure multiple Microsoft 365 tenant connections within one Practifi organization. Each tenant operates independently with its own credentials, sync schedules, and user assignments, while all data flows into your unified Practifi system. Users assigned to each tenant maintain their existing Microsoft 365 environment and email addresses while contributing to a complete client view in Practifi.
Key capabilities include:
- Independent tenant configuration: Each Microsoft 365 tenant maintains separate sync settings, exclusion rules, and user assignments.
- Flexible exclusion rule hierarchy: Control data sync at user, tenant, or organization-wide levels to precisely manage what information flows into Practifi.
- Seamless post-acquisition integration: Newly acquired teams continue using their existing Microsoft 365 tenant while client data unifies in Practifi.
- Phased migration support: Run old and new Microsoft 365 tenants in parallel during transitions, allowing gradual user migration without disruption.
- Centralized management: Administer all tenant sync settings, exclusion rules, and logs from one location in Practifi.
Configuration Required
Multi-tenant integration must be enabled and configured by your Practifi Administrator or implementation team. This feature requires coordination with your Microsoft 365 administrators to establish credentials and permissions for each tenant you want to connect.
This enhancement enables organizations to maintain operational continuity during acquisitions and migrations while building toward a unified client data foundation in Practifi. For detailed setup instructions, see our article on Connecting Multiple Microsoft 365 Tenants to Practifi.
Styling Change to Read-Only Checkboxes
Salesforce has implemented a styling change in the Spring ’26 release that affects read-only checkboxes across all Practifi apps. Selected checkboxes now display a gray checkmark without a border, while unselected checkboxes display a dotted border. This is a visual change only—functionality remains unchanged. As this is a Salesforce platform-level change, it cannot be customized.
Resolved Issues
Follow-up Assistant
Follow-up Actions Display Issue Resolved
A visual display issue was affecting tasks generated by Follow-up Assistant when viewed via the eye icon on the Meetings page. Borders around individual follow-up tasks were not appearing, making it difficult to visually distinguish between separate action items.
A CSS fix has been implemented to restore borders around suggested tasks in Follow-up Assistant. When the eye icon is clicked to view AI-generated follow-ups from meeting summaries, each task now displays with proper visual separation, improving readability and clarity.
The issue was caused by a global CSS rule that was inadvertently removing borders from action items. The fix applies a targeted CSS override to restore the expected styling for task suggestions in Follow-up Assistant when viewed from the Meetings page.
This fix is applied automatically and requires no configuration changes or action by administrators. Users may need to refresh their browsers to see the updated styling.
Related Activity Link in Follow-up Assistant Tasks
Tasks created by Follow-up Assistant are now automatically linked to their source Meeting record in the Related Activity field, ensuring users can trace back to the original meeting context.
Previously, tasks created by Follow-up Assistant were not automatically linked to their source meeting in the Related Activity field, breaking the contextual connection between follow-up actions and the meetings that generated them.
With this fix, tasks generated by Follow-up Assistant now automatically populate the Related Activity field with the source Meeting record. This ensures users can trace back to the original meeting context and maintains consistency with manually-created follow-up tasks.
Users will now see AI-generated tasks properly connected to their source meetings, improving task context and making it easier to understand why specific follow-ups were created. This also ensures that AI-generated tasks appear correctly in meeting-related task views alongside manually created follow-ups.
Smart Notes
Smart Notes Automatically Remove Events from Meetings with Missing Notes
We resolved an issue where Event records with Smart Notes did not update the Has Notes field (practifi__Has_Notes__c). This caused events documented only with Smart Notes to continue appearing in the Meetings with Missing Notes tile, requiring users to add a standard Salesforce Note as a workaround.
Smart Notes now correctly trigger updates to the Has Notes field:
- When a Smart Note is created or linked to an event, the Has Notes field is set to TRUE, and the Event record is removed from the Meetings with Missing Notes tile
- When a Smart Note is deleted, the system checks for any remaining documentation:
- If no notes remain, Has Notes = FALSE, and the Event record reappears
- If other notes exist, Has Notes stays TRUE
Smart Notes are now fully recognized as valid documentation for compliance and workflow tracking, eliminating manual steps and improving accuracy.
Smart Notes Record Limit Increased on Client Records
Previously, Smart Notes displayed a maximum of 50 records when viewed from a Client record, even when more Smart Notes existed. The display limit has been increased to 1,000 records to align with other Smart Notes areas, ensuring all relevant records are visible from the client detail page.
Active Forms
Task Completion Issue with Required Fields
In certain process types, tasks could not be completed if a required Active Form field already contained a value, even when all required information was present. Users previously needed to edit the field (for example, by adding a space in a text field) to proceed.
Tasks can now be completed as expected without requiring manual adjustment to field values. This fix applies to all process types using the same task completion logic.
Microsoft 365 Sync
Events Deleted When Converting an Individual to a Household
When converting an Individual to a Household, events could be deleted from the timeline, resulting in lost notes, Feed mentions, and broken notification links. This affected both Practifi-created events and those synced from Outlook/Microsoft integration, particularly in collaborative scenarios involving multiple advisors.
The event sync process now uses a queueable job architecture with asynchronous processing checks to ensure all events, including their notes, mentions, and attachments, are properly preserved and transferred to the Household timeline during conversion.
Important Notes:
- No configuration required: This fix is automatic with no administrator intervention needed
- Forward-looking only: Prevents future event deletions but does not restore previously deleted events
- Expected behavior: All events from the Individual will now appear on the Household timeline with complete details intact
RMD Alert Process Creation Restored
RMD Alerts were failing to automatically create follow-up processes for clients with outstanding Required Minimum Distributions (RMDs) when the RMD Process Type was configured to assign tasks using Specify by Servicing Team Role or Specify by Business Role assignment types.
The RMD Alert scheduled job now correctly retrieves the necessary assignment information from RMD Process Type configurations. When the daily RMD Alert job runs, it successfully creates the expected follow-up processes for clients with outstanding RMDs, regardless of the assignment type used.
Firms using RMD Alerts with a Servicing Team Role or Business Role assignment will now see processes created automatically as expected. No configuration changes are required; existing RMD Alert and Process Type configurations will work automatically once the fix is deployed.
Meeting Summaries Now Visible When Recording Status is Media Expired
We’ve resolved an issue where Notetaker-generated meeting summaries disappeared when the associated recording reached Media Expired status. Previously, users could see that a meeting occurred, but couldn’t access the summary content.
Meeting summaries now remain accessible even after recordings expire or are removed. Summaries generated by Notetaker are preserved independently of the underlying media, ensuring your meeting notes and follow-up actions remain available.
This fix is included in the Blaufränkisch release and is also being packaged into a patch release for Practifi Intelligence clients.
Activities
Duplicate Mark as Complete Button on Task Records
We identified an issue where the Salesforce Spring ’26 update caused the Mark as Complete button to appear twice on the Task record page. This caused visual confusion for users completing tasks. We’ve applied a product-level CSS fix to resolve the duplicate button display, and the button now appears as expected on all Task records.
Blaufränkisch Minor Release - April 2026
The following changes were rolled out in an update on April 6, 2026:
Smart Note Creation Guard
Smart Notes now includes a built-in creation guard that ensures all records are created through Practifi's verified pathways. This strengthens data integrity by validating the source of every new Smart Note at the point of creation.
How It Works
The creation guard is active by default and applies to every new Smart Note. All standard workflows continue to operate as expected, including creating Smart Notes through the Practifi interface (template-based, content block-based, and legacy template creation), generating meeting summaries via the Notetaker integration, and running Practifi's built-in migration batch process.
If a Smart Note is created outside these supported pathways (e.g., custom Apex, Salesforce Flows, or third-party integrations), the guard will surface a validation error to maintain data quality.
Impact
No action is required for standard Smart Notes usage. Firms that have built custom automations or third-party integrations that create Smart Note records directly should review those workflows, as they will now be subject to the creation guard's validation.
Notetaker Edit Default Bot Button Restored
The Edit Default Bot button was missing from Notetaker settings following the Blaufränkisch release. Administrators who needed to update bot appearance settings (name or image) had to navigate to Notetaker Custom Settings in Salesforce Setup as a workaround.
The Edit Default Bot button has been restored to the Bot Appearance section of the Notetaker tab on the Intelligence Features page in the Settings app, allowing administrators to configure bot name and image directly from the settings UI as intended.
Notetaker Meeting Transcripts and Summaries Not Generating
Some clients experienced issues where the Notetaker bot either failed to join scheduled meetings or joined successfully but did not generate transcripts and summaries afterward. In such cases, meetings would complete without any Notetaker output being saved to the associated Practifi record, requiring manual follow-up by advisors.
Two underlying issues were identified and resolved. First, an infrastructure capacity limit in the middleware layer was causing connection failures when the service exceeded its processing quota. This was addressed by upgrading the service tier to support higher throughput. Second, a Salesforce API issue was preventing transcript and summary content from being reliably saved after processing. The code was updated to introduce retry logic for content insertion failures, improve handling of recurring calendar events, and prevent duplicate configuration updates during the sync process.
Microsoft 365 Sync - Duplicate "On Behalf Of" Calendar Updates Resolved
Following the Blaufränkisch release, some clients experienced duplicate calendar update emails being sent to meeting attendees. When a delegate updated a calendar invite on behalf of the meeting organizer, a second update email was incorrectly sent from an unrelated user (typically an administrator whose account was connected to Microsoft 365 Sync in Practifi) on behalf of the same organizer. This occurred even in environments where the sync was configured as one-way (Microsoft to Practifi), causing confusion for attendees who received unexpected update notifications.
The issue in the Microsoft 365 Sync process that triggered duplicate outbound calendar updates has been resolved. Calendar invite updates made by delegates now send only the expected notification from the delegate, without triggering additional updates through the Practifi sync connection.
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 Forms | Enhanced Prefilling and Event Creation in Active Forms |
|
| Smart Notes | Smart Notes Migration Tool |
A new "Migration" page has been added to the Smart Notes Settings UI. This page provides tools for converting legacy Salesforce Notes, Task descriptions, Call descriptions, and Event descriptions into Smart Notes.
|
| Smart Notes Supported in Tasks and Calls |
Smart Notes components are now available for Task record pages in two locations:
Admin Action Required: For existing orgs, administrators must manually add the Smart Notes component to Task record pages:
Administrators can add the component to one or both locations based on their org's workflow preferences. |
|
| Data Model – Smart Notes | Categories for Smart Notes, Templates, and Content Blocks |
|
| Settings app – Smart Notes | New Categories tab with Category Manager interface for creating and managing categories | |
| Smart Notes - User Interface |
Admin action required: Create categories in Settings → Smart Notes → Categories before users can assign them Optional: Update page layouts to include the Category field, or configure defaults in Custom Settings → Smart Note Settings |
|
| Smart Notes | Smart Note Creation Guard |
|
| AI Notetaker | Manage Calendar Connections for AI Notetaker | A new "Manage Calendars" tab has been added to AI Notetaker settings, allowing administrators to view and disconnect user calendar connections. |
| AUM Rollups (Core Product) | AUM Calculation Enhancements (All Integrations) | Rollup job criteria updated to exclude assets with Stage values of Disposed, Draft, Declined, Did Not Proceed, and Potential. Only assets with Stage of Owned, Application, or Financed are now included. Affected jobs: AUM To Service, Annual Revenue To Service, AUM To Financial Product, Number of Assets. |
| AUM Rollups (Superannuation) | AUM Calculation Enhancements (All Integrations) | Same criteria update applied to: Member Account to Value, Total Member Accounts, Active Member Accounts. |
Comments
Please sign in to leave a comment.