Pinot Blanc - July 2024

Follow

Overview

The following article covers what's new in our Pinot Blanc release (beginning in July 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 Pinot Blanc, we're adapting Deliverables, Deals and Services to accommodate a wider range of use cases.

Release Highlights

Deliverable Enhancements

Activation Rules for Deliverables

Because not all clients need the same level of service, your firm might want to tailor Deliverables to fit different client types. Practifi already allows users to create ad-hoc Deliverables on a client's Service record, but this process is manual. With this release, we're introducing the ability to activate Deliverables automatically when specific criteria are met. For example:

  • If Client Segment = Platinum, activate the Quarterly Review Deliverable
  • If Client Segment = Gold, activate the Semi-Annual Review Deliverable
  • If Client Segment = Silver or Bronze, activate the Annual Review Deliverable

Practifi Administrators can create one or more rules using the new Activation Rules tab on Deliverable Type records. The system checks these rules daily. Any existing Deliverables for which the activation rules are true will have their status set to Active. If a Deliverable does not meet the criteria, its status is Inactive. 

Screenshot 2024-06-03 at 11.21.43 AM.png

To learn more about activation rules and other Deliverable settings being introduced with this release, please see our Creating and Managing Deliverables article.

Automatic Completion of Services Based on Deliverables

While many of your firm's services are recurring, this isn't always true. Estate planning, for example, can be a one-off exercise comprised of a group of discrete tasks. Once the tasks are done, so is the service. To bring this behavior to Practifi, we’re leveraging Deliverables to track those tasks. It's now possible to automatically complete a Service when all its underlying Deliverables are completed or canceled. This feature can be used in conjunction with the ability to Complete, Cancel and Reactivate Deliverables and Automatically Complete Deliverables Based on Number of Fulfillments.

We've added a new Complete automatically with Deliverables setting on Service Type records. When this box is checked, the Service's stage will be updated to Completed when all its related Deliverables have a status of Completed or Canceled.

 

Screenshot 2024-06-06 at 10.30.51 AM.png

Complete, Cancel and Reactivate Deliverables

There are cases where a Deliverable has served its purpose and is no longer needed, or perhaps you want to discontinue it in favor of a new one. In these instances, your firm might prefer to update a Deliverable's status for reporting purposes rather than simply deleting it. We've added two new actions on Deliverable records and list views: Complete Deliverable and Cancel Deliverable.

 

Screenshot 2024-06-12 at 10.08.31 AM.png

 

The difference between these two actions is the status applied to the Deliverable. As you might expect, completing a Deliverable gives it a status of Completed, while canceling it changes the status to Canceled. When a Deliverable’s status is set to Completed or Canceled, the following things happen:

  • The Deliverable no longer appears in the sidebar on Task and Event records.
  • The Next Due Date field’s current value is deleted and stops recalculating.
  • Fulfillment activities are not created.

