Barbaresco - April 2025

Overview

The following article covers what's new in our Barbaresco release (beginning in April 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.

Barbaresco enhances efficiency with a new account opening workflow, expanded servicing team management, improved event handling and more.

• Product Enhancements
  • Pershing New Account Opening Workflow
  • Delete Team Member Action for End Users
  • Streamlining Notes and Files for Events with Attendees
  • Improved Formatting for Active Form and Task Action Alerts
  • Email Functionality Enhancements
• Resolved Issues
  • Active Forms
    • Preventing Duplicate Active Form Pinned Fields in Process Launch
    • Active Form File Upload Enhancements and Error Prevention
    • Execution Rules Support Currency Fields in Active Forms
    • Visibility Rules for Prefilled Fields in Active Forms
    • Enhanced Active Form Field Mapping for Accuracy
    • Corrected Active Form Preview Behavior in Process Launch
  • Deliverables
    • Front-End Validation for Fulfillment Settings on the Deliverable record page
    • Deliverable Due Date Calculation Fix
  • Miscellaneous
    • Black Diamond Holding/Asset Names Exceeding 80 Characters
    • Practifi Propel CSS Styling Fixes
    • New Deal and Promote to Prospect Actions Validation
    • Improved Checklist Formatting on Task Pages
    • Starting a Process with No Launch Tasks
• Change Log

Product Enhancements

Pershing New Account Opening Workflow

We've made significant enhancements to the new account opening workflow for our Pershing integration, making it easier and more efficient for users to open accounts while keeping data in sync between Practifi and Pershing. We've built a Pershing New Account Opening process type in Practifi that seamlessly connects with Pershing NetX360.

This process features a task with a Flow-built Active Form that has all the necessary questions from the Pershing New Account Opening form.

The Active Form automatically populates Contact and Entity data, significantly reducing manual data entry. This process can be used to open multiple accounts simultaneously for the same client.

Once the form is completed, Practifi automatically sends the input data to Pershing NetX360, where a draft account is created. Users must then complete the account opening process in NetX360. After the draft account is set up, Practifi retrieves the account number and associates it with the corresponding Asset record, which is also created automatically.

If you're interested in the new account opening workflow for Pershing, please reach out to your CSM or Practifi contact.

Delete Team Member Action for End Users

We created servicing teams because multiple people often serve clients at your firm. With this release, we're making it easier to manage these teams. Previously, only System Administrators could remove servicing team members using the Remove All Members or Delete actions in the Servicing Team component. We've introduced a new record action and permission set to enable non-admin users to remove servicing team members without needing Modify All access on the Account object.

The Delete Team Members action on Entity records invokes a new Flow called Practifi - Delete Team Members. Users can access this action by clicking the caret next to the Change Owner button in the record side panel.

To manage access, we've introduced a new permission set called Practifi - Servicing Team - Delete Members. System Administrators will be given this permission set by default. Non-admin users must be assigned the permission set to access the Delete Team Member action. Practifi Administrators can assign the permission set to individual users or add it to a Permission Set Group.

Please note the following:

• System Administrators will continue to see the existing Remove All Members and Delete actions in the Servicing Team component.
• The Remove All Members and Delete actions also remain visible for users with Delete permissions on the Account object.
• The System Administrator profile controls the visibility of these actions via the Practifi - Custom Objects, Fields & System - Administrator permission.
• Account Owners (standard users) retain access to servicing team options.

Streamlining Notes and Files for Events with Attendees

Previously, creating an event with attendees generated duplicate child events, leading to inconsistencies in Notes and Files visibility. We've updated the Upcoming Meetings tile configuration so both organizers and attendees can access a single, unified Event record.

This eliminates duplicate entries in the Upcoming Meetings tile. Notes and Files are now visible to all participants. We've ensured proper visibility for events, whether they're accessed via the Activity Timeline or the Upcoming Meetings tile.

Please note: Child events may still appear in the Calendar menu, but this will not impact Notes and Files access.

Improved Formatting for Active Form and Task Action Alerts

We've enhanced the formatting of success and error messages for Active Form Tables and Task Actions, making notifications clearer and more legible.

