Pinot Meunier - July 2025

Overview

The following article covers what's new in our Pinot Meunier release (beginning in July 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 Pinot Meunier, we're introducing two new AI-powered features in Practifi, along with numerous other enhancements to boost productivity and improve the user experience.

• Product Enhancements
  • Smart Process Builder
  • Follow-up Assistant
  • Processes and Tasks
    • Improved Handling for Auto-Completed Tasks
    • Validation Check for Auto-Completed Tasks
  • Add Active Form Prompts to Pinned Active Form Sections
  • Set As Created By Field Extended to More Objects
  • User Permissions
    • Improved License and Permission Set Configuration
    • Enhancements to Read-Only User Permissions
  • Deliverables
    • Deliverables Wait for Active Services
    • Better Tracking of Missed and Canceled Items
  • Improved Black Diamond Account Name Mapping
• Resolved Issues
  • Smarter Execution of Task Outcomes and Actions
  • Help Text for Button Groups in Active Forms
  • Flow Header Display Issue in Task Templates
  • Birthdate Display on Household Members Card
  • Asset-Based Service Selection Logic Restored
  • Prevention of Incorrect Service Creation for Lost Clients
  • Fix for Deliverable Fulfillment Task Assignment
• Change Log

Product Enhancements

Smart Process Builder

Manually building processes in Practifi involves several steps, particularly for complex workflows. With this release, we're leveraging AI to significantly reduce this effort. Our new Smart Process Builder harnesses the power of a large language model to transform how administrators create and configure processes.

Smart Process Builder is an intelligent automation tool that converts natural language descriptions into Process Type records, complete with tasks, outcomes and actions. Instead of manually designing each step, task and decision point in a process, you can use prompts to describe what you want to accomplish in plain English, letting Smart Process Builder handle the technical configuration.

Smart Process Builder uses an LLM to understand your process requirements and automatically:

• Generate visual flowcharts that map your entire process
• Create detailed task configurations with appropriate statuses and priorities
• Establish logical branching and decision points
• Provide industry-standard recommendations for process optimization
• Suggest enhanced prompts for better outputs

If you're interested in Smart Process Builder, reach out to your Client Success Manager or Practifi contact.

Follow-up Assistant

We're also excited to announce Follow-up Assistant, an intelligent feature that automatically generates contextually appropriate action items from your meeting notes. This AI-powered tool is designed to understand your firm's unique workflows and recommend the right type of follow-up actions for maximum efficiency.

Unlike generic AI notetaking solutions that only generate basic tasks, Follow-up Assistant understands Practifi's workflow engine and can recommend processes, task templates and standard tasks based on the context of your notes.

Follow-up Assistant works with any note created on a Client or Prospect record in Practifi, whether the text within it is generated by an AI notetaker or written by your team members. You can create action items that truly reflect the work you need to accomplish, reducing the time spent manually creating processes and templated tasks.

If your firm uses a notetaking tool that integrates with Practifi, the AI notetaker automatically creates the complete note in Practifi. Analysis begins immediately and suggestions appear in about 30 seconds.

Follow-up Assistant reviews the content of notes created in your Practifi instance. The AI determines whether to suggest standard tasks (similar to traditional manual task creation), processes or templated tasks. Recommendations are tailored to match your firm's established workflows.

If your firm is using AI note-taking tools, Follow-up Assistant can enhance that functionality with Practifi-specific action item generation. Even if you're taking notes the traditional way, you can still access AI-powered follow-up suggestions without changing your current note-taking process. Follow-up Assistant saves you time and ensures consistent follow-ups across your practice.

You can also access Follow-up Assistant from the side panel on the Home page to see suggested action items across your practice.

If you're interested in Follow-up Assistant, reach out to your Client Success Manager or Practifi contact.

Processes and Tasks

Improved Handling for Auto-Completed Tasks

Some firms create tasks that launch with a status of Completed, often for compliance-related processes that don't require user action. We've made these tasks less confusing by redesigning how they appear.

