Contents:
Overview
The True/False Decision Node allows you to make branching logic based on the criteria on a record or on a record you previously matched using a Match Node. Utilize a True/False node to determine if a certain condition is met and then determine the path the Lead record should take. This node allows for 2 outcomes, True or False. If you have multiple conditions that require more than 2 outcomes (such as geo, industry, company revenue size etc), utilize the Branch Decision node.
Customization
When you select a True/False decision node, you need to determine which object you’re evaluating to see if a condition is met.
For Calendar Router, you have the following options:
- Prospect: The condition is being evaluated against the incoming Prospect that is being processed through the router flow.
- Prospect to Lead (P2L): The condition is being evaluated against a matched Lead from a prior Lead Match Node.
- Prospect to Account (P2A): The condition is being evaluated against a matched Account from a prior Account Match Node.
- Prospect to Opportunity (P2O): The condition is being evaluated against an Opportunity from a prior Opportunity Match Node.
- Duplicate Lead (DupeL): The condition is being evaluated against a potential duplicate Lead from a prior Dupe Lead Match Node.
- Duplicate Contact (DupeC): The condition is being evaluated against a potential duplicate Contact from a prior Dupe Contact Match Node.
After you have selected the type of True/False node, you have a number of options to configure the node.
- Node Name: By default, the Node Name is set to True/False. You can change this label to anything you need. We strongly recommend giving this node a meaningful name such as the subject of the decision. This will help others understand the purpose of the node.
- Description: This field is not required but we recommend adding a description to document any customizations made to the node. If someone else needs to take over the management of the flow, they will be able to understand the goal of the customizations.
- Rule Type: You will see 2 options under Rule Type:
- SOQL: The SOQL (Salesforce Object Query Language). Currently this option is not available for the Prospect Decision Node. It is available for the other T/F decision node types such as Prospect to Lead and Prospect to Account.
- Logic: The Logic option gives you tools native to LeanData to set up the criteria for the decision of the node.
Logic Rules
When you select a Logic Rule for the basis of the Decision Node, you will see tools to help you build the logic behind the decision being applied to the record.
Under the option, Logic Rule, you will find the following:
- Prospect Variable: The Prospect Variable selector will give you a list of all the variables on the Prospect (First Name, Last Name, Company, etc.) that you are routing.
- Operator: The Operator gives you a condition to apply to the variable for the decision. (Example: Contains, does not contain, starts with, is null, etc). The values in the Operator selection change depending on the field selected.
- Value: The Value is the value you are evaluating against in your selected field.
To Add a Logic Rule to the Decision Node:
- Click on the True/False Decision Node.
- Click the pencil icon to the right of the node. The edit window opens on the right side of the page.
- Select the option: Logic Rule. The screen displays the Field, Operator, and Value boxes.
- Select the desired field to apply the decision to. If you start typing the first letters for the desired field such as “st” for status, you will see the list filter for just fields that have the text combination you entered.
- Select the desired operator.
- Enter/select the value you are evaluating against in your selected field.
- Set other fields as needed.
- Save.
Logic Rules with Matched Records
When working with Matched records, the options you will see depends on the type of node you are configuring. If you are configuring a Prospect to Lead True/False Node you will see Matched Lead fields in your Logic. If you are configuring a Prospect to Account you will see Matched Account fields as you can see in the screenshot below.
The matched record fields you can access depends on the type of True/False node that you selected and if you have previously matched to a record of the same type. For example, in order to access Matched Account Fields, you need to have previously matched to an account in the Calendaring Router flow and the True/False node type you selected needs to be Prospect toAccount. These two factors will configure the node to pick up matched account fields as you can see in the screenshot above.
Value/Variable
The Value/Variable selector lets you choose between a specific Value to compare like Revenue greater than 10 million. With the Variable option you will be comparing the matched field with a variable field such as Industry Equals Industry. Only records that have the same industry as the Prospect Industry will satisfy this condition.
Please Note: If you select a specific Branch node (Prospect to Account for example) and have not previously matched to the same object type, (Account), you will still be able to configure the node with the matched fields but you will get an error when saving the node configuration.
Merge Fields
The Merge Field feature allows you to insert a value from another variable field into the Value Field . Fields on any matched objects are available, as well as any variables directly on the routed record.
Working with Multiple Conditions
True/False Decision Nodes include only 1 rule for the decision. However, within the 1 rule, you can have multiple conditions. When you have a rule with multiple conditions you are given the option to specify the relationship between the conditions. By default, you will see an AND relationship. You can change this to OR as needed. You can also use parentheses to group conditions together. Example: ((1 AND 2) OR 3).
Node Edges
The True/False Decision Node gives you 2 edges to route records through, Met and Not Met. All records that meet the Logic Rule and Conditions you have set, will be sent through Met edge. All records that do not meet the rules and conditions will be routed through the Not Met edge.
Things to Know & Best Practices
- Use Logic rules rather than SOQL conditions as much as possible.
- If you need more than 2 outcomes, use a Branch Node instead of a True/False node.
- Change the names of the Labels as needed to help identify certain paths in the flow.
- Change the names of your Nodes so you can easily decipher the condition or criteria going through that node.
- Add descriptions wherever you can.
- You can only use a Decision node that references fields on a matched record if you had previously found a matched record in a corresponding match node.
Summary
The True/False Decision Node is a powerful tool to test a record against a specific condition and to determine the Prospects route through your router flow. The True/False node gives you two edges for Prospects that meet the conditions of the node and the Prospects that do not meet the node conditions. Using the customization settings, you can create a powerful test for your Prospects.
For more information on working with router flows please see our BookIt FlowBuilder Guide.