For Active Form Tables, the Failed Create and Delete alerts now display the table’s purpose and name. Failed Update alerts indicate which record failed but omit the table name. Successful actions list all processed records.

For Task Actions, success messages now display the action type, label and processed record (if applicable). Failure messages include the action type and label to assist with troubleshooting.

Email Functionality Enhancements

We resolved multiple issues with the Send an Email action in both standard Salesforce Email actions and Active Forms, improving recipient merge field handling, email tracking and visibility of send limits:

• Recipient Merge Field Error – Emails failed to send in Active Forms when using recipient merge fields, displaying an error in the email preview within the Task Completion workflow. Emails with recipient merge fields are now sent successfully via Active Forms.
• Empty From and To Fields – Due to the above error, these fields remained blank in the email preview within the Task Completion workflow, preventing manual input. The From and To fields are now correctly populated based on configured settings, avoiding blank entries.
• Missing Email Logs – Emails sent via the Send an Email action in an Active Form were not logged in the recipient’s Activities timeline despite being delivered successfully. Sent emails now consistently appear in the Activities timeline of recipient records.

In addition to the above fixes, we've also introduced a daily send limit tracker. A counter in the email preview screen of the Task Completion workflow now displays the remaining emails available for the day (X/Y send limits remaining).

Please note the following about the new counter:

• Salesforce imposes a limit of 5,000 external emails per day.
• The send limit tracker updates within a few minutes; it does not refresh instantly.
• If a Practifi user is the first recipient, the Salesforce email limit is not reduced, and the email will still be sent, even though it won’t appear in their activity list.
• Emails count toward the limit when the user is in the CC or BCC field or added as a second recipient.
• The email preview in the Task Completion workflow is available only if a recipient is entered in the To field.

Resolved Issues

Active Forms

Preventing Duplicate Active Form Pinned Fields in Process Launch

We've refined how Active Form pinned fields behave when launching a process using the Start a Process action. Previously, when a process included multiple launch tasks, Active Form pinned fields would duplicate but not retain user input across tasks, potentially causing data loss.

Now, Active Form pinned fields will only appear on the first launch task for user input and will no longer display on subsequent launch tasks to prevent duplication. After process creation, pinned fields will persist correctly across all tasks, ensuring seamless data retention. The help text for the Include Active Form in Launch Action? field has also been updated for clarity.

Active Form File Upload Enhancements and Error Prevention

Previously, deleted files caused an ENTITY_IS_DELETED error when completing tasks with Active Form file uploads. If a file was removed from an external location (e.g., the Files component) and another file was uploaded, the system retained a reference to the deleted file, preventing task completion.

To solve for this, the system now validates file references before completing a task. Additionally, we introduced an inline delete button in Active Forms, allowing users to remove uploaded files before task completion. These improvements ensure better file management and prevent upload-related errors.

Execution Rules Support Currency Fields in Active Forms

Execution Rules failed to evaluate Currency fields in Active Forms, preventing some Task Actions from triggering correctly. These rules now correctly process currency values, whether entered manually or retrieved from a related record. Actions that rely on Currency field conditions will now trigger seamlessly upon task completion.

Visibility Rules for Prefilled Fields in Active Forms

Visibility Rules were not triggering correctly when a picklist field was pre-filled in an Active Form. Previously, visibility conditions only applied if the value was manually selected, leading to inconsistencies in form behavior. Visibility Rules now recognize pre-filled values and apply conditions as expected. When a field is pre-filled based on a related record, the visibility criteria automatically trigger for other dependent fields.

Enhanced Active Form Field Mapping for Accuracy

We've improved Active Form field assignments to ensure that only the relevant values transfer between tasks. Previously, when a user changed a picklist value, both the new and previous selections could persist in the next task. Additionally, past selections couldn’t be removed unless a multi-select picklist was used, which was not intended.

We introduced Execution Rules to control which values pass to the next task. These rules ensure that only the correct field values are transferred, preventing unintended data carryover. This fix supports multiple mapping configurations for a single field.

Corrected Active Form Preview Behavior in Process Launch

We resolved an issue where launching multiple instances of a process with Active Forms in the launch task incorrectly displayed an Active Form preview for all instances. This caused unintended behavior, where inputs from the first instance were copied across all others, contradicting the system message stating Active Forms would not appear in the window.