When a task is created with a default status of Completed, the Record Alerts component will now be dynamically hidden to avoid confusion. Instead, users will see a clear, dark-themed informational message that appears just below the success toast, confirming that no further action is required. If any follow-up actions are configured, they will still run as expected, even if the task is auto-completed.

Validation Check for Auto-Completed Tasks

A new warning now appears in the Validation Check component when run on Process Task records, alerting administrators if a task is set to launch with a default status of Completed. This helps ensure better visibility and oversight of task configuration.

Please note: This validation check is only available at the Process Task level and does not apply to Process Type records.

Add Active Form Prompts to Pinned Active Form Sections

Based on client feedback, we’ve introduced support for Active Form Prompts within Pinned Active Form Sections under the Pinned Active Form Fields tab of a Process Type. Users can now create prompts for pinned sections using the Active Form Prompt object, following the same process used for Process Tasks.

Active Form Prompts for pinned sections now support all six standard types, styled using Salesforce Lightning Design System (SLDS) scoped notification styles:

• General
• Informational (Light)
• Informational (Dark)
• Success
• Warning
• Error

Each type includes appropriate icons and styling for a consistent and clear user experience. Practifi Merge Language (PML) is supported in the body of the prompt, allowing dynamic content rendering based on context, just like in other configurable areas of the platform.

You'll notice several UI enhancements on the Process Type record page. A Dynamic Related List – Single component has been added to display Active Form Prompts, located below the existing Active Form Sections and Active Form Fields related lists, displaying up to 10 records with columns for Name, Form Section and Type.

To ensure a consistent user experience across all Active Form Sections, the Active Form Prompts related list is also available on individual Pinned Active Form Section records, mirroring the experience for Process Task sections. Users can create prompts directly from this related list, ensuring the prompt is automatically associated with the correct section.

The Active Form Prompt record page uses a Header and One Region template. The Header region includes a Highlights Panel, while the Main region contains two tabs:

• Details (default): Displays prompt content and configuration.
• Visibility Rules: Includes a Rule Builder for setting display conditions.

To maintain consistent display order within a section, we've added validation checks for duplicate Order values across Fields, Prompts and Tables. If duplicates are found, an error is flagged and each duplicate record is listed.

Set As Created By Field Extended to More Objects

A new field called Set As Created By has been added to the following objects:

• Entity
• Contact
• Deal
• Service
• Asset/Liability

We added the Set As Created By field to support data migration and delta load scenarios. This enhancement mirrors the existing functionality on the Activity object, allowing users to explicitly define the original creator of a record.

The new field is available wherever a Set As Created Date field is present. During Insert operations, the value from the Set As Created By field is copied into the system field CreatedById, if permitted by trigger settings. During Update operations, only the custom field is updated, while the CreatedById remains unchanged. This behavior is enabled when the Set Created Date & Created By Via API setting is enabled in Practifi Trigger Settings, or when no Practifi Trigger Setting record exists.

Insert/Update/Upsert operations vary by object type, as detailed in the table below:

Object	Insert Behavior	Update Behavior	Upsert Behavior
Service	Copies both custom fields to system fields	Only custom fields are updated	New: both copied to system fields Existing: only custom fields are updated
Asset/Liability			N/A
Entity		N/A	New: both copied to system fields Existing: only custom fields are updated
Deal		N/A
Contact		Only custom fields are updated	N/A

User Permissions

Improved License and Permission Set Configuration

We’ve made important improvements to how Practifi permission sets are configured and assigned based on Salesforce user licenses. These changes resolve previous inconsistencies and reduce manual effort when onboarding new users.

We removed the Practifi - Console User permission set from both the Super and Standard permission set groups for consistent configuration. We've designated the Practifi- Console User permission set as a standard permission set for Salesforce Platform licensed users. We've also validated successful assignment for Platform users and identified and resolved conflicts to support assignments to Salesforce licensed users, where applicable.

To support efficient onboarding, certain permission sets and permission set groups are assigned automatically based on a user's license and/or profile. The assignment logic works as follows:

