Montepulciano - April 2024

Learning Team

Overview

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

Over the years, the Practifi team has received a wealth of valuable feedback from clients and internal users alike. This feedback ranges from ideas for major enhancements to suggestions for minor updates and improvements. While high-severity issues are prioritized and solutions can be deployed promptly, suggested changes are usually integrated more gradually, often deployed alongside key new features with each major release.

The Montepulciano release is entirely dedicated to responding to user feedback and resolving issues. It includes a broad range of enhancements, refinements, fixes and other technical improvements. Thanks to everyone who has contributed suggestions to help us improve the user experience in Practifi.

Product Enhancements

Click-to-Dial Extended to More Phone Numbers

Many Practifi organizations have a softphone integration that allows users to click a phone number from within a Practifi record and have it place the call over their internet connection. We've extended the click-to-dial feature to other places where phone numbers are displayed:

Members and Client Entities sections on the Key Records component
Contact Details component
List views where phone numbers are displayed

Relate Contacts via Relationships

We've extended the range of relationships you can use to link Client, Entity and Contact records and expanded where you can set them up. Previously, you could only establish new relationships from an Entity or Client record. Using the New Relationship action, you can now establish Relationship records directly from a Contact record.

In addition, you can link Contacts with other Contact records. This opens up a lot of possibilities. You can now map out connections between family members in other Households (e.g., siblings, parents or children) or other Contact records (e.g., accountant or attorney).

When setting up or modifying the range of available Relationship Types, we renamed the Entity Type field to Available To. We added some help text to make the intended function clear. You will now also see Contact as one of the available options.

Contact Information Added to Key Records for Individuals

We've enhanced the Overview section on Individual records to include key contact details, making it consistent with the Household and Organization page layouts.

Screenshot 2024-04-08 at 1.31.05 PM.png

The Individual's Details section displays the following contact information for the individual:

Entity (Individual) name
Age
Preferred Phone
Email

Mailing Label Field Settings for Individual and Organization Records

You can now override the default mailing label (addressee) for Individual and Organization records. Previously, this was only available for Households and Contacts. We've made the Replace Mailing Name With field available on Individual and Organization records, allowing you to override the default mailing label for that specific record.

We've also extended the custom settings that allow Practifi Administrators to define different addressee defaults for your firm.

Please note: Record-level settings take precedence over organization-wide settings.

Completed Task Confirmation Redesign

We redesigned the Mark as Complete window for Tasks to improve its informativeness and usability to complement some of the enhancements to Deliverables made in the Cabernet Franc release in February 2024.

These updated design features include:

A Completion Details section at the top of the window that displays only if at least one of the below elements is applicable for the Task
A field to enter time spent on the Task (if the Practifi - Time Tracking - User permission set is enabled)
A What was the outcome? picklist field (if available on the Task)
Info scope for the Task Actions preview (if available on the Task)
A Review What’s Been Done section, visible if the Task being completed has an Active Form, Checklist items or Deliverables that could be fulfilled

New Relationships and Relationship Types Reports

We've introduced two new report types: Relationships and Relationship Types. Fields from related Entities and Contacts have been included in these reports via lookup fields, providing comprehensive insights into relationships across your client database.

Screenshot 2024-04-08 at 1.26.24 PM.png

Feed Component Added to Sidebar on Task and Event Record Pages

We've extended the range of features available on the sidebar for Task and Event record pages by adding a Feed component. This allows you to access the Feed from any tab while working on a Task or Event record and makes the sidebar consistent with the Home page and Contact record page. The Feed component can be expanded or collapsed as needed.

Screenshot 2024-04-08 at 1.36.41 PM.png

Feed Posts Now Show Timestamps

Previously, historical Feed posts displayed rounded timestamps (e.g., 4 years ago) instead of the exact date and time of the post. The enhanced Feed component will now display exact timestamps for improved transparency and accountability.

Screenshot 2024-04-08 at 1.41.51 PM.png
Please note: This update applies only to the main Feed component on Entity records. Feed posts displayed in the side panel of Task and Event records will still show rounded timestamps.

Resolved Issues

These improvements and fixes are grouped in the following sections by product functionality.

Active Forms

Document Saved to a Process/Launch Task When Uploaded via a Pinned Field

Support for file uploads has been implemented in Active Form Pinned Fields during the creation of Process Types. This enhancement ensures that the uploaded file is saved to the launch Task when it is created.

Active Form Record-Locking Fixes

Several issues were reported related to errors caused by record locking. Records are locked in Practifi when they are being modified to prevent multiple users from updating the same record at the same time.