A new Reactivate action is now available for completed or canceled Deliverables. It allows users to change a Deliverable's status back to Active. When a Deliverable is reactivated:

  • It starts appearing again in the sidebar assistant on Tasks and Events.
  • The Next Due Date field is recalculated based on the current date (today's date).
  • Once the due date is recalculated, fulfillment activities will be created again.

These actions appear on the Deliverable record page and as row and mass actions in the Deliverable list views. You can include the Status field from Deliverable records when reporting on fulfillment.

Automatically Complete Deliverables Based on Number of Fulfillments

Along with the ability to manually complete Deliverables, we're also introducing automation around Deliverable completion. We've added an optional setting called Complete after X fulfillments to Deliverable Type records. When enabled, it allows Practifi Administrators to specify how many times a Deliverable should be fulfilled before it’s considered complete.

 

Screenshot 2024-06-03 at 11.23.57 AM.png

 

This is intended for Deliverables that are limited engagements rather than ongoing. For example, a quarterly review Deliverable specifically given to clients during their first year with the firm must only be fulfilled four times. Once that Deliverable has accrued four statuses of Fulfilled on Time or Fulfilled Late, the Deliverable's status is changed to Completed. This setting can be used with the new Complete Service with Deliverables setting to automate Deliverable and Service completion.

Handling Deliverables on Canceled Tasks

If your firm uses fulfillment activities for Deliverables, the Tasks created by the feature automatically display the Deliverable they're fulfilling in the Marked for Fulfillment section of the side panel. Previously, no automation was applied to Deliverables marked for fulfillment when the associated Task was canceled.

As of this release, when a user cancels a Task, the system deletes the fulfillment record for any associated Deliverables, which are moved from the Marked for Fulfillment section to the Available for Fulfillment section.

Screenshot 2024-06-05 at 11.16.53 AM.png

Please note: Tasks with a status of Canceled will display Deliverables in the Available for Fulfillment section, but plus icons will not appear next to them because canceled Tasks cannot be used to fulfill Deliverables. However, Deliverables previously marked for fulfillment by a Task that is then canceled can be fulfilled by other open Tasks.

Deals and Services Enhancements

New Options for Service Creation

The services your firm offers don't always follow a conventional sales cycle. For example, a client might ask your firm to invest the proceeds from a home sale. In this instance, they're already interested in the service, and creating and closing a Deal is unnecessary. To address this, we're introducing more flexibility around initiating Services in Practifi. We've added a new Available in field to Service Type records. This field controls where users can kick off Services. The options are as follows:

  • New Deal action
  • New Service action
  • New Deal and New Service actions

The Available in setting allows you to tailor workflows to the specific needs of each Service Type, enhancing efficiency and usability. For example, you might make a Service Type available only in the New Service action if the service does not require a Deal to be tracked. If you want to let users decide how they want to start the Service, you can make it available in both the New Deal and New Service actions. 

 

Screenshot 2024-06-03 at 10.27.57 AM.png

 

When Service Types are made available in the New Service action, users can create Services directly from the Services & Pipeline section of a Client record without creating a Deal.

Screenshot 2024-06-03 at 11.02.02 AM.png

Depending on how it's configured, the Available in setting on Service Type records can impact how users progress through the Promote to Prospect and Promote to Client workflows. For more information on this and other Service-related features coming with this release, please see our article on Creating and Managing Service Types.

Create Multiple Services for a Client

Let's say your firm wants to create Services to track the annual preparation of client tax returns. In this case, you'd want a separate tax preparation Service to be initiated and completed each year. Previously, users didn't have the option to create more than one Services of the same type rather than merging them together. We're giving Practifi Administrators the ability to determine what should happen when a Deal is won. 

The new When a Deal is won setting on Service Type records determines what happens when a Deal related to the Service Type is marked as Closed Won. Admins can choose from the following options:

  • Add to existing Service (if available)
  • Create a new Service
  • Let the user decide


Screenshot 2024-06-03 at 11.28.50 AM.png

 

The When a Deal is won setting impacts the behavior of the Promote to Prospect and Mark as Closed Won workflows. When it's configured to let the user decide, they will be prompted to choose whether to create a new Service or add to an existing Service (if available) when closing a Deal.

Custom Stages for Deals and Services

When looking at your firm's different services, the path from identifying a prospect to completing the work can vary greatly. Previously, only one set of stages was available for Deals and Services in Practifi, making it impossible to include variations in lifecycle management. We're addressing this limitation by introducing the option to create custom stages on the Deal and Service objects as well as Record Types that can then be associated with the Service Type record.

 

Screenshot 2024-06-06 at 2.18.23 PM.png

If you're considering enabling this feature, please click below to view important information.

Custom Stage Considerations

  • Once you create a record type in the Deal or Service object, all subsequently created records must have record types. This means a few things:
    • Once this feature is enabled, it cannot be turned off again. Therefore, be sure you want to use it before enabling it.
    • If a Deal or Service is created for a Service Type with no record type specified, it will use the default record type that appears in the active user's profile. Unless a profile has been modified, the default record type is the first one created for that object.
    • Deals created in the Business Development app or for prospective members in the Retirement app don’t relate to Service Types; however, they, too, will need record types to be assigned. To do so, use the Biz Dev Deal Record Type Name and Member Deal Record Type Name settings in the Practifi Settings section of Custom Settings (found in Salesforce Setup). In these fields, specify the API Name of the record types you wish to use.
  • Certain predefined stage values are used within Practifi, such as the Mark as Closed Won action, which updates a Deal’s stage to Closed Won; these will continue to work irrespective of how the Stage field is customized.
    • As a general rule, we recommend customizing the open stages of a Deal or Service rather than those which denote that it’s closed.
    • Please note: The Business Development app uses a Status field on the Deal object to represent different stages of the lifecycle, unlike the Advisor app, which uses a Stage field. Any customizations made to the Status field values will impact the automation associated with the lifecycle flows in the Business Development app, as all Status values are integrated with these flows.
  • Once a record type is created, it cannot be deleted. However, it can be renamed and its stages reconfigured to be used with other Service Types.
  • Future Salesforce release updates plan to place a hard limit on the number of record types that can be used within an instance; currently, the planned limit is 200.
    • Practifi itself contains only 21 record types out of the box, so creating new record types to customize Deal and Service stages won’t risk hitting that limit.
    • However, if your instance is heavily customized or contains several AppExchange products, you should take stock of the number of record types in use and the number you plan to create before enabling this feature. 

For detailed instructions on enabling this feature, please see our Creating Custom Stages for Deals and Services article.

 

New Service Types Page in Settings

Practifi Administrators can now access Service Type records via a new Service Types page in the Settings app. Previously, Service Types were located on the Categories page. This change makes it easier and more intuitive to find Service Type records in the Settings app.

 

Screenshot 2024-06-14 at 8.08.44 AM.png

 

Please note: Existing Practifi organizations will see both the legacy Categories page as well as the Service Types page in the Settings app.

Streamlined New Deal and Promote to Prospect Workflows

We've updated the New Deal and Promote to Prospect workflows to improve usability. Previously, users had to click through multiple screens to complete these actions. With this release, the New Deal and Promote to Prospect windows will be responsive, updating dynamically based on users' selections. This reduces the number of clicks needed to advance through the workflow.

 

Screenshot 2024-06-14 at 1.03.53 PM.png

 

Other Enhancements

View Data Captured in Screen Flows

We've added the ability to display the data captured in Flow-based Active Forms on completed Task records. Previously, only Active Forms built using Form Elements allowed you to see what was entered in the form.

When building an Active Form using Flow Builder, a new option called "Completed task record pages" is now included in the Appears in field in the Details & Settings section of the Active Form Flow record.

Screenshot 2024-06-10 at 9.37.56 AM.png

When an Active Form Flow is configured to appear in completed Task record pages, the values captured during the Flow interview in variables enabled for input/output can be displayed on the Active Form tab of the Task record after it has been marked as complete.

To enable this, Practifi Administrators can edit the Screen Flow in Flow Builder to add a Decision element based on Task status and a Screen element with a Display Text component. Then they can create another instance of the Active Form Flow and configure it to display in completed Task records. For more information on using this setting, please see our article on Understanding and Using Flow Builder.

Fields Added to Addepar Integration

We've extended the range of fields available as part of Practifi’s integration with Addepar. The Asset and Holding record page layouts have been updated to display these new fields.

Many of the fields are customizable from the Addepar side and can be amended or updated within Addepar if you wish to include values with slightly different calculation methods.

The data mappings are detailed in the tables below.

Asset/Liability Object

Practifi Field Label

Addepar Field Name

Practifi Field Name


Performance Last 5 Years

_custom_pfi_twr_5_yr_7841

practifi__Performance_Last_5_Years__c

Performance Last 10 Years

_custom_pfi_twr_10_yr_7842

practifi__Performance_Last_10_Years__c

Performance since Inception

_custom_pfi_twr_since_inception_7843

practifi__Performance_Since_Inception__c

Total Return Last 5 Years

_custom_pfi_total_return_5_yr_7849

practifi__Total_Return_Last_5_Years__c

Total Return Last 10 Years

_custom_pfi_total_return_10_yr_7850

practifi__Total_Return_Last_10_Years__c

Total Return since Inception

_custom_pfi_total_return_since_inception_7851

practifi__Total_Return_Since_Inception__c

Contributions MTD

_custom_pfi_contributions_mtd_7860

practifi__Contributions_MTD__c

Contributions QTD

_custom_pfi_contributions_qtd_7861

practifi__Contributions_QTD__c

Contributions YTD

_custom_pfi_contributions_ytd_7862

practifi__Contributions_YTD__c

Withdrawals Last 12 Months

_custom_pfi_withdrawals_1_yr_7863

practifi__Withdrawals_Last_12_Months__c

Withdrawals MTD

_custom_pfi_withdrawals_mtd_7864

practifi__Withdrawals_MTD__c

Withdrawals QTD

_custom_pfi_withdrawals_qtd_7865

practifi__Withdrawals_QTD__c

Revenue QTD

 

_custom_pfi_revenue_qtd_7870

practifi__Revenue_QTD__c

Revenue Last Year

Annualized Revenue Previous Year

practifi__Revenue_Previous_Year__c

Holding Object

Practifi Field Label

Addepar Field Name

Practifi Field Name

Asset Type

investment_type

practifi__asset_type__c 


For a full list of supported fields, please see our Enabling the Addepar Integration article.

Resolved Issues

Active Forms

  • Highlighting required fields in Active Form Tables: Required fields in Active Form Tables are now highlighted to make them stand out and indicate that users must fill them out to complete the related Task.
  • Active Form multi-screen navigation fix: Users could not freely navigate back and forth between screens of a multi-screen form with incomplete required fields.
  • Active Form prefill validation error: Pre-filling a lookup field with the ID of a record created by the Task (e.g., a Create a Record action) would fail a validation check.
    Please note: You will not be able to see the value being prefilled in the Active Form, as it happens after the Task is completed.
  • Active Form Screen Flow navigation fix: Users advanced to the next Active Form screen but were immediately returned to the previous screen.

Other Items

  • Use logged calls to fulfill Deliverables: We've added the ability to fulfill Deliverables using completed calls. On logged Call records, the side panel will display eligible Deliverables in the Available for Fulfillment section. Users can click the plus icon next to a Deliverable to fulfill it. This is the same fulfillment handling logic used for Events that occurred in the past.

  • Days Before Due Date field now required: On Deliverable Type records, the Days Before Due Date field appears when the Auto Create Fulfillment Activities box is checked. Previously, the Days Before Due Date field was not required and if a user left it blank, an error occurred. With this release, we've made the field required to prevent errors.
  • Asset Holdings moved to a separate tab: To improve visibility and accessibility, Asset Holdings (e.g., underlying portfolio records) have been separated from the Additional Information tab into a dedicated Holdings tab within Asset records.
  • Duplicate custom field fix: A custom field with the same name as a packaged Practifi field caused records to stop displaying on the record table as new records were loaded in via an integration.
  • Process Tasks completed without actions firing: Some Process Tasks were completed without firing the related actions. In the rare case this occurred, the failure would ordinarily be caught by the system and rerun, or admins would be notified to retry manually. Further investigation found that this issue may have stemmed from the backend use of Platform Events to trigger Task actions. Notifications were being sent to an automated user, making manual retries impossible.

    We've now extended the notification system to use the Notification bell to alert users when Task actions have failed and require manual intervention. In addition, we introduced a new custom setting to allow admins to change the Task action trigger from using Platform Events to a queueable job. Users can verify the firing of Task actions by checking Apex jobs, where a queueable job will be visible after completing the Task.

    With these changes, we aim to enhance the reliability of Task action execution and ensure timely notifications for manual intervention when necessary.

  • Large dataset in filter fix: Trying to load a page with 100+ unique filter options (such as Topics) could cause the page to either load slowly or crash altogether. Additionally, resetting filters would reload the page but not clear filters.
  • Streamlined relationship creation for Contacts and Entities: As part of the Montepulciano release in April 2024, we extended the range of relationships you can use to link Contact records to other Contacts or Entities, ensuring you can enter details from either direction of the relationship.

    We've now refined the Entity search when creating or editing a relationship to only return records relevant to the Entity type. For example, only matching records for Contacts will be displayed when relating to a Contact. This also applies to Individual, Household and Organization records, respectively.

  • Rulebook fix for ContactPointAddress object: Users encountered an error when creating Rulebook rules based on the ActiveToDate field on the ContactPointAddress object. We've made the ContactPointAddress object compatible with the Rulebook, allowing users to create rules using fields from the ContactPointAddress, ContactPointPhone and ContactPointEmail objects without error.

  • Translation Workbench fix for Actions menu: Practifi uses the native Salesforce Translation Workbench to display region-specific spellings of certain words. This ensures that UI labels are spelled as expected across US and Australian Practifi organizations.

    The Actions menu on Entity records did not display all options correctly when the Australian translation was enabled. We've resolved this issue so that the spelling of Actions menu items respects the Translation Workbench settings.

  • Enhanced Key Details component for custom data field ordering: When adding custom fields to the Key Details component, the corresponding UI display did not respect the defined field order, leading to random display order. This update now enables users to organize fields as needed.
  • New setting to hide Active Form field labels: As part of the Montepulciano release in April 2024, we introduced a feature allowing multiple Active Form fields to be mapped to a single Long Text Area field on a Process, including each field name with its value. We have received feedback that these field labels can disrupt the appearance of fields in subsequent steps and affect automatic flows.

    To address this, we have introduced a new custom setting, Hide Active Form Field Labels in Mapping, located in Custom Settings under Practifi Settings. When this setting is enabled, only the values of Active Form fields will be mapped, excluding the field labels. This setting is unchecked by default, maintaining the previous behavior.

  • Improved consistency for Tasks, Checklists, Active Forms and Deliverables: To simplify and standardize task execution, we have made the following actions available by default to all users (provided they have the necessary permissions): completing Process Tasks, checking off Checklist items, filling Active Forms and fulfilling Deliverables. This provides a more consistent approach.

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 record page Fields Added to Addepar Integration
  • Added new data points.
Client record page Overview - Active Services
  • Updated to display Services with stages not equal to Draft, Terminated, Completed or Blank.
Services & Pipeline
  • Added a New Service action button to the Services & Pipeline page.
    • The button will appear if the Available in attribute, found in the Service Type settings, is set to either New Service action or New Deal and New Service actions.
Services & Pipeline > Deals list view
  • The list view now includes all Deals associated with the Entity, regardless of their stage.
  • Introduced a None option in the Stage filter for Deals lacking a specific stage designation.
  • Introduced a None option in the Rating filter for Deals without any rating assigned.
Services & Pipeline > Services list view
  • Updated the data table configuration to display all Services related to the Entity, even those without a Stage assigned.
  • Introduced a None option in the Stage filter to facilitate filtering Services that do not have a specified stage.
Custom Settings - Practifi Settings Custom Settings for Biz Dev Deal Record Type Name and Member Deal Record Type Name
  • Added two custom settings under Practifi Settings called Biz Dev Deal Record Type Name and Member Deal Record Type Name.
Setting to Hide Active Form Field Labels in Mapping
  • Added a new custom setting called Hide Active Form Field Labels in Mapping under Practifi Settings.
Custom Settings - Practifi Trigger Settings Custom Setting for Skip Serv. Type in Promote to Prospect
  • A new custom setting has been added under Practifi Trigger Settings called Skip Serv. Type in Promote to Prospect, which is unchecked by default.
Deal object Fieldset - Practifi - New Deal action
  • Created a new fieldset named Practifi - New Deal action that includes fields from the Deal object such as AUM, One-time Revenue, Close Date, Stage, Rating and Description, giving users flexibility in configuring fields for the Promote to Prospect and New Deal actions based on their requirements.
Deals list views Mark as Closed Won - mass action modal update
  • The modal has been updated to inform users that the action will continue to work as it does currently in the product. Users are notified that the When a Deal is Won setting configured on Service Types won't impact the mass action. To utilize this setting, users need to use the record action instead.
Removal of the Mark as Closed Won action button from data tables related to closed Deals
  • The Mark as Closed Won action button, previously visible on Pipeline data tables designated for closed Deals, has been removed across all apps. This action held no value for closed Deals, as they were already closed.
Updates to data tables
  • The table config has been updated to support custom stages for Deals.
  • The Stage filter has been configured to support custom stage values for Deals.
Change Stage action
  • All Deal record lists now include a row and mass action.
  • The modal has been configured to display a picklist of stage options based on the records selected, accommodating either single record type or multiple record types.
Mass Edit action
  • The Stage field in this action does not allow user input and is restricted.
  • The help text for the Stage field in this action has been updated to inform users to use the Change Stage action to update stages, as multiple custom stages may be involved for different record selections.
Deliverable Fulfillment object Help text
  • We removed irrelevant help text from the Status field on the Deliverable Fulfillment object.

Deliverable record page

Days Before Due Date Field Now Required

 

  • The Days Before Due Date field, which appears when the Auto-create fulfillment Activities box is checked, is now mandatory at the field level.


Automatically Complete Deliverables Based on Number of Fulfillments
  • A new field, Complete after X fulfillments, has been added to specify how many times a Deliverable must be fulfilled before being marked as complete.
    • This field is located in the Fulfillment Settings section and can be edited by users with the Manage Deliverable Settings permission set.
Activation Rules for Deliverables
  • Added the Rule Builder component to the Deliverable record page positioned under an Activation Rules tab adjacent to the System tab.
Complete, Cancel and Reactivate Deliverables
  • Added a new Completed Status for Deliverables, indicating the Deliverable’s job is done and it’s no longer required.
  • The Status field has been made read-only on the record page to prevent unauthorized changes
    • The Status field defaults to Active upon Deliverable creation.
  • A new Complete action has been added for manually completing Deliverables, visible when the status is not already Completed or Canceled.
    • This action can be found on the Deliverable record page and in record lists.
  • A new Cancel action has been added to the Deliverable record page and lists, allowing users to change a Deliverable's status to Canceled.
    • The Canceled status was introduced in Cabernet Franc for canceling Services or marking clients as lost. Now, it applies to individual Deliverables as well.
    • This action is displayed on the record page only when the Deliverable's status is not already Completed or Canceled.
  • A new Reactivate action has been added to the Deliverable record page and lists, allowing users to update completed or canceled deliverables to Active.
    • This action is displayed on the record page only when the Deliverable's status is Completed or Cancelled.
Backend field to store activation rule
  • Implemented a new Long Text Area backend field called Activation Rule on both Deliverable Type and Deliverable objects for defining activation rules.
Deliverable Type record page Days Before Due Date Field Now Required
  • The Days Before Due Date field, which appears when the Auto-create fulfillment Activities box is checked, is now mandatory at the field level.
Automatically Complete Deliverables Based on Number of Fulfillments
  • A new field, Complete after X fulfillments, has been added to specify how many times a Deliverable must be fulfilled before being marked as complete.
    • This field is located in the Fulfillment Settings section and can be edited by users with the Manage Deliverable Settings permission set.
Activation Rules for Deliverables
  • Added the Rule Builder component to the Deliverable Type record page positioned under an Activation Rules tab adjacent to the System tab.
Backend field to store activation rule
  • Implemented a new Long Text Area backend field called Activation Rule on both Deliverable Type and Deliverable objects for defining activation rules.
Deliverables list views Complete, Cancel and Reactivate Deliverables
  • A new Complete action has been introduced for manually completing Deliverables, available as both single-record and mass actions.
    • This single-record action is displayed only when the Deliverable's status is not Completed or Canceled.
  • A new Cancel action has been added to the Deliverable record page and record lists, allowing users to change a Deliverable's status to Canceled, available as both a single-record and mass action in Deliverable record lists.
    • This single-record action is displayed only when the Deliverable's status is not Completed or Canceled.
  • A new Reactivate action has been added to the Deliverable record page and record lists, allowing users to update completed or canceled Deliverables to Active, available as both a single-record and mass action.
    • This single-record action is displayed only when the Deliverable's status is Completed or Canceled.
Column and Filter upgrades
  • Added a Status column next to the Type column.
  • Introduced a Status checkbox filter, allowing users to easily filter records by Deliverables' status.
  • Removed the default Set Reminder column from the list view.
Mass Edit action
  • In the Status field within the mass Edit action on Deliverables list views, help text has been added to guide users on making status changes.
    • Users are advised to utilize the Complete, Cancel and Reactivate actions for this purpose.
Holding record page Fields Added to Addepar Integration
  • Added new data points.
Lookup Rollup Summaries Config updates for Lookup Rollup Summaries related to practifi__Stage__c
  • Updated criteria for the following summaries related to practifi__Stage__c being Active to exclude stages Draft, Terminated, Completed or Blank:
    • AUM To Client
    • Annual Revenue To Client (New)
    • Annual Revenue To Client
Mark as Closed Won action on Entity record page Contextual footer button
  • Relabeled the footer button as Close Deal to better reflect the context of the action.
Implementation of Reactive Screen Components
  • Depending on the Service Type When a Deal is won settings configured,
    The modal now dynamically displays text to the user, informing whether the closed Deal is added to an existing Service (if available) or creates a new Service.
  • Users are prompted in real-time within the modal to choose between associating the closed Deal with an existing Service (if available) or creating a new Service if the setting is configured to do so.
New Deal action on Prospect record page New Deal button
  • This action button will appear on the Entity record if the Available in attribute, found in the Service Type settings, is set to either New Deal action or New Deal and New Service actions.
Implementation of Reactive Screen Components
  • Implemented teactive screen components within the modal interface to streamline user interactions, aimed to reduce the number of clicks and screens users navigate through.

  • On inputting a Service Type,
    Fields from the Practifi - New Deal action fieldset are visible within the same screen in the modal. This allows users to input Deal details for creation without navigating to additional screens.

Contextual footer button
  • Relabeled the footer button as Create Deal to better reflect the context of the action.
Process Task record page Improved Consistency for Tasks, Checkboxes, Active Forms and Deliverables
  • In the Settings app, the help text for the Enable Advanced Execution Management? field on the Process Task record page has been revised to offer a clearer explanation of how it influences Task execution.
Promote to Client action on Entity record page Contextual footer button
  • Relabeled the footer button as Promote to better reflect the context of the action.
Implementation of Reactive Components
  • Depending on the availability of open Deals on the Prospect record and the Service Type Available in settings configured, the modal now displays options to the user to either close existing Deals or leave them open and create new Services.
Promote to Prospect action on Entity record page Contextual footer button
  • Relabeled the footer button as Promote to better reflect the context of the action.
Implementation of Reactive Screen Components
  • Implemented reactive screen components within the modal interface to streamline user interactions, aimed to reduce the number of clicks and screens users navigate through.
  • Relevant components will dynamically appear on the same screen based on the chosen Service Type.
Prospect record page Overview - Pipeline
  • Configured to display Deals with stages not equal to Closed Won or Closed Lost.
  • Adjusted configuration to support custom stages.
Pipeline - Deals list view
  • The list now includes all Deals associated with the Entity, regardless of their stage.
  • Introduced a None option in the Stage filter for Deals lacking a specific stage designation.
  • Introduced a None option in the Rating filter for Deals without any rating assigned.
Potential Service field
  • Added a new lookup field called Potential Service in the Overview - Basics - Key Measures section, positioned below the Potential Annual Revenue field on a Prospect record page.
Service object Fieldset - Practifi - New Service Action
  • Created a new fieldset named Practifi - New Service Action that includes fields from the Service object such as Service Name, Start Date, Stage, AUM and Description, giving users flexibility in configuring fields for the New Service action based on their requirements.
Service record page New Deliverable action
  • The New Deliverable button in the Service Record area has been changed from a modal flow to a detailed page button.
Service Type record page Category (Service Type)
Record page improvements
  • The Category record has been migrated to a dynamic form.

  • New Summary section created, existing fields moved here.

  • Added a new Text Area field named Description below the existing Active checkbox.

  • Added help text to the Group field.

  • Added a new Default asset-based service? checkbox below the Group field (unchecked by default).

  • Created a new Service Settings section below the Summary section.

  • Added a new Available in picklist field in the Service Settings sectionn with the following options:

    • New Deal action

    • New Service action

    • New Deal and New Service actions.

  • Added a new When a Deal is won picklist field in the Service Settings section that is conditionally visible based on the Available in setting for creating Deals. It has the following options:
    • Add to existing Service (if available)
    • Create a new Service
    • Let the user decide
  • Added two new text fields, Deal Record Type and Service Record Type, in the Service Settings section that are conditionally visible when the Category is a Service Type.
Service Types app page Settings app page for Service Types
  • Created a dedicated app page for Service Types in the Settings app, replacing the existing menu item for Categories.
Available Service Types list view
  • The new Service Types app page displays a list view called Available Service Types with the following columns:
    • Service Type Name
    • Active
    • Group
    • Default asset-based service
    • Created Date
    • Available in
    • When a Deal is won
Services list views Updates to data tables
  • The table config has been updated to support custom stages for Deals.
  • Data tables related to Active Services display records where the stage is not equal to Draft, Terminated, Completed or Blank.
  • Data tables related to Inactive Services display records where the stage is equal to Draft, Terminated, Completed or Blank.
  • The Stage filter has been configured to support custom stage values for Services.
  • The Type filter has been renamed Service Type.
Change Stage action
  • All Service record lists now include a row and mass action.
  • The modal has been configured to display a picklist of stage options based on the records selected, accommodating either single record type or multiple record types.
Mass Edit action
  • The Stage field in this action does not allow user input and is restricted.
  • The help text for the Stage field in this action has been updated to inform users to use the Change Stage action to update stages, as multiple custom stages may be involved for different record selections.

Task record page


 

Deliverable Fulfillment on Logged Call Activities
  • A collapsible Available for Fulfillment section displays Deliverables ready for fulfillment via the call, while a subsequent section called Fulfilled shows a list of already fulfilled items.
Handling Deliverables on Canceled Tasks
  • The Available for Fulfillment section in the Deliverables component sidebar will no longer display the plus icon next to Deliverables if the status of the Task is Canceled.
1 out of 1 found this helpful

Comments

0 comments

Article is closed for comments.