• If a user is assigned the Salesforce Platform license type, they are automatically assigned the Practifi - Console User permission set.
• If a user is assigned the Practifi User - Salesforce or Practifi User - Salesforce Platform profile, they are automatically assigned the Practifi - Standard User permission set group.
• If a user is assigned the System Administrator profile, they are automatically assigned the Practifi - Administrator permission set group.

All other permission assignments will continue to be managed manually. These changes ensure accurate permission mapping based on user licenses and profiles, reduce manual setup effort, mitigate potential configuration errors and provide a consistent and scalable permission strategy across environments.

Please note: These changes apply to new Practifi organizations created after the Pinot Meunier upgrade.

Enhancements to Read-Only User Permissions

We’ve improved the Practifi – Read Only User permission set group to better support scenarios where users need visibility into system data without the ability to make changes, such as during external audits or when providing temporary access to stakeholders.

We reviewed and enhanced the Practifi - Read Only User permission set group to ensure users assigned to this group can view all necessary records without compromising data integrity. It now includes custom object access via the practifi__Custom_objects_fields_system_View permission for read-only access to custom Practifi objects and fields. The Salesforce_objects_standard_view permission grants view access to key Salesforce standard objects. These updates help ensure uniform read-only access across both standard and custom records in all environments.

While read-only users cannot edit or create records, some action buttons may still appear in the interface. These buttons are non-functional for read-only users and all access restrictions remain fully enforced. We're exploring future enhancements to streamline the interface by hiding these buttons for read-only users, helping create a more intuitive experience.

Deliverables

Deliverables Wait for Active Services

We’ve enhanced how Deliverables behave when linked to Services that are not yet active, such as those with a Draft, Canceled or Completed status. This update ensures Deliverables no longer activate prematurely, helping to avoid confusion and maintain workflow accuracy.

Previously, if a Service was created in an inactive state but its Deliverables met activation criteria, those Deliverables could still become active or appear in the Marked for Fulfillment area on Task and Event records. This behavior was inconsistent with the Service's status and could disrupt task planning.

With this update, Deliverables tied to Services in inactive statuses (i.e., Draft, Canceled, Completed, Terminated or Blank) will remain inactive, even if their activation rule criteria are met. Deliverables will now only activate when the parent Service is in an active status and the Deliverable's activation rules are satisfied. This prevents Deliverables from activating too early, aligns Deliverable behavior with Service status and supports cleaner workflows and more accurate task tracking.

Better Tracking of Missed and Canceled Items

We've made important improvements to how Practifi tracks missed and canceled Deliverable fulfillments, enhancing accuracy, transparency and auditability.

For clearer status of missed fulfillments, we've addressed an issue where the system marked missed fulfillments as Pending, which inaccurately suggested they were awaiting action. Missed fulfillments will now correctly show a Status of Missed. This change provides a more accurate reflection of the Deliverable's status. It applies to fulfillments where the following conditions are met:

• The Outcome is Missed.
• The Status is either Active or Marked for Fulfillment.
• The Deliverable Type's If It Isn't Fulfilled By Its Due Date setting is set to Treat it as Missed and Recalculate the Due Date.
• The due date has passed without fulfillment.

After deployment, a one-time update will correct existing records by updating all Fulfillment records that have an Outcome of Missed and a Status of Pending to a Status of Missed.

For canceled tasks, we've resolved an issue where cancelling a task linked to a Deliverable before it was fulfilled would delete the associated Fulfillment record, resulting in lost audit history. Canceled tasks will no longer delete Fulfillment records. Instead, the record will now show a Status of Task Canceled and an Outcome of Task Canceled. The record will also retain a reference to the canceled task, ensuring traceability. This change applies only to future task cancellations, as previously deleted records cannot be restored.

To support these enhancements, we've added the following values to the Deliverable Fulfillment object:

• Status field: Missed and Task Canceled
• Outcome field: Task Canceled.

These changes improve accuracy in fulfillment reporting, provide full visibility of canceled tasks and prevent loss of important audit data.

Improved Black Diamond Account Name Mapping

We've enhanced our Black Diamond integration to ensure that asset names in Practifi more accurately reflect the client-facing names used in the Black Diamond portal, providing a more intuitive and consistent experience for users.