The Active Form preview no longer displays in multi-instance process launches. This ensures system behavior aligns with the message in the process selection screen and prevents data duplication across instances.

Deliverables

Front-End Validation for Fulfillment Settings on the Deliverable record page

To prevent invalid configurations, a front-end validation feature has been implemented in the Fulfillment Settings on the Deliverable record page. Previously, you could incorrectly save an invalid combination of the Auto Create Fulfillment Activities and If It Isn’t Fulfilled By Its Due Date fields, bypassing backend validation. This oversight led to detached activities, workflow inefficiencies and an accumulation of task backlogs.

Now, when the Auto Create Fulfillment Activities field is enabled, the only allowed option for If It Isn’t Fulfilled By Its Due Date field is "Treat it as overdue". Attempts to save an invalid value will prompt an error message.

Deliverable Due Date Calculation Fix

There was an inconsistency in how days were counted when calculating a Deliverable’s due date based on different Initial Calculation Basis options:

• When using Service Start Date, the count started from tomorrow.
• When using Date During Calendar Period, the count started from today.

This discrepancy led to inconsistent due date calculations for the same frequency settings across different bases.

Now, for all Initial Calculation Basis options—Based on Service Start Date, Based on End of Calendar Period and Based on Date During Calendar Period—the system will consistently start counting from today or use today as the reference for determining the appropriate week, month or year based on the configured frequency.

Additionally, for all "Every X" frequency configurations—Every X Weeks, Every X Months and Every X Years—counting will begin from the day the deliverable is created (today) and the due date will be determined by adding the configured frequency to this start date. For example, if a Deliverable's frequency is set for “Every 2 Weeks” and created on May 1, 2025, the next due date will be:

May 1, 2025 + 14 days = May 15, 2025

When using the Sync with Services action, users can choose Today’s Date or Last Fulfillment Date as the reference point for recalculating the due date. If the Last Fulfillment Date is in the past, the system will default to Today’s Date.

Miscellaneous

Black Diamond Holding/Asset Names Exceeding 80 Characters

Holding/Asset names exceeding Salesforce's 80-character limit could not sync into Practifi via the Black Diamond integration. While Salesforce has acknowledged this limitation, there are no immediate plans on their roadmap to increase the limit.

In line with a similar fix for our Addepar integration, we have now applied the same solution to Black Diamond. When synced into Practifi, holding/asset names exceeding 80 characters will be automatically truncated to the first 80 characters. This ensures seamless data synchronization and consistency across Practifi-owned integrations.

Practifi Propel CSS Styling Fixes

Recent Salesforce updates may have overridden or disrupted the existing CSS styling for Practifi Propel, leading to UI inconsistencies in the Client Book. We have reviewed and corrected the affected CSS to restore the intended styling and ensure a consistent user experience in the Client Book.

New Deal and Promote to Prospect Actions Validation

Previously, when users attempted to invoke the New Deal or Promote to Prospect actions on a record that did not satisfy the validation filter criteria for a custom Entity lookup field on the Deal object, the process would fail, displaying a generic error message. This ambiguity led to confusion and could interrupt workflows.

We've replaced the generic error message with a custom warning message. If the associated Entity does not fulfill the necessary filter conditions (e.g., Account Record Type NOT EQUAL TO Household), users will receive a specific message that clarifies the reason for the failure.

Improved Checklist Formatting on Task Pages

Checklist items on the Task record page have been reformatted to improve readability and make better use of available space. Previously, text wrapping occurred too early, creating unnecessary blank areas and making longer checklists difficult to scan.

Now, checklist items extend effectively across the page while maintaining proper alignment. This ensures a cleaner layout, reduces excess white space and enhances the overall user experience without affecting button placement or UI functionality.

Starting a Process with No Launch Tasks

We've improved the Start a Process workflow to provide better validation and user feedback when initiating processes without launch tasks. If a Process Type has the Suppress At Launch checkbox enabled for all its tasks, a validation check triggers a warning in the Issues to Resolve table.