Pinned Active Form Fields now save asynchronously: Several users encountered an Apex Script UnhandledTrigger Exception, which indicated a failure to obtain exclusive access to specific records during an update. To prevent record locking, the trigger will now save Pinned Fields asynchronously rather than synchronously.
Active Form on Process Launch fix: Some users reported a List Exception error when launching a new Process with Active Forms on the initial Task, preventing subsequent Tasks from initiating. The Lookup Rollup Summary calculation mode was updated from real-time to scheduled to prevent record locking.
Active Form on Saving Task fix: Some users with complex Active Forms reported an Active Form error when completing a Task. The underlying cause was related to record locking rather than the Active Form.

Active Form Pinned Field Visibility for Start a Process Action

Active Form Pinned Fields were not displaying in the Start a Process window when there were no direct Active Form Fields on the initial Process Task. The workaround was to include a hidden Active Form field. The problem has been resolved, and Pinned Fields will now display as configured in the Start a Process window without requiring the direct Active Form fields.

Uploaded File Display Fix

When using a File Upload field on an Active Form component, the uploaded file's name would display twice despite only being uploaded once. Uploaded files will now display as expected.

Active Form Save to Record - Date/Time Field

We resolved an issue where updating an Active Form Date/Time field would correctly update the corresponding field on the related Entity, but leaving the field unchanged would result in an error.

Active Form Table Picklists with Commas

You can now include commas within picklist values in an Active Form Table by adding a backslash before the comma. Previously, commas were treated as delimiters, separating entries into multiple values instead of being treated as one choice. Now, if a picklist is configured as "Alpha\, Beta, Gamma" the Active Form will display the list as:

Alpha, Beta
Gamma

Map Multiple Fields to a Single Long Text Area Field in a Process

You can now map multiple Active Form fields to a single Long Text Area field on a Process, with each field name included alongside its respective value. This is consistent with mapping fields to the Task Description.

Active Forms Decimal Place Fix

Previously, Active Form fields designed for currency or number inputs did not support decimal places. Decimal number input has been enabled in Active Form fields, allowing users to input decimal values as needed.

Making Active Form Completion Consistent with Task Completion

We resolved an inconsistency between which users can complete Tasks and who can complete Active Form fields. The following users can complete a Task, check off Checklist items and fill out Active Form fields:

The Task owner or assignee
Members of the Entity's Servicing Team, as configured on the Task's Enable Advanced Execution Management? setting
Queue members, where the Task is assigned to that queue

Please note: A change was made to this functionality with the Montepulciano Minor Release - May 2024.

Task Completion with Active Form Error If Clicked Too Quickly

Some users encountered premature validation errors when attempting to complete a Task before Active Form fields finished loading in the Task completion window. To prevent these premature error messages, we've disabled footer buttons in the Task completion window until Active Form fields are saved.

Processes, Tasks and Activities

Enhancement to Default Process Name Formulation

Process Name is a text field with an 80-character limit. We updated the default Process name formation logic to utilize the entire Process name with the Entity name appended for the remaining characters. This naming convention applies to all objects accessible via the Start a Process action. For example, if starting a Process for another user record, that user’s name would be appended to the Process name.

When starting Processes as a Mass Action for multiple clients simultaneously, each Process name will reflect the respective client's name.

The automatically generated Process name will be displayed in the Start a Process window to allow users to overwrite or update the name before kicking off the Process.

Update to Process Type Deep Clone Help Text

The Deep Clone action allows Practifi Administrators to create a copy of a Process Type and its associated items. We've updated the help text to clarify that all other features of the Process and underlying Tasks—such as Outcomes, Active Form Screens, Prompts, Tables, Validation Rules, Rule Criteria and Rule Actions—will also be cloned.

Process Group Enhancement

You can now separate and categorize Processes into groups for better organization and reporting. This is particularly useful if your firm has a long list of Processes that users have to scroll through. Enabling Process Groups also aligns them with the grouping already available for Task Templates.

Users will now see an option to select a Process Group when using the Start a Process action. The picklist defaults to All Groups, and there is also an option for No Group to display all Process Types that do not have a defined Group value.

Screenshot 2024-04-09 at 10.23.31 AM.png

We've also added new Process Group filters and columns to Process list views.

Screenshot 2024-04-09 at 10.27.38 AM.png

Process Stage Group Fix

We resolved an issue where failure to define a Stage Group when configuring a Process Type resulted in an error. Stage Group is now mandatory when configuring a Process Type.

Please note: This change does not directly impact Pre-existing Process Types. However, the related Process may generate an error if the Stage Group field is not populated. If you edit a pre-existing Process Type that does not have a Stage Group defined, you will not be able to save your changes without entering a Stage Group.

Process Creation Flow Now Available for Portal Users

Even though the Process Creation flow is overridable and can be duplicated and modified, it was not available in Practifi Portals. We updated the related Apex Action method to Global, which allows the Process Creation flow to be viewed and utilized during Portal configuration.