Previously, asset names in Practifi were sourced from the Account Name field in Black Diamond, which is a system-generated, non-editable value that often resulted in names that were difficult to interpret. With this update, we now prioritize the Display Name field, which is an editable and intuitive label, so that Practifi users see clearer, more recognizable account names that align with what's shown in Black Diamond.

Before this change, the name field on the Black Diamond Account was mapped to the Name field on the Asset_Liability__c object in Practifi. If the Black Diamond name field was empty, the integration used the displayName field on the Black Diamond Account as a fallback. The Black Diamond displayName on Account was mapped to the practifi__Description__c (Description) field on the Asset_Liability__c object.

We've updated the mapping logic prioritize clarity and consistency, as follows:

Black Diamond Field on Account	Practifi Field on Asset_Liability__c	Purpose
displayName (used as primary)	Name	Displays the intuitive, client-facing name
name (used as fallback)	Name	Used if displayName is empty
account (used as final fallback)	Name	Used if both displayName and name are empty
name	practifi__Description__c	Now used to store the system-generated name

This enhancement ensures that asset names in Practifi are clearer, easier to recognize and aligned with what clients and advisors see in the Black Diamond portal. By prioritizing Black Diamond's editable Display Name field, which is designed for clarity and client communication, over the system-generated Account Name, Practifi now presents more meaningful and intuitive account names, resulting in a more consistent and user-aligned experience across platforms.

Resolved Issues

Smarter Execution of Task Outcomes and Actions

We've improved how actions are executed during task completion, especially for tasks that include a mix of actions with and without associated outcomes. For tasks that include actions with outcomes and actions without outcomes, we've made the following changes:

• Actions linked to outcomes will only execute if their associated outcome is selected during task completion.
• Actions not linked to any outcome will always execute, no matter which outcome is selected.

As before, for tasks with actions but no outcomes, all actions will continue to be executed when the task is completed. For tasks where all actions are tied to outcomes, only actions linked to the selected outcome will be executed.

For example, let’s say you have a task with the following setup:

• Action 1 → linked to Outcome 1
• Action 2 → linked to Outcome 2
• Action 3 → not linked to any outcome

If a user selects Outcome 1 during task completion:

• Action 1 will be executed (linked to the selected outcome)
• Action 3 will be executed (not linked to any outcome)
• Action 2 will not be executed (linked to a different outcome)

This update applies to all tasks that were already created in the system but not yet completed.

Please note: In rare cases where two actions of the same type exist, one linked to an outcome and one not, the system will continue to execute them based on their order. These are considered misconfigurations and are not recommended.

Help Text for Button Groups in Active Forms

We’ve fixed an issue where the configured help text wasn’t appearing when picklist options were displayed using the button group style in Active Forms. This did not affect picklists shown as drop-down menus, where the help text was displayed correctly.

With this update, help text now appears as expected for button groups, ensuring that users receive the right guidance regardless of how picklist fields are presented.

Flow Header Display Issue in Task Templates

A display issue affecting Flow components embedded in the Lightning record page of task templates has been resolved. Previously, even when the Show Header option was enabled in the Flow configuration, the header would not appear when the template was launched.

Upon investigation, it was found that a CSS attribute introduced in a previous release unintentionally hid the Flow header. The CSS selector used was too broad, which caused the header to be suppressed when the Flow component was rendered.

We’ve updated the global CSS in our package to apply a more specific selector. This correction ensures that Flow headers now render correctly when the component is used on Lightning pages and the Show Header option is enabled.

Birthdate Display on Household Members Card

Within Household records, we’ve enhanced the Household Members card in the Overview tab to ensure that both birthdate and age are clearly visible for each client. Previously, a client’s age was displayed correctly, but their birthdate was missing from the Household Members card even though it existed in the system. This has now been resolved.

The issue stemmed from the card’s JSON configuration, where the field type for Birthdate was incorrectly set to Birthdate instead of the supported Date type, which caused it to render improperly.