Instead of displaying a blank screen when no tasks are launched, the Start a Process window now presents a confirmation message, ensuring users understand the process has been created successfully.

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?
Deliverables	Front-End Validation for Fulfillment Settings on the Deliverable Record Page	The system prevents users from saving invalid combinations of fulfillment settings by implementing front-end validation. When the Auto Create Fulfillment Activities box is checked, the only acceptable choice for the If It Isn’t Fulfilled By Its Due Date field is "Treat it as overdue". Should users attempt to save an invalid value, an error message will be displayed to guide them.
Task Completion workflow > Email preview screen	Email Functionality Enhancements	The email preview screen now shows remaining daily send limits (X/Y send limits remaining) for visibility.
Processes & Tasks	Preventing Duplicate Active Form Pinned Fields in Process Launch	Added a validation check for missing launch tasks and replaced the blank page with a success message when tasks are suppressed. Active Form pinned fields now appear only on the first launch task in the Start a Process workflow, preventing data loss across tasks.
	Process Type > Help Text Update for Include Active Form in Launch Action? checkbox	Help text has been updated to clarify how Active Form pinned fields display in the Start a Process action and persist post-launch.
Active Form Field Assignment	Enhanced Active Form Field Mapping for Accuracy	An Execution Rules tab has been added to the Active Form Field Assignment record, featuring a Rule Builder component that enables conditional value mapping to target fields. This enhancement allows users to define multiple mappings for a single target field while ensuring that only one dynamically determined value is passed based on execution criteria.
New Deal Action	New Deal and Promote to Prospect Actions Validation	When users try to create a new deal on an Entity record that does not satisfy the necessary validation filter criteria, we have replaced the previous generic error message with a new custom warning message to offer clear guidance on the reasons behind the failure of the action.
Entity Record Page	Delete Servicing Team Member Action for End Users	Added a new action in the overflow menu next to the Change Owner button to invoke the deletion Flow.
Permission Sets		Introduced a permission set to control access for non-admin users. Admins receive this by default, while non-admins require explicit assignment.
Settings App – Additional Features - Practifi Promote	Ensuring correct metadata values for Practifi Promote: Attributed Revenue and Practifi Promote: Primary Campaign	The system now verifies and ensures that required records in Additional Features Setting metadata are correctly populated. If records are missing or incorrect, they are automatically updated with default values to enable accurate campaign revenue attribution. No changes are made if the records already exist with correct values. Users can view and update these values through the existing settings sections: Practifi Promote: Attributed Revenue Practifi Promote: Primary Campaign
Flows	Delete Team Member Action for End Users	Flow Name: Practifi - Delete Team Members Flow Introduced a new local flow to allow non-admin users to delete servicing team members. No modifications to existing functionality.
	Preventing Duplicate Active Form Pinned Fields in Process Launch	Flow Name: Practifi - New_Record_Process Flow Refined flow logic to prevent duplicate Pinned Active Form Fields when launching a process. For customized client flows, ensure the following elements align with the standard flow: Practifi - New Process Flow Active Form with Component (API Name: Active_Form). Increment Iterator (API Name: Increment_Iterator).
	New Deal and Promote to Prospect Actions Validation	Flow Name: Practifi - New Record - Deal Added an Action element to display a success message when the Insert Deals element (API Name: Insert_Deals) executes successfully. Improved error handling by updating the Screen element (FIELD_FILTER_VALIDATION_EXCEPTION_error_screen) to display an error message when the Decision element (checking_for_FIELD_FILTER_VALIDATION_EXCEPTION) validation fails, ensuring that users receive appropriate error notifications.
		Flow Name: Practifi - Entity Life Cycle - Promote to Prospect Added a Decision element checking_for_FIELD_FILTER_VALIDATION_EXCEPTION_skip_enabled to validate deals when Skip Service is enabled. This element branches to two Screen elements: One for general error messaging Another specifically for the FIELD_FILTER_VALIDATION_EXCEPTION error Added a Decision element Create_Deal_for_New_Deal_when_Skip_Service_disabled to validate deals when Skip Service is disabled. This also connects to: A general error screen A specific error screen for the FIELD_FILTER_VALIDATION_EXCEPTION error Added an Action element success_toast_skip_disabled near the end of the flow to display a success toast upon successful completion.