Completed Tasks for Client Entities Fix

We resolved an issue where open Tasks related to a Client Entity were displayed under both the Client Entity and the parent Client Household/Organization (Primary Entity), but completed Tasks related to a Client Entity would appear only on the parent record.

This issue arises when a Task has different values for the Related To and Related Entity fields. Completed Tasks for a Client Entity will now display under both the Client Entity and its parent record.

Process Task Outcome Not Using Order Field

We resolved an issue where Task Outcomes were displayed alphabetically rather than in the order specified in the Order field.

Please note: This change will affect existing Outcome lists on Tasks for all Practifi organizations.

Deleted Activities Not Being Delinked from Related Tasks

We've ensured that when an Activity record is deleted, its value is promptly removed from the related Task record page. Users can now complete tasks without encountering errors.

Please note: This fix applies only to new records. As this fix operates asynchronously, completing the Task may take a few minutes as the system performs its job.

Assignment by Business Role for Task Templates and Process Tasks

The configuration of Assignment by Business Role allows for the selection of multiple Business Roles. Unfortunately, this configuration is invalid; only the first listed Business Role is assigned to the Task. We've introduced a validation message to prevent the selection of multiple Business Roles during the Task saving process.

Please note: These modifications impact the creation of new Task records but do not update existing Task Templates and Process Tasks. We recommend using queues if you need to assign Tasks to more than one team member.

Enable Reassignment of Tasks to Users and Queues

Previously, the Change Owner action only allowed Tasks to be reassigned to users. Reassigning a Task to a queue was not an option. We enabled the reassignment of Task records to users and queues, providing a more flexible user experience. To ensure consistency, we also updated the button label to Change Owner on every list view that displays a Reassign Owner/Change Owner button, including both mass actions and row actions.

Screenshot 2024-04-09 at 10.43.23 AM.png

Separation of Task Templates Page into Active and Inactive Tabs

As the List View component has a 30-record limit, we've split the Task Templates page in the Settings App into separate tabs for Active Task Templates and Inactive Task Templates, allowing more templates to be stored.

Screenshot 2024-04-09 at 10.48.41 AM.png

Removed Holdover Stages from SPA on Action Objects for Process Tasks

The Action record on a Process Task previously included picklist values that were holdover stages from Practifi’s SPA version and not aligned with available options at the Entity object/field level on the Salesforce Lightning version. These deprecated stages have been removed.

Improvements to Task Completion Notifications

When completing Tasks using row actions, we've replaced the Next button with a Finish button to make it clear to users that no more steps are required.

Completing a Task via a row action now triggers a success/failure notification, depending on the completion outcome, providing users with immediate feedback.

Completing Tasks in bulk via mass actions in list views now triggers a bell notification indicating the outcome of success or failure. Users can click on these notifications to access a batch record page displaying processing outcomes for further review.

Complete Task Mass Processing Converted to Asynchronous

The background processing for Complete Task mass actions has been converted from synchronous to asynchronous to improve performance. Users will receive a bell notification once the mass action is completed.

Tasks List Views for Other Users Fix

When viewing another user’s profile, Tasks list views displayed Tasks belonging to the logged-in user rather than the user being viewed. Tasks list views (including standalone, Process Tasks or a combination of both) now correctly display the Tasks assigned to the specified user. This has been fixed in both the User Page - Overview (Key Records) and Processes & Tasks components.

Division and User Pages Events and Calls Display Fix

We revised the Activities component on Division record pages to ensure users can view all Events and Calls relevant to their Division. This fix has been implemented across all applications for Division record pages.

Additionally, we improved the Activities component on User record pages so Activities list views now display Event and Call records where the Assigned To field matches the current user or where the current user is listed as one of the attendees of an event.

Delegated Tasks List View Fixes

We resolved an issue where delegated Tasks displayed slightly different results for the same user when viewed in different apps. Updates have been made to the queries as follows:

Business Dev (BD) - Tasks - Open delegated tasks (Home page tile and tile table)
Business Dev (BD) - Tasks - Due and overdue delegated tasks (Home page tile and tile table)
Employer Relations - Open Tasks I Have Delegated (Home page tile and tile table)
Marketing - Tasks - Due and overdue delegated tasks (Home page tile and tile table)

My Open Tasks List View Fix

We've resolved an issue where certain Tasks list views were showing only Tasks related to Entities. We've updated the query to be based on the WhoId of the Task rather than the WhatId, so the following areas will now display the running user's open Tasks, including both ad hoc and Entity-related Tasks:

Tasks page > My Open Tasks view
Tasks page > My Tasks view
Open tasks Home page tile table

Entity Records

Options for Automated Noticeboard Posts on Death of Household Member