We’ve corrected the JSON configuration to ensure that birthdate now displays properly alongside age. To maintain consistency, this enhancement applies across all entity types—Households, Organizations and Individuals—and is now reflected in the following locations:

• Members Card (Overview tab - Key Records section)
• Contact Details panel (left-hand side)

We've also ensured that age continues to display with no changes and that there is no impact on other card functionalities or user workflows.

Asset-Based Service Selection Logic Restored

We’ve resolved two regression issues affecting how asset-based Services are selected and associated with assets. These issues, originally fixed in the Graciano release, reappeared in later updates and are now fully addressed in the Pinot Meunier release.

Please note: This fix applies only to new records created after the upgrade. Existing records will remain unchanged.

Previously, a Service Type with no defined order was incorrectly taking priority over one with a lower value in the Order field. It was expected that the Service with the lowest order should be selected.

Secondly, when multiple Services had the same or blank order values, the system ignored the Last Modified Date and selected an older Service. The expected behavior was that the Service with the most recent Last Modified Date should take precedence in such cases.

Now, when an Asset record is marked as Under Advice, the system selects and associates the correct asset-based Service using the following logic:

• No Existing Asset-Based Service
  • Look for Service Types where:
    • Group = Asset-Based
    • Default = Checked
  • Selection priority:
    • Lowest Order field value
    • If Order field is tied or blank, use the most recent Last Modified Date
  • If no default exists, apply the same logic to all asset-based Service Types
  • Create a new Service and associate the asset
• Existing Asset-Based Service(s)
  • One Service exists → Asset is linked to that Service
  • Multiple Services exist → Asset is linked to the most recently modified Service
• Record Updates
  • The Asset record’s Service field is populated
  • The Service record’s Assets tab displays the linked asset

Prevention of Incorrect Service Creation for Lost Clients

We’ve resolved an issue where asset-based Services were being unintentionally created for lost clients, even when the asset had no value or a terminated Service already existed. This fix helps maintain data accuracy and prevents confusion in Client records.

In certain cases, editing or saving an asset with a $0 value for a client marked as Lost would trigger the creation of a new asset-based Service, even if the following were true:

• The client was already marked as Lost
• The asset value was $0
• A terminated Service already existed for that asset

We’ve updated the system logic to prevent new asset-based Services from being created when editing or saving an asset marked as Under Advice if any of the following conditions are met:

• The related client is marked as Lost
• The asset’s stage is one of the following:
  • Disposed
  • Did Not Proceed
  • Declined
• The asset has a valid Date Closed (practifi__Date_Closed__c)

These checks ensure that Services are only created for assets that are active and relevant. Going forward, no duplicate Services will be created for lost clients, regardless of asset value. Assets with $0 value can still be created or edited for active clients (e.g., for pending data entry). Terminated Services will remain unchanged and will not be recreated.

This enhancement ensures cleaner data, avoids redundant Service records and supports more accurate Client record management.

Fix for Deliverable Fulfillment Task Assignment

We addressed an issue where nominated tasks associated with Deliverables were not being assigned to the appropriate user, despite the Assignment Type being correctly set in the task template. With this fix, task assignments now adhere to the defined configuration, improving clarity, ownership and workflow consistency.

Previously, when a Deliverable had a nominated task, typically scheduled to be generated a few days prior to the Deliverable’s due date, that task was created using a template that specified the intended assignee (e.g., the Service Owner or Client Owner). However, in certain instances, these tasks were mistakenly assigned to the user who scheduled the background Apex jobs rather than the intended assignee.

With this update, tasks are now assigned precisely as defined in the Assignment Type of the task template. The correct user, such as the Service Owner or Client Owner, will receive the task according to the task template configuration. Tasks will no longer default to the user who initiated the background Apex jobs.

