Understanding Processes



Processes streamline your firm's frequently repeated work by operating from various record types to create workflow automation. The process follows a determined workflow that generates tasks while triggering the automatic creation of new tasks based on preceding tasks. In addition, processes have the functionality to update task and process outcomes and automatically change record stages.

This article outlines the functions and meanings behind the terms you will encounter when establishing a process in your Practifi instance. For more information on how to create a process, please consult our Creating Processes article.

Process Building Page

The process building page is where the skeleton of the process lives and contains the process settings, related tasks, actions, and outcomes. Within this page, the Summary section houses the relevant information about the process, such as the process's name and the objects that the process relates to. Relating a process to objects enables access to the process within those contexts in Practifi. For example, a process related to the Client object can be accessed from a client record. However, if the process is only related to the Client object, it cannot start from within a Service or Client Entity record. 

This section also establishes if the process is active within your Practifi instance and whether it includes a helpful description to make it clear to your team members where and when to use it. As your firm's workflow evolves or streamlines, older processes may need to be deactivated or modified, and the process building page is where these edits will begin. Once a process is moved to inactive status, it will not be available for selection by any user. 

Process Settings

Process settings set the starting stage for the process, potentially enabling a time-based kick-off and standardizing the assignment of the process. These process settings can be modified following the initial creation of the process, but the modifications will not change any currently running process settings.

Process Stage

The process stage sets the overall stage while your firm works through the underlying tasks. The process stage is separate from the related task's stage and typically stays in an in-progress stage while working on the related tasks. The process stage would then transition to closed upon completing the final task. Each process has an open configuration for custom stages for each transitional state and the ability to create as many or as few as needed.

Assignment Type

The options within the Assignment Type field in the process settings establish which of your team members will be assigned as the process owner upon creation. The automation behind this option standardizes the assignment of the overall process in the following ways:

  • None – Auto-assigns the process to the team member starting the process.
  • Specify Now – Allows a specific team member or queue to be assigned the process upon process creation. Teams attempting to assign ownership via Specify Now will need to make the assignment choice and select the save button before gaining access to change the Owner field.


    Please Note: Once the team selects the Save button, they can change the owner by clicking on the gray person icon next to the current Owner name. 


    A new menu will open to allow the selection of a specific user or queue assignment.


  • Assign to Service/Client Owner – Assigns the process to the related service or entity owner.
  • Specify by Servicing Team Role – Allows the selection of specific servicing team roles assigned at the entity or team member level.

Please note: If you would like to build a queue to allow for larger team assignments for either Processes or Process Tasks, feel free to review our article on Creating and Managing Queues.

Time-Based Commencement Settings

The time-based commencement settings allow the process to begin based on various date fields across the Entity, Contact, Service and Deals objects. First, a target object is selected to relate to the process. Within that target object, a date field is selected to base the beginning of the process. Basing the process on the date field means that the process can be set to begin a certain number of days before or after the date populating the field.  

Within the time-based commencement settings, the Commencement Timing field sets if the process occurs before or after the date within the target field. The Number of Days field in commencement settings is used to input the correct amount of days that the system calculates to set the timeline for the beginning of the process. The numbers for this field begin at one and operate as calendar days, not business days, and must be considered when setting the field information.

Process Tasks

The Process Tasks section is where the main components of a process exist. While each section can be complex, the Process Tasks section needs the most work to build effectively and accurately. This section sets what builds each step, the various outcomes within those steps, and establishes actions that can start the following step(s), service dates and process stage changes. Within this section, you will encounter task settings, outcomes, actions and predecessors. 

Task Settings

Like the main process, each process task will allow you to set standards for the overall assignment within the task settings. This is established with the same definitions as the process assignment, where it is assigned to a specific person, queue or servicing team member based on the relationship to the entity or owner. The Due Date Interval within task settings establishes the number of days between creating the task and its due date. With this interval established, the system will calculate the task's due date automatically.

Rather than having all process tasks begin at process creation, tasks can be suppressed to begin at a later time triggered by using the  Suppress At Launch checkbox. With this checkbox enabled, the task will need an action to establish its creation in the workflow. Also similarly to the main process, the underlying tasks can be set to have their immediate status set before any team members push it forward through the Status field. Within task settings, the Priority field presents us with the option of adding a "high," "normal" or "low" priority to help team members understand the general importance of completing this item.