As part of the Petit Verdot release in September 2023, we introduced the Rulebook feature. One of the pre-configured rules that shipped with the Rulebook is called Client Death. This rule automatically creates a critical Noticeboard post and creates a Task when a Date of Death is entered for a Household member. Although the Client Death rule is inactive by default, there is potential for conflict with a pre-existing Practifi setting to automatically create an important Noticeboard Post that triggers if a Date of Death is entered for a Household member.

If you prefer to utilize the Client Death Rulebook rule, we've introduced a new Custom Practifi Setting where you can disable the legacy Deceased Household Member setting. If you prefer to utilize the legacy setting, you should ensure the Client Death Rulebook rule is not enabled (it is disabled by default). If desired, you can also use the new Custom Practifi Setting to modify the default text posted to the Noticeboard if you want to use the legacy automation.

You can use one or the other of these notification options, or you can disable both if you do not want a Noticeboard post to be created when a Household member passes away. We do not recommend enabling both options, as this will result in duplicate Noticeboard posts.

Description Field Fix on Conversion of a Contact to an Individual

When a Contact associated with a Household or Organization is converted into an Individual using the Convert to Individual action, any previous data saved in the Description field on the Contact's Basics page is now retained.

Convert to Individual Preferred Phone Fix

We resolved a mismatch between the Preferred Phone for a Client and a Contact, which could cause an error upon conversion of a Contact record to an Individual record using the Convert to Individual action.

Add Individual to Household/Organization Address Fix

We fixed an issue where adding an Individual to a Household or Organization would overwrite the original address, even though the Exclude Address from sync checkbox was selected. Practifi will now retain the original address listed in the Individual record before addition to the Household or Organization.

Missing Feed Posts When Adding an Individual to a New Household/Organization

We resolved an issue where adding an Individual to a new Household or Organization did not retain the Individual's Chatter Feed posts.

Please note: The Feed from the Individual may not immediately appear due to the job running asynchronously. You may need to refresh the browser page to see the Feed in the Household/Organization record immediately, or you can wait for the job to auto-run.

Missing Address When Adding an Individual to a New Household/Organization

We introduced a check to prevent the sync of Household to Contact record addresses if no Primary Entity exists in the Household.

Structure Tab Fix Where Client Stage is Null

The Structure tab will now be displayed for Entities with no Client Stages recorded and will include Individuals, Households and Organizations.

Updated Division Logic When Updating Entity Owner

One of the key methods for keeping Client records separate and distinct between different firms or business units in the same Practifi organization is by setting up Divisions and Sharing Rules based on those Divisions.

We recommend that each User record in Practifi has a Primary Division assigned so that records owned by that user (such as Client records) inherit the user’s Primary Division. When a Client record's owner changes (generally when the client's main advisor changes), the Related Division of the client should typically update to reflect the new owner's Primary Division.

However, in cases where the new owner is a member of multiple Divisions, particularly if they have the original user’s Primary Division as one of their secondary Divisions, this transition may not occur as expected, and the Division on the Client records may not get updated.

To address this, we've introduced a new setting that allows Practifi Administrators to manage such exceptions independently. Additionally, we've ensured alignment with existing functionality by integrating with the Populate_Related_Division_from_Entity__c trigger setting, which copies over Related Division values from parent Entities to their child records. However, exceptions are made for Account and Financial Product objects, as they are the highest level in the Practifi hierarchy and cannot utilize this setting. Instead, they will always utilize the new setting.

For seamless integration with existing functionality, we created a new organization-wide custom field in Custom Metadata Types > Practifi Feature Settings called Inherit Related Division To with the following options:

Always Set to Owner's Primary Division: When the Entity owner changes, the Related Division inherits the new owner's Primary division, regardless of the new owner's memberships in multiple Divisions.
Remain Unchanged if Owner Belongs to Division: When the Entity owner changes, the Related Division retains its existing value if the new owner is a member of that Division, preventing unnecessary updates to the Division.

This setting lets Practifi Administrators control how an Entity's Related Division is inherited during record creation or update, aligning with their organizational structure and processes. If the new owner belongs to multiple Divisions, including the Entity's current Related Division, clients can choose whether the Entity retains its existing Division or migrates to the new owner's Primary Division based on their reporting and operational preferences.

Please note: The new Inherit Related Division To setting is not added to the Custom Metadata layout of existing Practifi organizations by default. It must be manually added.

Allow Division Selection on Entity Creation

Where a user is a member of multiple Divisions, we've introduced enhancements to allow them to specify the Related Division during Entity creation. This ensures Entities and their child records are created with the correct Division.

When creating a new Entity (Household/Organization/Individual), users will see a new Owner lookup field beneath the Source field and a Related Division field that defaults to the Primary Division of the selected owner, if available, in the Entity creation flow. The picklist only shows Division options where that user is a member.