This fix ensures clear ownership of fulfillment tasks, accurate task tracking and accountability and a more reliable and consistent Deliverable workflow.

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?
Process Type > Pinned Active Form Fields tab	Add Active Form Prompts to Pinned Active Form Sections	Introduced a Dynamic Related List – Single component positioned below the existing Active Form Sections related list. This new list displays up to 10 Active Form Prompts, with key columns for Name, Form Section and Type to provide quick visibility into configured prompts.
Pinned Active Form Section record page		The Active Form Prompts related list is now available on individual Pinned Active Form Section records. This mirrors the experience provided for Process Task sections and allows users to create prompts directly from the sidebar. Prompts created this way are automatically associated with the relevant section, streamlining the configuration process.
Entity	Set As Created By Field Extended to More Objects	A new Set As Created By field has been introduced to the following objects: Entity Contact Deal Service Asset/Liability This enhancement allows users to explicitly define the original creator of a record, which is particularly useful during data migration and delta loads. It aligns with existing functionality on the Activity object. Key Behaviors: Insert: Value from Set As Created By is copied into the system field CreatedById, if permitted by trigger settings. Update: Only the custom field is updated; CreatedById remains unchanged. Trigger Dependency: Behavior is enabled when: The setting Set_Created_Date_With_Bulk_API__c is active, or No Practifi Trigger Setting record exists.
Contact
Deal
Service
Asset/Liability
Super and Standard Permission Set Groups	Improved License and Permission Set Configuration	The Console User permission set has been removed from both Super and Standard permission set groups for consistent configuration.
Salesforce Platform User Licence		The Console User permission set is now designated as a standard permission for Salesforce Platform users.
User Trigger	Improved License and Permission Set Configuration	New automation assigns the correct permission set at user creation: System Administrator profile → Assigned Administrator permission set group Salesforce Platform license → Assigned Practifi Console User permission set Practifi User – Salesforce or Salesforce Platform profiles → Assigned Standard User permission set group All other assignments remain manual for now.
Practifi – Read Only User permission set group	Enhancements to Read-Only User Permissions	We reviewed and updated the Practifi – Read Only User permission set group to ensure consistent, secure view-only access. This now includes:   Custom Object Access: practifi__Custom_objects_fields_system_View grants read-only access to custom Practifi objects and fields. Standard Object Access: Salesforce_objects_standard_view grants view access to key Salesforce standard objects. These updates ensure uniform read-only access across both standard and custom records in all environments.
Household Members Card JSON component	Birthdate Display on Household Members Card	The JSON configuration for the Household Members card has been updated by changing the field type from BirthDate to Date, enabling the birthdate to display correctly on the card.
Client Record (Households, Organizations, and Individuals)		The birthdate now displays correctly alongside the age for each member shown in the Members card on the Overview – Key Records section and the Contact Details panel (left-hand side).
Deliverable Fulfillment	Better Tracking of Missed and Canceled Items	New Status values added to the Deliverable Fulfillment object: Missed Task Canceled New Outcome value added to the Deliverable Fulfillment object: Task Canceled Impact: Missed fulfillments now correctly display Status: Missed instead of Pending. A one-time post-deployment update will correct existing records with Outcome = Missed and Status = Pending. Canceled tasks no longer delete Fulfillment records. Instead, they are updated with: • Status: Task Canceled • Outcome: Task Canceled • The link to the canceled task is retained for traceability Applies only to future task cancellations; previously deleted records cannot be restored
Task	Improved Handling for Auto-Completed Tasks	Tasks launched with a default Completed status now dynamically hide the Record Alerts component to avoid confusion, and a dark-themed informational message appears just below the success toast to clearly indicate that no further action is required.
Process Task		Validation Check Component When the Validation Check is run, a new warning now alerts administrators if a task is configured to launch with a default Completed status, helping ensure better visibility and control over task behavior.
Black Diamond integration	Improved Black Diamond Account Name Mapping	Updated Field Mapping Logic Black Diamond Account (displayName) → Practifi Asset Asset_Liability__c (Name) Used as the primary source Black Diamond Account (name) → Practifi Asset Asset_Liability__c (Name) Used as a fallback if displayName is empty Black Diamond Account (account) → Practifi Asset Asset_Liability__c (Name) Used as a final fallback if both displayName and name are empty Black Diamond Account (name) → Practifi Asset Asset_Liability__c (practifi__Description__c(Description)) Now used to store the system-generated account name