Overview
The following article covers what's new in our Vermentino release (beginning in November 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.
With Vermentino, we're giving you more frequency and due date options for Deliverables. We also continue to respond to user feedback with enhancements, refinements, fixes and other technical improvements.
- Product Enhancements
-
Resolved Issues
- Liking Feed Posts with Attachments
- Editing Feed Posts with Attachments
- Email Address Sync Issue
- Home Page Tiles Filter Set Error
- Enhanced Help Text for Default Household Name Setting
- Household and Organization Creation Display Fix
- Field Length Fix for Withdrawals on Assets
- Constant Contact Duplicate Email Issue
- Constant Contact Apex CPU Limit Error
- Retry Errors for Microsoft 365 Email and Event Sync
- All-Day Event Sync with Microsoft 365 Fix
- Calendar Event Reassignment Fix in Microsoft 365
- Outlook Email Image Display Issue
- Addepar Trusts and Holding Companies Sync Error
- Vermentino Minor Release - December 2024
- Change Log
Product Enhancements
Flexible Scheduling for Deliverables
In our Pinot Blanc release, we introduced several enhancements to our Deliverables feature. With this release, we continue to make Deliverables more configurable, specifically when determining how often they should be fulfilled and when they should become due.
Configure Custom Frequency Lengths
Previously, frequency options for Deliverables were limited to traditional calendar periods like monthly, quarterly and semi-annually. We're adding three new options—Every X months, Every X weeks and Every X years—to allow Practifi Administrators to specify how long the period should be by providing the value for X in a separate field.
When calculating due dates, the last calendar day of the specified period becomes the due date.
Please note: When you change the Frequency field value of a Deliverable Type and click the Sync with Services button, the system prompts you to decide how the due dates for existing Deliverables should be recalculated. This applies to all frequencies except the options for Every X weeks, Every X months and Every X years.
There's an exception for these three scenarios: the prompt is triggered only when the X Value field is changed, but not when other conditionally rendered fields are modified. For example, if you've selected the Every X weeks frequency and change the X Value field, the prompt appears. However, if you modify the Day field in the Scheduling section (which appears conditionally), the system does not ask the recalculation question.
Set Custom Due Dates
Before this release, when a Deliverable Type’s Initial Calculation Basis was set to Based on Calendar Period, the end of the calendar period was used as the due date. There was no way to set a due date any earlier, such as a Deliverable with an annual frequency that would be due on April 15th rather than December 31st.
To address this limitation, the Based on Calendar Period option has been renamed Based on End of Calendar Period, and we've added a new option called Based on Date During Calendar Period. This enables scenarios like the one mentioned above to work as intended.
The configuration options for the Date During Calendar Period option are the same as those used when configuring recurring tasks. Practifi Administrators can specify either a Specific Date (a fixed numerical date within the period, e.g. the 15th day of the month) or a Relative Date (a day whose numerical date varies depending on when the period begins, e.g. the first business day of the month).
Both Initial Calculation Basis options have additional fields that display conditionally depending on selected options. These are described in the Change Log below.
Considerations
Please keep in mind the following about the scheduling of Deliverables:
- To ensure consistency, due date calculations will be the same for both initial and ongoing schedules. If the initial date is the 15th of every month, the subsequent due dates will also be the 15th.
- When the Initial Calculation Basis is set to Based on Date During Calendar Period, we recommend setting the Ongoing Calculation Basis to Based on Due Date. However, if you opt to set the Ongoing Calculation Basis to Based on Fulfillment Date, it is important to understand that subsequent due date calculations for Deliverables may not occur at consistent intervals aligned with the chosen frequency.
- If a Deliverable is fulfilled significantly earlier than the scheduled due date, the X year cycle will begin counting from the early fulfillment date. This adjustment may lead to inconsistencies in the anticipated due dates every X years, as the cycle is reset based on the early fulfillment rather than the original schedule.
- On the Deliverable Type record, there is a fulfillment setting called If It Isn't Fulfilled By Its Due Date, which can be configured as "Treat it as overdue". With this configuration, a Deliverable can be fulfilled after its scheduled due date. Such cases may result in inconsistencies in the anticipated due dates every X years. In some instances, it may involve skipping expected frequency intervals if the Deliverable is fulfilled significantly later than the original due date, as the cycle is reset based on the late fulfillment rather than the original schedule.
New Contact Address Sync Control Setting
By default, when an Entity (Account) is created, two fields on the new Entity—Sync Postal Address with Members and Sync Location Address with Members—are set to True. These settings are located on the Basics tab of the Entity record and will automatically sync the Entity’s address to its associated members (Contacts/Individuals). When these settings are enabled, Entity-level addresses overwrite Contact-level addresses, even when Contact addresses may have been populated by a data import.
To prevent unintended data overwrites, we’ve introduced a new setting called Contact Address Sync Control, which can be found under Custom Settings > Practifi Settings in Salesforce Setup. This enhancement provides more control over address syncing, reducing the risk of unintended data loss while offering flexibility for managing addresses at both the organization and record levels.
Please note the following about the implications of this new setting:
Contact Address Sync Control Enabled | Contact Address Sync Control Disabled |
The Entity address to Member address sync is disabled. Address syncing is turned off across all records in the organization. |
Organization-wide sync is enabled; address syncing is active across the organization. |
Record-level fields are overridden. Regardless of the Sync or Exclude field settings at the record level, addresses will not sync between Entities (Accounts) and Members (Contacts). |
Record-level controls are active. Users can manually control address syncing using the Sync fields on Accounts and Contacts. Sync behavior will follow the settings for each individual record. |
For existing Practifi organizations, the Contact Address Sync Control setting will be disabled by default to preserve current sync behavior. New Practifi organizations from November 2024 will have the Contact Accress Sync Control setting enabled by default to prevent Contact addresses from being overwritten by Entity addresses during data imports or when adding new Contacts to an Entity.
Considerations
Please keep in mind the following:
- When the Contact Address Sync Control setting is on, address syncing between Accounts and Contacts will not occur, even after data imports.
- When the Contact Address Sync Control setting is off, addresses will sync according to the default behavior (Sync fields on Accounts are checked and Exclude fields on Contacts are unchecked).
- Exercise caution when disabling the Contact Address Sync Control setting, as Contact addresses may be overwritten with the Entity’s address during Account edits (depending on the record-level settings).
- If you need different sync behavior for different records, the setting can be disabled to allow syncing. Then, you can manually adjust the sync fields on individual records to prevent or enable address syncing as needed.
Salutation Field Updates
When creating an Individual, Household or Organization via the Global Actions menu or when adding new members to a Household or Organization, "None" is now available as a picklist value in the Salutation field. This improves consistency, as "None" was previously available when editing Contact records but not when creating them via Global Actions or Entity actions. There is also a new Salutation picklist option for "Mx.".
The Salutation field now has the following values available:
- None
- Mr.
- Ms.
- Mrs.
- Dr.
- Prof.
- Mx.
We've rolled out this change to the following Flows:
- Create an Individual: Allows the creation of contacts without a predefined salutation.
- Create a Household: Available for primary, spouse and dependents.
- Create an Organization: Available for organization members.
- Entity Actions:
- New Member
- Add Household Member
- Add Organization Member
Please note: This enhancement will be automatically included in all Practifi organizations created after the Vermentino release. For existing Practifi organizations, the Salutation picklist must be edited in Salesforce Setup to make the new values visible. For more information, please see our Managing Custom Fields and Picklists article.
Version Control Visibility for Risk Profiles
In our Zinfandel release, we introduced version control for Risk Profiles, allowing Practifi organizations to preserve previous versions of questionnaires rather than overwriting them when making edits. In this release, we're giving firms improved visibility into which version of the Risk Profile question set is used for each client. We've made changes to the following areas:
- Risk Profile page: The Version field has been added as a default column in the Risk Profile list view on the Client record.
- Client Risk Profile Basics tab: The Version field now appears on the Basics tab of the Risk Profile record, positioned below the Owner field.
Please note: When making changes to your firm's questionnaire, we recommend creating a new version of the existing question set and activating it to ensure that any updates are reflected in the new version. Making changes directly to an old question set may result in modifications to existing Risk Profile questions associated with the previous version. You should only change a previous version of the question set to address issues such as typos. To learn more about working with question sets, please see 📚 Understanding and Managing Risk Profiles.
Resolved Issues
Liking Feed Posts with Attachments
An error occurred when users attempted to like or dislike Feed posts with attachments. This issue has been resolved, and users can now interact with these posts as expected.
Editing Feed Posts with Attachments
Feed posts that contained only attachments (i.e., no text or other content) were not editable. This has been resolved, and users can now make changes to these posts using the Edit function.
Email Address Sync Issue
Deleting an email address from the Basics page of an Individual record did not update other areas where the email address was displayed. The PersonEmail and Email__c fields are now synced for insert, update and delete actions to ensure that any email address updates made on the Basics page are reflected across the following areas:
- Overview - Key Records card
- Contact Details card
- Client and Directory list views
Home Page Tiles Filter Set Error
Certain Home page tiles, including the Open Delegated Tasks and My Tasks tiles, displayed a filter set error. This issue prevented users from filtering records within the tile tables. We implemented a product-level fix to restore full filtering functionality, allowing users to filter and view tasks without issues.
Enhanced Help Text for Default Household Name Setting
We've updated the help text for the Default Household Name field in the Household Name Settings custom setting to improve clarity. This setting lets you define the default format for newly created Household names.
Please note: This setting applies only to Households created after setting this format. To update names for existing Households, use the Update Household Names action available in the Clients page in the Data Management app.
Household and Organization Creation Display Fix
Users were unable to enter Spouse details using the Create a Household global action. Similar issues were reported when trying to enter additional Employee details when using the Create an Organization global action. An update to CSS settings has resolved the issue and all relevant fields now display as expected.
Field Length Fix for Withdrawals on Assets
The Withdrawals Last 12 Months field on the Asset Liability object was incorrectly limited to a single-digit input. It now supports values up to 16 characters long (including 2 decimal places), which is the standard length for currency fields in Practifi.
Constant Contact Duplicate Email Issue
Constant Contact list memberships for Entities and Contacts were not syncing correctly, particularly when multiple records with different names shared the same email address. Constant Contact treats emails as unique identifiers, causing only one record to sync and leaving the others unsynced. We updated the logic to ensure name matching occurs for all records with duplicate emails. This ensures that all Constant Contact memberships sync correctly, even when duplicate emails exist.
Constant Contact Apex CPU Limit Error
The Constant Contact activities sync was failing due to Apex CPU time limit errors, even after reducing the activity batch size and increasing API limits. We've reduced the Sync Tracking Activities Batch Size to 1 from the default value of 5, ensuring that the sync no longer exceeds CPU limits and preventing further failures in the nightly Constant Contact sync.
Retry Errors for Microsoft 365 Email and Event Sync
A new Retry Errors from Last 30 Days button has been added to the Logs & Errors tab on the Microsoft 365 Sync page in the Settings app. This button allows users to retry all email and event sync errors from the past 30 days with a single click, simplifying and speeding up error resolution.
All-Day Event Sync with Microsoft 365 Fix
Following a Microsoft outage, some all-day events created in Practifi failed to appear on relevant Outlook calendars despite the sync running successfully. The issue has now been resolved and all events now display as expected.
Calendar Event Reassignment Fix in Microsoft 365
We have resolved an issue where transferring an Event from one user to another in Practifi would not remove the Event from the original calendar or would generate a duplicate entry. Now, when a meeting is reassigned, it updates correctly on the new user's calendar without duplicating or remaining on the original user's schedule.
Outlook Email Image Display Issue
When users send Outlook emails containing images using the Microsoft 365 Email integration in Practifi, the images appear broken in both the email body and as attachments within Practifi. Additionally, recipients of these emails do not receive the images correctly. Updates have been made to the Azure function to resolve this issue. Moving forward, images sent via Outlook emails will now display correctly in both the email body and as attachments within Practifi.
Please note: This fix will only apply to new emails synced into Practifi after the update.
Addepar Trusts and Holding Companies Sync Error
Addepar portfolios tied to trusts or legal entities were not syncing properly with Practifi, even when the Sync Trusts and Holding Companies setting was enabled. Only performance data was syncing, and the associated client entities or assets were not being created. We've added a check to handle null values in the integration. If a value is null, the process skips the affected section and continues with the next step. This ensures the integration completes as expected, creating client entities and assets as needed.
Vermentino Minor Release - December 2024
The following changes were rolled out in an update in December 2024:
- Event created with attendees not populating: We resolved an issue with the Microsoft 365 Sync where event attendees were populating, only to be immediately deleted.
- Improved email matching in Microsoft 365 Sync: Some emails in the Microsoft 365 Sync were not appearing in the Matched or Unmatched lists but only in the All Emails list, impacting email storage management. Only emails created from Microsoft 365 Sync are displayed.
-
Table page error for non-admin users: We fixed an issue where non-admin users encountered a Type Error message "t.typeAttributes.rowActions.forEach" when accessing pages containing tables. The root cause was an unintended Security Check user permission being assigned to certain user profiles. To address this, we made the following changes:
-
User permission set groups have been updated to exclude the Security Check permission.
-
The Security Check permission has also been updated to prevent errors if it is manually added to a user in error.
-
- AUM tile calculation issue: We resolved an issue where AUM tiles were displaying incorrect values, such as showing $7 instead of the correct amounts in the millions. This was caused by an overflow error when handling large numbers. The tile calculations have been corrected to ensure accurate AUM values are displayed.
-
Process Task error with queueable jobs: We addressed an issue where completing a Task failed to trigger associated actions, such as creating a new Service or Process. This was caused by conflicts with Salesforce governor limits after transitioning from platform events to queueable jobs. Processing logic was revised to divide each platform event into separate transactions. This ensures each transaction operates under its own governor limits, preventing conflicts.
- Constant Contact sync improvements: Fixed a Null Pointer Exception that caused the Constant Contact sync to fail.
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 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? |
Asset/Liability Object | Field Length Fix for Withdrawals on Assets |
|
Client Record - Risk Profile - Basics Tab | Version Control Visibility for Risk Profiles |
|
Client - Risk Profile Data Table |
|
|
Custom Settings | New Contact Address Sync Control Setting |
|
Enhanced Help Text for Default Household Name Setting |
|
|
Deliverable Type and Deliverable objects | Flexible Scheduling for Deliverables |
|
The following required fields display conditionally based on the selected Date Type and Frequency values:
|
||
Entity Actions
|
Salutation Field Updates |
We’ve introduced a new None option to the Salutation picklist across various global and entity actions to provide consistent options when creating records. The Salutation field now includes the following picklist values across all relevant global and entity actions:
Flows Updated:
Additionally, these global actions are now flow-based, ensuring better control of picklist values in alignment with the data model. Consistent Salutation options now apply to the New Member, Add Household Member and Add Organization Member Entity actions. |
Global Actions:
|
||
Microsoft 365 Sync Settings App Page | Retry Errors for Microsoft 365 Email and Event Sync |
|
Comments
Article is closed for comments.