If the selected owner is not associated with any Division, the Related Division field will not be displayed, enabling users to proceed with Entity creation without assigning a Division.

Please note: This enhancement is being made to the default global layout. Existing Practifi organizations with modified flows for Entity creation will not see these improvements.

Promote to Prospect Flow Fix

We resolved an issue where the Promote to Prospect flow would fail if organization default triggers were disabled and only local user triggers were enabled. This typically only occurs as part of large manual data loads, such as onboarding a new set of clients or migration from a previous database. The Promote to Prospect flow now functions reliably even when organization default triggers are disabled and only local user triggers are enabled.

Refinements to Salutation and Sex fields

We've refined the behavior and available picklist options for the Salutation and Sex fields in various member addition flows:

The Salutation field has been made non-mandatory and allows users to select None if applicable.
The Sex field has been relabeled to Gender to align with the field naming convention in the Contact object. It has been made non-mandatory and includes the following picklist options to match those on the Contact record page:
- None
- Male
- Female
- Other

The following flows have also been updated:

New Member (Household and Organization)
Add Organization Member - (Create a new member)
Add Household Member - (Create a new member)

Edit Owner Button Now Hidden

Several automations occur when updating the owner (usually the main advisor) of an Entity or Client. Users can update the owner on related child records such as Household Members, Open Processes & Tasks, Active Services and Assets & Liabilities. There is also the ability to retain the existing Servicing Team.

Previously, it was possible to bypass this automation by clicking the Edit button in the Account Owner field rather than the intended method of using the Change Owner button in the record side panel. We've now hidden the Edit button to ensure consistency and promote the best practice of using the Change Owner flow.

Assets and Liabilities

Asset/Liability Role Character Limit

When adding a new Role for an Asset or Liability (e.g., Owner or Beneficiary), a name for the Role is automatically created by appending the Asset/Liability name to the Client name. When this Role Name exceeds the 80-character limit, users can manually shorten it and save it without encountering an error.

Automatic Creation of Asset/Liability Role

When a related Client is recorded on an Asset/Liability and the Asset/Liability Role field is blank, a new Role of Owner will automatically be created for that Asset with the primary member of the related Client. This is particularly important for Assets such as those sourced via the Tamarac integration, where all Assets are created during the bulk sync regardless of whether the Asset is linked to a Client. This can then impact RMD eligibility rules as one of the criteria is Asset Role = Owner.

Please note: Existing Assets without a Role recorded will require a mass update for the changes to take effect.

Asset/Liability Fix for Client Entities

Previously, when recording an Asset/Liability against a Client Entity (e.g., an Entity such as a Trust or Private Company as part of a parent Household), the Client Entity would be displayed as both the Related Entity and the Client. This behavior has been amended so that the Client Entity will continue to be the Related Entity, but the parent Client (typically a Household) will now show in the Client field.

Please note: This update will only impact newly-created records.

List Views

List Views for All Records Fix

We resolved an issue where the Entity query on the Directory page displayed more records than expected when the filters were open (i.e., All Records). This was also the cause of a discrepancy between the actual number of records displayed and the number shown at the top of the list view. We updated the filter queries for the Directory and Pipeline pages to ensure only the expected records are displayed.

List Views Record Selection Fix

We resolved an issue where selected records persisted across different list views when switching between them or refreshing the view. The counters indicating the number of records selected, displayed and in total will now refresh when switching list views.

Data Management App List View Fix

We resolved an issue where some list views in the Data Management app were not displaying all records due to the hideNone attribute being set to True in the JSON filters. We've removed the hideNone attribute from the filters, ensuring list views display all intended records.

Management App Queue Filter Fix

The All Tasks view on the Tasks page in the Management app includes filters for both Assigned to Queue and Assigned to User, but the Queue filter only showed records assigned to the running user who is a member of the queue. We've merged the Assigned to User and Assigned to Queue filters into a single filter called Assigned To that combines options for both Users and Queues and functions according to the selected criteria. Additionally, the Owner column in the All Tasks list view was renamed to Assigned To to maintain consistency.

Integrations

Microsoft 365 Event Description Truncation Fixed

The Microsoft 365 Event Description synced into Practifi was previously truncated to 250 characters. The Event Description now syncs accurately into Practifi without truncation.

Microsoft 365 Multi-Day Events

We resolved an issue where multi-day events from Microsoft 365 were displaying as single-day events in Practifi. Multi-day events are now accurately reflected in Practifi.

Updated Addepar and Black Diamond Integration Pages to Support Search

The search function on Addepar and Black Diamond integration pages displayed errors that required manual backend configuration to enable Allow Search. We've also added new filtering options in the Integrations list view to allow you to easily see imported portfolios that are not linked to Practifi portfolios.