Outcomes function as answers to each process task, and they operate to potentially create decision-tree logic within a process to branch into the various scenarios that may exist. Outcomes determine the path that the overall process will take and determine which task should follow next. For example, when completing the process step "Confirm meeting with prospect," you may be able to communicate with them via phone or email to confirm the meeting, or you may be unable to reach them. These options are created as outcomes for the process task and can be structured to lead to different issues within the larger process. 


Actions are the "next steps" that can come from any movement on a process task once a process step moves to a completed status. These can be as simple as a stage change to the overall process or as complicated as creating a new service and starting an additional process. 

The complete list of action type options available are:

  • Create New Task in the Process
  • Start a New Process
  • Set Process Stage for this Process
  • Create a New Service
  • Set Service Stage for Related Service
  • Set Client Stage for Related Client
  • Create a New Service and a New Process

Multiple actions can be layered upon a process task to achieve multiple functions from the list above to complete a singular task.

Please note: To build multiple actions based on completing one task, you must create each action item individually.

Preset Checklist Items

Tasks are often much more than a single instruction: they’re a collection of individual items that add up to a complete workflow step. These items have a natural home in the Checklist, which overcomes the need for complicated task instructions or multiple steps.

Items in the Checklist come in two forms:

  • Manual items - These are considered complete when the owner of the task puts a tick in their checkbox.

  • Automatic items - These are considered complete when their criteria have been fulfilled. Criteria logic is handled by a checkbox field located elsewhere, which gets automatically checked using either formula logic or other automation. The automatic checklist item simply reflects the status of that field.

When setting up Task Templates and Process Task items preset Checklist items can be established and available in the left sidebar. These fields are available when creating a Checklist item:

Field Name Type Help Text

Text (255)


Number (10,2)



  • Manual (default)

  • Automatic



If checked, then the user completing the workflow step will be required to complete this checklist item first.

Criteria Location

Only appears if the item’s Type is Automatic.

Text (255)

Specify the checkbox field used to determine whether this item has been completed by entering the path taken to get there from the Task record using Salesforce formula syntax.

Use either a checkbox formula field or one that’s checked using other automation.


If Criteria Location isn’t accessible

Only appears if the item’s Type is Automatic.


  • Don’t display this item (default)

  • Display this item as incomplete

If a Criteria Location is not on the Task, but instead on a related record, then certain lookup fields must be populated in order to reach it.

Use this field to determine whether missing lookup fields cause the item to be ignored, or treated as incomplete.


The checklist appears in the right sidebar of the Task record page. Completing manual items is as easy as checking the box, however, automatic items will only be marked as complete if their criteria are fulfilled. As a result, their label should always clearly indicate what criteria they represent.

The Refresh button located at the bottom-right of the checklist lets you obtain the latest data from the checklist’s automatic items, which can be useful if you’ve had the page open for some time.

When completing a task with the Mark as Complete action, the checklist will appear again, providing the last opportunity to tick off any items before proceeding with the required items needing to be checked before it is allowed to be marked as completed. Once the task has been completed, the checklist cannot be modified.

Users can use the New button in the bottom-left of the checklist to add a new item. This is true regardless of whether the task is a step in a Process, a Task Template or an ad-hoc task not tied to a workflow at all. Only the owner of the task can create checklist items; the New button doesn’t appear to other users. Checklist items created on open tasks can only be manual tasks; automatic ones must be preset.

Checklist items can be deleted, but only if they were created while the task was open. Preset checklist items cannot be deleted. If deletion is an option for a checklist item, then a delete button will appear next to it. If you add or remove preset Checklist items from a Process Task or Task Template that’s already in use, those changes will not apply to open tasks.


The Predecessors section shows any actions that led to the creation of the particular process task. The first step in a process will not have any predecessors listed, as nothing came before it, but all other steps should have predecessors displayed. The Predecessors section is helpful because it allows the creating user to see everything that led to the start of the task, especially if your process uses grouped predecessors, where several process tasks must be completed to move on to a particular step. This section is also helpful for testing your process from the end to the beginning to ensure no unknown gaps exist in the workflow created by tasks not correctly linked to the process.

Default Process Types