MoneyGuide Integration Can Include Prospect Data

We've enhanced the MoneyGuide integration to transfer data from Practifi for both Prospects and Clients. Previously, only Client records were transferred.

New Rollup Added for Revenue Installments

We added a Lookup Rollup Summary to sum Installments for the last 12 months to the Revenue Last Year (Rolling) field on the Asset/Liability object. This feature enables Orion Connect and any future integrations that populate the Installment object to calculate this field.

Miscellaneous

Deliverable Descriptions Now Display Rich Text

A new Description field was added as part of the Cabernet Franc release in February 2024 to allow Practifi Administrators to better customize and provide clarity to users around the Deliverables associated with your firm’s Services. Although the Deliverable configuration allowed rich text, we resolved an issue where the formatting was lost when users viewed the Deliverable's description by hovering over the Info icon.

Restricted Picklist Fix

We resolved a Script Exception error that occurred when updating restricted picklists where the API name no longer matched the field label, usually when a picklist label was amended from the default Practifi value.

Stage History Fix for Renamed Stages

The Stage History for various objects—including Deal, Service, Process, Entity and Tasks—was recording the Stage API field name rather than the Stage name (Label). Where a Stage was renamed or relabeled, the original Stage name would be shown rather than the new name. Stage History now accurately reflects the relabeled Stage name as intended.

Updated Policy Permission Set Name

The permission set Practifi - Additional Features - Policy Coverage User has been renamed Practifi - Additional Features - Policy to reflect its purpose better. This helps avoid confusion, as there is a separate permission set specifically for Policy Coverage, which retains its original name Practifi - Additional Features - Policy Coverage.

Division and Financial Product Headings Display Fix

Division and Financial Product headings were not displaying on their respective Lightning pages. We've corrected the CSS styling issue to ensure these headings display correctly.

Layout Enhancements for Private Investment Records

On Private Investment records, we've added a new Progress & Key Dates section with Stage, Start Date and End Date fields, allowing you to track progress and key dates effectively.

New Button for Personal Security Questions

The mechanism for adding a new Personal Security Question was not intuitive, so we've added a New button on the Personal Security Questions related list on Entity records.

Please note: This update only impacts organizations that have enabled the Security Check feature.

Sharing Defaults for Services Set to Public Read/Write

To ensure that all users can access the Service object and to reduce the effort when customizing Sharing Rules, we've set sharing defaults for the Service object to Public Read/Write.

Please note: This change will only impact new Practifi organizations and will not be automatically applied to existing organizations.

Service Page Hyperlink Fix

When clicked, the hyperlinked names of Service records in the Services & Pipeline section of User records were not working as expected. We've addressed this issue, and hyperlinks function correctly on the Services tab within User records.

Montepulciano Minor Release - May 2024

In mid-May 2024, we rolled out an update that allows more flexibility regarding which users can complete Tasks.

Process Tasks and Task Templates

Process Task and Task Template records have an Enable Advanced Execution Management? checkbox. When enabled, this setting allows administrators to specify servicing team member roles or business roles who can execute the task.

When Advanced Execution Management is enabled, the following users can complete Tasks, check off Checklist items and fill out Active Form fields for the Task:

The Task owner or assignee.
Members of a queue, if the Task is assigned to a queue.
Members of the Advanced Execution Team, as specified in the Task's settings.

When Advanced Execution Management is not enabled for a Process Task or Task Template, any user can complete the Task, check off Checklist items and fill out Active Form fields.

Personal Tasks

The Advanced Execution Management setting does not apply to ad-hoc personal tasks. This means that any user can complete them.

Change Log

Each of the features and enhancements in this release that modify configurable product areas describes the affected areas in their section of the release notes. This section consolidates each of those into a singular table, making it easier to get a sense of the release’s changes as a whole.

🔧 Implementation Details The below product areas 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?
Addepar integration	Updated Addepar and Black Diamond Integration Pages to Support Search	Automatic Allow Search Activation: The TSO now automatically enables the Allow Search attribute for the practifi__Addepar_Portfolio__c and object. Addepar Portfolio Filtering: To assist users in filtering Addepar portfolios linked to Practifi clients, we introduced the Linked to Client formula text field in the Addepar portfolio object. This field indicates whether a portfolio is linked to a Practifi client. New Filter in Integrations List View: We added a Linked to Client filter in the Integrations list view, allowing users to filter Addepar portfolio records based on their linking status to Practifi clients. Display of Linked to Client Field: The Linked to Client field is now visible as a column in the Addepar Portfolios Integrations list view, providing users with quick visibility into portfolio linking status.
Asset trigger	Automatic Creation of Asset/Liability Role	The Asset trigger has been updated to create an asset role only if the Client (practifi__Client__c) field has been set during the update and if there isn't already an existing asset role linked to the asset. Please note: Existing assets will require a mass update for the changes to take effect. Please ensure to perform this update to maintain consistency and alignment with the enhanced trigger behavior.
Asset/Liability trigger	Asset/Liability Fix for Client Entities	When creating or updating an Asset/Liability record within a Client Entity, the Related Entity field pulls in the Parent ID of the Client field. This ensures that the Client field displays the Client Entity value, while the Related Entity field accurately reflects the Household/Organization value of the Client Entity. Please note: This updated trigger only impacts new records.
Black Diamond integration	Updated Addepar and Black Diamond Integration Pages to Support Search	The TSO now automatically enables the "Allow Search" attribute for the practifi__Black_Diamond_Portfolio__c object.
Contact record page	Edit Owner Button Now Hidden Relate Contacts via Relationships	To promote best practices and ensure consistency, we've hidden the Edit button for the Account Owner field because clicking this button displays the standard Salesforce Change Owner action, bypassing our custom automation. Added the New Relationship action button on the contact record page to establish new connections to and from the contact. This action covers both Contact-to-Contact and Contact-to-Entity relationships. Relationships created through this action will appear in the contact record's Relationships tab and will also be aggregated under the associated Primary Entity.
Custom Metadata Types	Updated Division Logic When Updating Entity Owner	We've introduced a new setting called Inherit Related Division To to manage Division updates when an Entity's owner changes, especially in cases where the new owner is part of multiple divisions, potentially causing the Related Division to remain unchanged. This setting, found in Custom Metadata Types > Practifi Feature Settings, offers two options: Always Set to Owner's Primary Division: The Related Division inherits the Primary Division of the new owner, regardless of other Division memberships. Remain Unchanged if Owner Belongs to Division: The Related Division retains its current value if the new owner is a member of that Division. Please note: For existing Practifi organizations, the Inherit Related Division To setting must be manually added in Custom Metadata Layouts in Setup.
Custom Settings	Options for Automated Noticeboard Posts on Death of Household Member	We introduced a new custom setting called Show NoticeboardPost for Deceased Member. When this setting is enabled, our codebase automatically generates an Important level noticeboard post on a Household record whenever a related member is marked as deceased. The content of the Noticeboard post can be customized using the existing custom setting Noticeboard Post For Deceased HH Members that we already have in place.
Data Management app Tasks page	Data Management App List View Fix	On the Tasks view, we merged the Assigned to User and Assigned to Queue filters into a single Assigned To filter. This combined filter now includes options for both Users and Queues and operates based on the selected criteria. We renamed the Owner column to Assigned To in order to maintain consistency with the filter label.
Entity record page	Edit Owner Button Now Hidden Structure Tab Fix Where Client Stage is Null	To promote best practices and ensure consistency, we've hidden the Edit button in the Account Owner field because clicking this button displays the standard Salesforce change owner action, bypassing our custom automation. Our custom Change Owner action on the sidebar of Entity record pages triggers several automations when updating the owner. We encourage users to utilize this sidebar action for owner changes. We upgraded the Structure tab to display Entity Structure for all client stages, including Blank stage, for Individuals, Households and Organizations.
Event record page	Feed Component Added to Sidebar on Task and Event Record Pages	On the Event page layout, the sidebar displays Deliverables. The Feed component is now positioned below the Deliverables section. If Deliverables are disabled, the Feed component appears independently on the sidebar. To improve usability, the Feed component is presented as an accordion, allowing users to expand or collapse it as needed.
Financial Product record page	Layout Enhancements for Private Investment Records	Added the following fields to the Financial Product page layout: Stage Start Date End Date These fields are now part of the new Progress & Key Dates section, positioned above the existing Target & Performance section.
Individual record page	Contact Information Added to Key Records for Individuals Refinements to Salutation and Sex fields Mailing Label Field Settings for Individual and Organization Records	The Individual record page Overview includes a new section titled Individual’s Details. Name, Age (if not deceased), Email and Preferred Phone are displayed. The format of the Individual's Details section matches that of the Household Members and Organization Members sections seen on Household/Organization record pages. For deceased Individuals, the system displays a Deceased label instead of their age and the Email and Phone fields are hidden. Instead, Birthdate and Date of Death field values are shown. The Gender field has been added to the Basics tab on the Individual record page layout to be consisent with the Contact record page. Added the Replace Mailing Name With field on Individual record pages in the Mailing Label section. This allows users to replace the Entity's name on the Mailing Label with custom text.
Lookup Rollup Summaries	New Rollup Added for Revenue Installments	Added Installments to the Revenue Last Year (Rolling) Lookup Rollup Summary, which facilitates its calculation by Orion Connect and future integrations managing Installment object data. Please note: This Lookup Rollup Summary is inactive by default and requires activation.
Management app Tasks page	Management App Queue Filter Fix	For the All Tasks view, we merged the Assigned to User and Assigned to Queue filters into a single Assigned To filter. This combined filter now includes options for both Users and Queues and operates based on the selected criteria. We renamed the Owner column to Assigned To in order to maintain consistency with the filter label.
New Member flows	Refinements to Salutation and Sex fields	We updated the Salutation and Gender fields in the following flows: New Member for Households and Organizations Add Organization Member - (Create a new member) Add Household Member - (Create a new member) Previously, Salutation was required with a None picklist option. Now, it's optional, allowing users to choose None if needed. The Sex field has been changed to Gender. It was previously required and limited to Male and Female options. It is now optional with picklist options for None, Male, Female and Other, aligning with the Contact object's practifi__Gender__c field.
Organization record page	Mailing Label Field Settings for Individual and Organization Records	Added a new field called Default Mailing Name for Organizations in the Mailing Label section.
Orion Connect integration	New Rollup Added for Revenue Installments	Added Installments to Revenue Last Year (Rolling) Lookup Rollup Summary, which facilitates its calculation by Orion Connect and future integrations managing Installment object data. Please note: This Lookup Rollup Summary is inactive by default and requires activation.
Permission Sets	Updated Policy Permission Set Name	Renamed the Practifi - Additional Features - Policy Coverage User" permission set to Practifi - Additional Features - Policy for clarity. This adjustment distinguishes it from the Practifi - Additional Features - Policy Coverage permission set.
Personal Security Questions	New Button for Personal Security Questions	Added a New Button on the Personal Security Question Related List for Entity records. Please note: This update only impacts organizations that have enabled the Security Check feature.
Process Stage record page	Process Group Enhancement	We made the Group picklist field required on Process Stage records associated with a Process Type. This change prompts users to specify a group, preventing NULL values and potential errors. Please note: Existing Process Stage records are unaffected unless they are edited.
Process Task record page	Removed Holdover Stages from SPA on Action Objects for Process Tasks	We removed holdover stages from the Action record on Process Tasks to ensure alignment with available options at the entity object/field level in Salesforce Lightning. Previously included stages like "Qualified Out," "Deceased client," and "Unqualified" have been removed, retaining only values consistent with those seen at the entity level: "Prospect" "Lost prospect" "Client" "Lost client." This adjustment ensures consistency between stages in the Action record and those at the entity level.
Process Type Deep Clone action	Update to Process Type Deep Clone Help Text	Updated help text: "You're about to make a copy of this Process Type, which includes all of the records that comprise its configuration, such as Process Tasks, Actions and Active Form Fields. This could cause a lot of records to be created. Are you sure you want to continue?" Please note: The Deep Clone action remains unchanged in functionality, ensuring the cloning of all relevant components associated with the Process and Task(s).
Relationship Type record page	Relate Contacts via Relationships	Renamed the Entity Type field to Available To on the Relationship Type record. Added Contact as an option to the choices in the Relationship Type multi-select picklist and included relevant help text for this field.
Settings App Task Templates page	Separation of Task Templates Page into Active and Inactive Tabs	The Task Templates page in the Settings app now has separate tabs for Active and Inactive Task Templates list views.
Start a Process flow	Enhancement to Default Process Name Formulation	We've enhanced the default Process name formation logic to incorporate the entire Process name, appending the object's name for the remaining characters based on the context of the object on which it was invoked. This naming convention applies to all objects accessible via the Start a Process action. The automatically generated process name will appear in a text field in the Start a Process window, allowing users to overwrite or update the name before initiating the Process.
Task Change Owner action	Enable Reassignment of Tasks to Users and Queues	We replaced the existing lookup field in the Change Owner workflow with a custom multi-object lookup component that allows users to select between Users and Queues for task reassignment. The button label across all list views displaying the Reassign Owner/Change Owner button has been updated to Change Owner, ensuring a uniform user experience.
Task completion flow	Completed Task Confirmation Redesign	The updated design for the Mark as Complete window includes: A Complete Details section is displays the following, depending on how the Task is configured: Time tracking functionality (if the permission is enabled) Outcome selection picklist (if available on the task) Info scope for Task actions preview (if available on the Task) A Review What’s Been Done section if the task has An Active Form, Checklist items or Deliverables it could fulfill.
Task record page	Feed Component Added to Sidebar on Task and Event Record Pages	On the Task record page, the sidebar includes sections for the Checklist and Deliverables. The Feed component is now positioned below the Deliverables section, providing easy access to updates and discussions. If Deliverables are disabled, the Feed component appears beneath the Checklist. To improve usability, the Feed component is presented as an accordion, allowing users to expand or collapse it as needed.