Your Practifi organization comes with default process types included for use. These process types can be managed to enable or disable their use in your organization depending on your firm's needs. The following list contains the default process type names and a short description of their intended use. 

  1. Plan Implementation Meeting - A process that sets up and conducts a meeting with a prospective client after an investment plan has been created. This meeting in particular is focused on developing and presenting a financial plan as well as discovering other potential opportunities with the prospect.
  2. Account Closing - This process is designed to walk through the necessary steps to close out one or more financial accounts for a client, either at the client’s request or if the client is leaving the firm. It includes discussions with the client, documenting and collecting the proper forms and all the steps necessary to take with the custodian.
  3. Annual Review Meeting - This process is designed to help your firm conduct annual review meetings with your clients as part of your service obligation to them. Includes meeting scheduling, preparation before and on the meeting day as well as assisting with any follow-up items that arise from the meeting itself. 
  4. Account Opening - A process designed to keep you across all of the tasks that need to occur to open a new account for a new client or an additional account for an existing client. Includes collecting all the proper information, submitting forms to the custodians and informing the client once the account has been opened. 
  5. Investment Plan Creation - This process is part of onboarding a new client that occurs after a discovery meeting but before a plan implementation meeting. It is designed to set up a meeting with the prospect, develop an investment plan, present it to the client and determine what should happen post-meeting.
  6. Move Money - This process is designed to keep track of all the steps required when a client asks to move money from their accounts including receiving all the proper authorizations, checking with the custodian and disbursing the funds to the proper place. 
  7. Initial Contact with Prospect - This process helps conduct a meeting to assess the suitability of a new prospect. Includes meeting set up, preparation and fit of a prospect as well as next steps whether the prospect is a good fit or not. 
  8. Discovery Meeting - This process is part of the prospecting journey after the initial contact with a prospect and before developing an investment plan. Includes scheduling, preparing and conducting a meeting that leads to more information about the prospect's financial situation.
  9. Life Event - This process is designed to assist the user in updating key parts of the client record when specific major life events occur to a client. Often with major life events, the investment plan is affected. This process will help determine what to do in the event of a death, or whether the event impacts the client’s investment plan. 
  10. Trade Request - This process is designed to make sure that when a  client requests a trade all the appropriate checks and balances are followed including determining whether the trade impacts their financial plan and ensuring the trade processes without error at the custodian. 
  11. Terminated Client - This process assists in accomplishing all the things that need to be accounted for when a client leaves the firm including returning prorated fees, updating the client record and filing all of the necessary paperwork.
  12. 401k Rollover - This process is designed to help track the steps needed to properly roll over a client 401k to your firm including gaining the proper signatures, contacting the custodian and verifying the funds have rolled over to the new accounts. 
  13.  Job Change - This process assists the user in updating the client record in all of the necessary places as well as sets a review for the job change impacting the client’s financial plan. 
  14. New Employee Onboarding - This process is to aid operations users in onboarding a new employee to your firm including setting them up in each of the systems as well as all of the training and getting them the proper paperwork. 
  15. Employee Departure - This process ensures that when an employee leaves all of the necessary paperwork, precautions and physical equipment are taken and collected from the departing employee.
  16. Address/Email Change - This process assists the user in making the appropriate changes to the client record when an address change is reported. This includes updating multiple systems that house client data and need to continue to be in sync.
  17. Charitable Contribution - This process helps organize the steps it takes for a client to make a donation to a charity including steps to confirm the organization, determine the amount of the donation and obtain the receipt of the donation. 
  18. Quarterly Billing - This process is designed to aid the firm in keeping track of their quarterly billing including generating invoices, reviewing exceptions, fee reconciliation and sending the bills to clients.
  19. Birthday Planning - This process is time-based meaning that it automatically will begin for each client a set number of days before their next birthday. Includes options with each client determining if you give them a call, meet for lunch, send a card, send a gift or any combination of these options. 
  20. Client Death - This process accounts for all the steps a firm is responsible for doing when they discover a client of theirs has passed including obtaining the death certificate, sending condolences, updating the client record, updating the financial plan and following up with any beneficiaries, if necessary. 
  21. Required Minimum Distribution - This process is designed to work with clients to ensure that they are meeting their required minimum distribution for the year on their retirement accounts. Includes steps to determine the RMD, check to see if it has been met and contact the client to encourage the distribution or inform them about meeting their requirement. 
1 out of 1 found this helpful



Article is closed for comments.